This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Difference between revisions of "CareTeam FHIR Resource Proposal"

From HL7Wiki
Jump to navigation Jump to search
Line 38: Line 38:
 
==FHIR Resource Development Project Insight ID==
 
==FHIR Resource Development Project Insight ID==
  
[http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?action=edit&ProjectNumber=1128]
+
[http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?action=edit&ProjectNumber=1128| Project 1128]
  
 
<!-- Please specify the id of your work group’s PSS for doing FHIR work.  (If submitted but not yet approved, just write “pending”.) The link to the PSS template can be found here: http://gforge.hl7.org/gf/download/docmanfileversion/6832/9398/HL7FHIR_DSTUballotPSS-20120529.doc -->
 
<!-- Please specify the id of your work group’s PSS for doing FHIR work.  (If submitted but not yet approved, just write “pending”.) The link to the PSS template can be found here: http://gforge.hl7.org/gf/download/docmanfileversion/6832/9398/HL7FHIR_DSTUballotPSS-20120529.doc -->

Revision as of 17:25, 21 January 2016



CareTeam

Owning committee name

Patient_Care

Contributing or Reviewing Work Groups

Patient_Administration


FHIR Resource Development Project Insight ID

Project 1128


Scope of coverage

The Care Team resource includes all the people and/or organizations of interest who participate in the coordination and delivery of care for a patient. This is not limited to clinicians/providers, but may include other caregivers such as family members, guardians, or others.

The Care Team, depending on where used, may include care team members specific to a particular care plan, an episode, an encounter, or may reflect all known team members across these perspectives.


RIM scope

Resource appropriateness

A Care Team reflects a data set that is related to other resources, e.g., Patient and CarePlan, describing a specific group of people or organizations that address one or more aspects of patient care.


Expected implementations

C-CDA and FHIR based CCDS focused APIs to access specific data sets will be the initial implementations, as well as other Care Plan related implementations.


Content sources

As this resource is introduced to separate it from CarePlan, rather than only being available for CarePlan, the data content is in part based on current CarePlan.Participant, as well as current C-CDA and Patient Administration requirements.


Example Scenarios

Resource Relationships

Refers to Person, Organization. Is referred by Care Plan, Patient, .....

Timelines

Ready for DSTU 3.0. with expected early adoption by those interested to satisfy US 2015 Edition CCDS API requirements.


gForge Users