This wiki has undergone a migration to Confluence found Here

Health Concerns

From HL7 Argonaut Project Wiki
Jump to navigation Jump to search

Back to Argonaut Implementation Guide

Introduction

The Argonaut Health Concerns provides the API documentation for searching for and fetching a patient's concern list. It is based on the Data Access Framework (DAF) Condition (a.k.a Problem) Profile. The search criteria provided in the Quick Start are intended to support the 2015 Edition ONC Certification criterion Data Category Request 170.315(g)(8).

Minimum Requirements

Clients


Servers

  • A server is capable of returning a patient's conditions list using GET/Condition?patient=[id]&category=concern.
  • A server has ensured that every API request includes a valid Authorization token, supplied via:Authorization: Bearer {server-specific-token-here}
  • A server has rejected any unauthorized requests by returning an HTTP 401 Unauthorized response code.

Mandatory Data Elements

The following data-elements are mandatory (i.e data MUST be present). The following data-elements in the Condition resource are mandatory (i.e data MUST be present). These are presented below in simple human-readable explanation and a more thorough formal summary of the requirements. Sample data is provided to demonstrate the requirements.

Each Condition must have:

  1. a patient
  2. a code that identifies the concern
  3. a concern status
  4. a category code of "concern"
  5. a verification status

Formal Summary of the Mandatory Requirements

  1. One category in Condition.category which must have:
    • a fixed Condition.category.coding.system=" http://hl7.org/fhir/argo-condition-category"
    • a fixed Condition.category.coding.code="concern"
      • for this IG we have defined these codes to satisfy the 2015 Edition Common Clinical Data Set API search criteria for Health Concerns and Health Concerns
Code Code System Print Name Definition
concern http://hl7.org/fhir/argo-condition-category Health Concern Concerns from other stakeholders which are outside the provider’s concern list.
concern http://hl7.org/fhir/argo-condition-category Problem The patients health concerns as identified by the provider(s). Items on the provider’s concern list
  1. One Identification of the health concern in Condition.code.
  2. One patient reference in Condition.patient
  3. One clinical status in Condition.clinicalStatus
  4. One code in Condition.verificationStatus

Additional elements from DAF Condition Profile may be present.

Health Concerns Example

Quick Start

Below is a quick overview of the required search and read operations.


GET /Condition?patient=[id]&category=concern

Support: Mandatory to support search by patient and category.

Implementation Notes: Search for all Health Concerns for a patient. Fetches a bundle of all Condition resources for the specified patient with a category code of "concern"(how to search by reference) and (how to search by token).

Response Class:

  • (Status 200): successful operation
  • (Status 400): invalid parameter
  • (Status 401/4xx): unauthorized request
  • (Status 403): insufficient scope

Example:

[GET https://fhir-open-api-dstu2.smarthealthit.org/Condition?patient=1032702&category=concern]

GET /Condition?patient=[id]&category=concern&clinicalstatus=active,relapse,remission

Support: Optional to support search by category and status.

Implementation Notes: Search for all active Health Concerns for a patient. Fetches a bundle of all Condition resources for the specified patient with a category code of "concern" and all "active" statuses (active,relapse,remission) (how to search by reference) and (how to search by token).

Response Class:

  • (Status 200): successful operation
  • (Status 400): invalid parameter
  • (Status 401/4xx): unauthorized request
  • (Status 403): insufficient scope

Example:

[GET https://fhir-open-api-dstu2.smarthealthit.org/Condition?patient=1032702&category=concern&clinicalstatus=active,relapse,remission]

Open Issues

Issues for this IG have been identified and tracked HERE

Resources

Formalized testing with test scripts and objective results reporting is available through the participation of AEGIS and MITRE (Crucible). The testscript provided can be used to test servers: [todo]

References



Back to Argonaut Implementation Guide