Closed f3derical closed 3 months ago
Hi @f3derical
I think the linked section is attempting to provide general guidance on best practice for design of a FHIR API if you're developing an API for a new use case - to make sure the mapping from data sources (that HNZ might have no view of to provide a mapping) is clear to stakeholders.
You're correct that it would be good to standardise on the interfaces for sharing of data for various scenarios (and this might include mappings from existing systems / standards where that's possible) - that's beyond the scope of this section of the standard for now, and more in the realm of things like NZBase, HISO standards, a potential future NZ Core standard, etc.
Summary
Hi there, I am questioning the need for each FHIR API designer to provide the mapping for each business domain. There is a variety of origin data (HL7v2 segments, HL7v3, CCDA sections, ...) that will be mapped to specific FHIR resources. Should it not be the responsibility of Te Whatu Ora to provide the expected mappings at a national level instead?
Link to standards item
https://apistandards.digital.health.nz/draft/fhir-api-standard/Principles%20and%20Guidelines/DataMapping
Which area of the standards does this apply to?