This wiki has undergone a migration to Confluence found Here

Difference between revisions of "FHIR Managing Overlap between Resources"

From HL7Wiki
Jump to navigation Jump to search
(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...")
 
(Migrate Content to Confluence/Added Forward Link)
 
Line 1: Line 1:
= Background =
+
Content on this page has been migrated to Confluence here: https://confluence.hl7.org/display/FHIR/Managing+Overlap+Between+Resources
 +
 
 +
=Background=
  
 
When designing resources for FHIR, HL7 works to ensure that resources are clearly differentiated with as little overlap in functionality as possible.  
 
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:
 
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
+
*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.  
 
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 =
+
=more=
  
 
For further information, see [[https://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=19251&start=0 gForge 19251]]  
 
For further information, see [[https://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=19251&start=0 gForge 19251]]  
  
 
Todo: migrate content to here
 
Todo: migrate content to here

Latest revision as of 15:08, 30 October 2019

Content on this page has been migrated to Confluence here: https://confluence.hl7.org/display/FHIR/Managing+Overlap+Between+Resources

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