search

hl7-be / allergy

Allergy package from the Patient Dossier
Other
0 stars 1 forks source link

Added value or reason for identifier with coding system https://www.ehealth.fgov.be/standards/fhir/allergy/NamingSystem/be-ns-allergy #98

Closed nicovn closed 1 year ago

nicovn commented 1 year ago

What is the added value, or reason for requiring an identifier with coding system https://www.ehealth.fgov.be/standards/fhir/allergy/NamingSystem/be-ns-allergy in the AllergyIntolerance resource ?

Where does that identifier come from ?

Can you give an example ?

bdc-ehealth commented 1 year ago

@nicovn ,

the reason for this identifier is that the business wants to be able to link copies in different systems together. So if a system, e.g. RSW has an allergy registration, (with its own technical id), and it passes it on to Vitalink (with its own technical id, i.e. a different one from the RSW id), than it can still know it is about the same allergy registration.

nicovn commented 1 year ago

Hi Bart,

And who will generate those identifiers in naming system https://www.ehealth.fgov.be/standards/fhir/allergy/NamingSystem/be-ns-allergy ?

Will eHealth foresee a service/endpoint that Vitalink/RSW, hospital EPR vendors... can call to generate a unique id in that naming system ?

Sorry, but I don't see how this will work in real world ...

Thanks !

Nico

bdc-ehealth commented 1 year ago

The value of the identifier will be a UUID, and that UUID, if it is created in an algorithmically correct way, is always unique, independent of the system that creates it. Every modern programming language has a library that is able to create these UUIDs.

See documentation here: https://en.wikipedia.org/wiki/Universally_unique_identifier

https://docs.google.com/document/d/13qamEPfdQ2HgUiXmjwHQNchpEU3LsQHF5MN9jKufX2g/edit?usp=sharing