FHIR Managing Overlap between Resources

From HL7Wiki
Revision as of 06:01, 8 November 2018 by GrahameGrieve (talk | contribs) (Created page with "= Background = When designing resources for FHIR, HL7 works to ensure that resources are clearly differentiated with as little overlap in functionality as possible. However...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Background

When designing resources for FHIR, HL7 works to ensure that resources are clearly differentiated with as little overlap in functionality as possible.

However this is often not possible, and that's particularly a problem when dealing with legacy information that's poorly described, and therefore poorly distinguished. Some typical examples where legacy information might be poorly differentiated:

  • Condition vs Observation
  • DiagnosticReport vs DocumentReference

Sometimes, the differentiation will be based on the source of the information, rather than the nature of the information. For instance, an EHR might have a set of DiagnosticReports that it received directly from a lab, and other diagnostic reports as DocumentReferences because they were recieved from the patient by scanning paper documents.

more

For further information, see [gForge 19251]

Todo: migrate content to here