STU 2 Ballot

This page is part of the Data Access Framework (v1.6.0: STU 2 Ballot 1) based on FHIR v1.6.0. . For a full list of available versions, see the Directory of published versions

D.21.0 U.S. Data Access Framework (DAF) Vital Signs Profile

D.21.0.1 Scope and Usage

This profile sets expectations for use of the Observation resource to record Vital Signs of a patient within the DAF FHIR IG. 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.

D.21.0.2 Meaningful Use Data Element Mapping

The DAF-VitalSigns profile mapping to Meaningful Use data elements and FHIR Resources are as shown below. For an overview of how the DAF profiles and data elements were derived from ONC 2014 Edition S&CC please refer to DAF FHIR IG data mapping section.


Meaningful Use Data Element Name Mapping to Priority DAF Data Elements FHIR Resource Mapping
Vital Signs
Patient for whom Vital Signs are being measured Observation.subject
Vital Sign being Measured Observation.name
Vital Signs value Observation.valueQuantity
Vital Signs reference range Observation.referenceRange

D.21.0.3 Boundaries and Relationships

This profile relies on the following other profiles:

  • DAF-Patient is used by DAF-VitalSigns profile to refer to patients.
  • DAF-Encounter is used by DAF-VitalSigns profile to refer to encounters during which the vital signs measurements were captured.
  • 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.

D.21.0.4 Content

Profiles:
DAF-VitalSignsDefines constraints and extensions on the Observation resource for use in querying and retrieving Vital Signs information.

D.21.0.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.

D.21.0.4.2 Example Usage Scenarios

The following are example usage scenarios for the DAF-VitalSigns profile:

  • Query for vital signs of a particular patient
  • Query for all patients whose vital signs are out of the reference range
  • Query for patients with a particular type of vital sign measurement

D.21.0.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.