This wiki has undergone a migration to Confluence found Here

Difference between revisions of "CareTeam"

From HL7 Argonaut Project Wiki
Jump to navigation Jump to search
m
Line 3: Line 3:
 
The Argonaut CareTeam provides the API documentation for searching for and fetching a patient's current care team list using the [http://hl7.org/fhir/DSTU2/careplan.html CarePlan resource].  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).
 
The Argonaut CareTeam provides the API documentation for searching for and fetching a patient's current care team list using the [http://hl7.org/fhir/DSTU2/careplan.html CarePlan resource].  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).
  
=== Usage Overview ===
+
== Usage Overview ==
 
<!--6-9 test items  e.g. A client has connected to a server and fetched patient demographics via GET /Patient/{id}-->
 
<!--6-9 test items  e.g. A client has connected to a server and fetched patient demographics via GET /Patient/{id}-->
 
===Clients===
 
===Clients===

Revision as of 07:42, 15 April 2016

Back to Argonaut Implementation Guide

Introduction

The Argonaut CareTeam provides the API documentation for searching for and fetching a patient's current care team list using the CarePlan resource. 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).

Usage Overview

Clients

Servers

  • A server is capable of returning a patient's current care team list using [[ GET/CarePlan?Patient/[id]&status=current$_include=CarePlan:participant.member[choice of Practitioner | RelatedPerson | Patient | Organization]]]
  • 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). These are presented below in simple human-readable explanations along with sample data to demonstrate the requirements.

Each CarePlan must have:

  1. a patient
  2. a status

Each CarePlan should have:

  1. a participant role if participant is present
  2. either a complete name or a reference to participant
    • Note the participant can be
      • a practitioner (doctor, nurse, therapist)
      • the patient
      • a relative or friend or guardian
      • an organization
CarePlan Resource Example

Quick Start

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


GET/CarePlan?Patient/[id]&status=current$_include=CarePlan:participant.member[choice of Practitioner | RelatedPerson | Patient | Organization]

Support: Mandatory to support search by patient.

Implementation Notes: Search for all current care team members for a patient. Fetches a bundle of all current CarePlan resource(s) and the participants referenced by the CarePlan resource(s) for the specified patient (how to search by reference) (how to search by token) (how to include referenced resources in search result).

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/CarePlan?patient=1137192]

Open Issues

Issues for the vitals IG have been identified and tracked HERE

TODO -

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