DSTU2 Ballot Source

This page is part of the FHIR Specification (v0.5.0: DSTU 2 Ballot 2). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions

4.21.14 U.S. Data Access Framework (DAF) DiagnosticReport Profile (Profile)

4.21.14.1 Scope and Usage

This profile sets expectations for use of the DiagnosticReport resource to record diagnostic reports 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. 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.

Note: In the context of DAF, DAFDiagnosticReport profile is limited to be used only to group or organize Laboratory Result observations.

4.21.14.2 Meaningful Use Data Element Mapping

The DAFDiagnosticReport 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 Test(s)
Diagnostic Report Code/Name DiagnosticReport.name
Diagnostic Test Category DiagnosticReport.serviceCategory
Diagnostic Report Diagnosis DiagnosticReport.codedDiagnosis
Diagnostic Report Conclusion DiagnosticReport.conclusion

4.21.14.3 Boundaries and Relationships

This profile relies on the following other profiles:

  • DAFPatient which defines DAF Patient profile is used by DAFDiagnosticReport profile to refer to patients.
  • FHIR Extensibility defines how extensions can be applied to FHIR resources and data types. Specifically the data-absent-reason extension can be used to code data elements with missing information when appropriate. See DAF FHIR IG for additional guidance.

4.21.14.4 Content

Profiles:
DAFDiagnosticReportDAF Diagnostic Report

4.21.14.4.1 Search Parameters

The full list of supported search parameters are can be accessed at DAF Requestor conformance expectations and DAF Responder conformance expectations.

4.21.14.4.2 Example Usage Scenarios

The following are example usage scenarios for the DiagnosticReport profile:

  • Query for diagnostic reports belonging to a Patient
  • Query for all patients who have had a specific diagnostic test report

4.21.14.4.3 Profile specific implementation guidance

There is no additional profile specific implementation guidance, please refer to DAF FHIR IG for implementation guidance common to all profiles.