This page is part of the FHIR Specification (v0.0.82: DSTU 1). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions
This profile sets expectations for use of the Observation resource to record lab results associated with a patient within the Data Access Framework (DAF) Implementation Guide. This profile identifies which core elements, extensions, vocabularies and value sets must be Supported by DAF actors. For the definition of Supported please refer to DAF FHIR IG. The data elements identified by the profile are based on ONC 2014 Edition S&CC and DAF use cases.
Six Observation profiles are defined to cover the various kinds of result values that are generated by laboratories and Ask at Order entry ('AOE') questions. These profiles are:
These profile are referenced in the DAF DiagnosticReport profile for one or more lab test results. They are also referenced for ask at order ("AOE") questions, other clinically relevant questions and for reporting prior results when requesting a test order using the DAF DiagnosticOrder. Although not specified in this implementation, it may be used in other resources as well.
The mappings between the ONC 2014 Edition S&CC data elements and DAF data elements are captured in the table below, where the first column identifies the ONC 2014 Edition S&CC data element name, the second column maps the ONC 2014 Edition S&CC data elements to DAF data elements which are derived from ONC 2014 Edition S&CC standards and DAF use cases and lastly the third column identifies the mapping to FHIR resources and attributes.
The DAFResults profile mapping to Meaningful Use data elements and FHIR Resources are as shown below.
Meaningful Use Data Element Name | Mapping to Priority DAF Data Elements | FHIR Resource Mapping |
---|---|---|
Laboratory Result Value(s) | ||
Lab Test Name | Observation.name.coding.code | |
Lab Test Result | Observation.value[x](Code,Quantity,Ratio or other) | |
Lab Test Specimen collection date | Observation.applies[x] | |
Lab Test Result Available Date | Observation.issued | |
Lab Test Result Interpretation | Observation.interpretation | |
Lab Test Result Reference Range | Observation.referenceRange | |
Body Site used to collect specimen | Observation.bodySite[x] |
This profile relies on the following other profiles:
Profiles: | |
DAFResultObsCode | US Realm DAF laboratory result using CodeableConcept Data Type for non-numeric results |
DAFResultObsQuantity | US Realm DAF laboratory result using Quantity Data Type for numeric results |
DAFResultObsRange | US Realm DAF laboratory result using Range Data Type for numeric results |
DAFResultObsRatio | US Realm DAF laboratory result using Ratio Data Type for numeric results |
DAFResultObsOther | US Realm DAF laboratory result using one of Attachment|dateTime|Period|SampledData|string|timeData Type for results. |
DAFResultObsPanel | US Realm DAF laboratory panel observation |
The full list of supported search parameters are can be accessed at DAF Requestor conformance expectations and DAF Responder conformance expectations.
The following are example usage scenarios for the DAFResults profile:
Implementers need to be mindful of the following during their implementation
Using Right DAF Result profile: Implementers are advised to use the right DAFResult profile based on the value to be represented. For example, in case the value element is a codeableConcept implementers should use DAFResultObservationCode profile. Similarly for representing Quantity, Ratio and Other types of results the appropriate DAFResult profile listed above should be used.
Representing No Known Lab Results: No Known Lab Results will be represented using the DAFResultsList profile with no entries.
See DAF FHIR IG for implementation guidance common to all profiles.