-
Notifications
You must be signed in to change notification settings - Fork 25
Description
Hello
First I'd like to say this is a much-needed library that's both incredibly fast and implements recent operators of the ECL.
I'm enjoying learning to use it!
I just came across a behaviour I don't quite understand for concepts in the UK drug extension, which have longer identifiers.
This first happened on my laptop and it seems the behaviour is similar using your helpful test server.
I do apologise in advance if the explanation should be obvious - I seem to be observing a change in the last digit of the concept ID of UK medical products. The two example below seem to affect all the REST endpoints I've tested.
I am wondering whether I'm missing something. The data stored seems valid, it's just the REST response doesn't match.
Curious to understand what is happening with the retrieval.
Thanks!
Peter
http://3.9.221.177:8080/v1/snomed/search?constraint=9401401000001101
[
{
"id": 47770001000001110,
"conceptId": 9401401000001100,
"term": "Zoladex",
"preferredTerm": "Zoladex"
}
]
You can see the concept id 9401401000001101
reads 940140100000110
0
http://3.9.221.177:8080/v1/snomed/concepts/38001711000001104/preferred
{
"id": 653951000001114,
"effectiveTime": "2020-01-22",
"active": true,
"moduleId": 999000011000001200,
"conceptId": 38001711000001100,
"languageCode": "en",
"typeId": 900000000000013000,
"term": "Leuprorelin 10.72mg implant pre-filled syringes 1 pre-filled disposable injection",
"caseSignificanceId": 900000000000017000
}
You can see the concept id 38001711000001104
reads 3800171100000110
0