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.3.13 U.S. Data Access Framework (DAF) Condition (a.k.a Problem) Profile (Profile)

4.3.13.1 Scope and Usage

This profile sets expectations for use of the Condition resource to record conditions,problems,symptoms and findings 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.

4.3.13.2 Meaningful Use Data Element Mapping

The DAF Condition 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
Problems
Problem Type Condition.category
Problem code Condition.code
Problem Description Condition.text
Date when Problem was documented Condition.dateAsserted
Age at onset of Problem Condition.onsetAge
Problem Severity Condition.severity

4.3.13.3 Boundaries and Relationships

This profile relies on the following other profiles:

  • DAFPatient which defines DAF Patient profile is used by DAFCondition 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.3.13.4 Content

Profiles:
DAFConditionDefines constraints and extensions on the condition resource for use in querying and retrieving patient's information related to problems which includes conditions, findings, symptoms etc.

4.3.13.5 Search Parameters

Search parameters defined by this package. See Searching for more information about searching in REST, messaging, and services.

NameTypeDescriptionPathsSource
abatedstringSearch based on Condition's status of resolvedf:Condition/f:abatementBooleanXML / JSON
agenumberSearch based on Condition onsetAgef:Condition/f:onsetAgeXML / JSON
concernStatustokenSearch by status of the Condition ConcernXML / JSON

4.3.13.5.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.3.13.5.2 Example Usage Scenarios

The following are example usage scenarios for the DAF Condition profile:

  • Query for a Patient's problems
  • Query for all patients who have had a specific condition,problem or finding
  • Query for problems experienced by patients during a time period
  • Query for problems based on severity

4.3.13.5.3 Profile specific implementation guidance

Implementers need to be mindful of the following during their implementation

    Representing No known Problems: No known Problems will be represented using the DAFProblemList profile with no entries.

    See DAF FHIR IG for implementation guidance common to all profiles.