hl7 fhir - SoR reference data -


fhir sor valuesets hardly ever have 1 one mapping - there need map 1 many or vice-versa.

in context, part of fhir response our server, need supply sor specific reference data along chosen fhir code/codeableconcept. example, see status below -

{   "resourcetype": "appointment",   "id": "example",   "text": {     "status": "generated",     "div": "<div xmlns=\"http://www.w3.org/1999/xhtml\">brian mri results discussion</div>"   },   "status": "booked",   **<<"sor_status" : "xyz_booked">>** } 

the idea being consumers need supply sor values during post/put/patch interactions correctly mapping sor.

we have considered using _fhir_comments or extensions carry such values each relevant attribute, but, there limitations both - _fhir_comments not intuitive purpose , extensions need create several (possibly duplicating) resources , reference data attributes need carry such values.

what recommendation in case - should go extensions? if so, there better (generic) way implement extensions - should consider extending types instead of resources? other suggestions welcome.

extensions appropriate way of conveying information. comments never intended convey semanticly meaningful information. primary purpose give guidance when reading example instances.

it's possible define extension that's allowed used on multiple resources. if have concept needs appear on many/most resources, need define 1 extension. list each allowed resources allowed 'context' extension.


Comments

Popular posts from this blog

node.js - Node js - Trying to send POST request, but it is not loading javascript content -

javascript - Replicate keyboard event with html button -

javascript - Web audio api 5.1 surround example not working in firefox -