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
 
(11 intermediate revisions by 2 users not shown)
Line 3: Line 3:
 
<div style="float: left;">[[Image:OpenHotTopic.GIF|35px| ]]</div>
 
<div style="float: left;">[[Image:OpenHotTopic.GIF|35px| ]]</div>
 
<div style="background:#F0F0F0">
 
<div style="background:#F0F0F0">
This page documents a [[:category:Pending FHIR Resource Proposal|Pending]] [[:category:FHIR Resource Proposal|FHIR Resource Proposal]]
+
This page documents a [[:category:Approved FHIR Resource Proposal|Approved]] [[:category:FHIR Resource Proposal|FHIR Resource Proposal]]
 
</div>
 
</div>
 
</div>
 
</div>
 
[[Category:FHIR Resource Proposal]]
 
[[Category:FHIR Resource Proposal]]
[[Category:Pending FHIR Resource Proposal]]
+
[[Category:Approved FHIR Resource Proposal]]
  
  
Line 30: Line 30:
  
 
[[Patient_Care]]   
 
[[Patient_Care]]   
 +
 +
==Committee Approval Date==
 +
2/18/2016
  
 
==Contributing or Reviewing Work Groups==
 
==Contributing or Reviewing Work Groups==
Line 38: Line 41:
 
==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]
+
Project 1128 [http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?action=edit&ProjectNumber=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 -->
Line 44: Line 47:
 
==Scope of coverage==
 
==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 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, patient themselves, 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.
 
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.
 +
 +
The Care Team exists to identify relationships and responsibilities.  The Care Team is neither an actor (the team as a whole does not 'perform') nor is the Care Team a target of action (i.e. CareTeam is not generally the focus of observations, though it's possible the CareTeam may be referenced by resources dealing with permissions)
 +
 +
gForge 9261 [http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_id=677&tracker_item_id=9261] has a draft of some of the proposed resource elements.
  
 
<!-- Define the full scope of coverage for the resource.  The scope must be clearly delineated such that it does not overlap with any other existing or expected resource.  The scope will be used to govern "what is the set of potential applications to consider when evaluating what elements are 'core' – i.e. in the 80%"
 
<!-- Define the full scope of coverage for the resource.  The scope must be clearly delineated such that it does not overlap with any other existing or expected resource.  The scope will be used to govern "what is the set of potential applications to consider when evaluating what elements are 'core' – i.e. in the 80%"
Line 95: Line 102:
  
 
==Example Scenarios==
 
==Example Scenarios==
 +
 +
* Set of individuals involved in helping to manage a patient's diabetes (GP, dietician, home care nurse, endocrinologist, patient, spouse)
 +
* Oncology care team for a particular patient
  
 
<!-- Provide a listing of the types of scenarios to be represented in the examples produced for this resource.  They should demonstrate the full scope of the resource and allow exercising of the resources capabilities (full element coverage, inclusion & omission of optional elements, repeating and singleton repeating elements, etc.) -->
 
<!-- Provide a listing of the types of scenarios to be represented in the examples produced for this resource.  They should demonstrate the full scope of the resource and allow exercising of the resources capabilities (full element coverage, inclusion & omission of optional elements, repeating and singleton repeating elements, etc.) -->
Line 101: Line 111:
  
 
Refers to Person, Organization.  Is referred by Care Plan, Patient, .....
 
Refers to Person, Organization.  Is referred by Care Plan, Patient, .....
 +
 +
Care Team is distinct from Group.  Group is patient-independent and identifies an undifferentiated set of individuals who are intended to be the target of one or more clinical activities (e.g. set of clinical trial participants, set of individuals impacted by or at risk of a public health event, a herd or flock, etc.)  Care Team is about establishing a set of relationships and roles and is specific to a particular Patient.
 +
 +
CareTeam is referenced by EpisodeOfCare and CarePlan to identify the set of individuals (and their respective roles) involved in providing the care defined by those two resources.
 +
 +
CareTeam may reference a condition.  CareTeam may have a type.
 +
 
<!-- What are the resources do you expect will reference this resource and in what context?
 
<!-- What are the resources do you expect will reference this resource and in what context?
  
Line 117: Line 134:
 
==gForge Users==
 
==gForge Users==
  
 +
Lloyd McKenzie
 
<!-- Identify the userids who will require commit access to gForge to maintain the resource.  (Ensure all users have registered for gForge.) -->
 
<!-- Identify the userids who will require commit access to gForge to maintain the resource.  (Ensure all users have registered for gForge.) -->

Latest revision as of 22:07, 24 February 2016



CareTeam

Owning committee name

Patient_Care

Committee Approval Date

2/18/2016

Contributing or Reviewing Work Groups

Patient_Administration


FHIR Resource Development Project Insight ID

Project 1128 [1]


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, patient themselves, 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.

The Care Team exists to identify relationships and responsibilities. The Care Team is neither an actor (the team as a whole does not 'perform') nor is the Care Team a target of action (i.e. CareTeam is not generally the focus of observations, though it's possible the CareTeam may be referenced by resources dealing with permissions)

gForge 9261 [2] has a draft of some of the proposed resource elements.


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

  • Set of individuals involved in helping to manage a patient's diabetes (GP, dietician, home care nurse, endocrinologist, patient, spouse)
  • Oncology care team for a particular patient


Resource Relationships

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

Care Team is distinct from Group. Group is patient-independent and identifies an undifferentiated set of individuals who are intended to be the target of one or more clinical activities (e.g. set of clinical trial participants, set of individuals impacted by or at risk of a public health event, a herd or flock, etc.) Care Team is about establishing a set of relationships and roles and is specific to a particular Patient.

CareTeam is referenced by EpisodeOfCare and CarePlan to identify the set of individuals (and their respective roles) involved in providing the care defined by those two resources.

CareTeam may reference a condition. CareTeam may have a type.


Timelines

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


gForge Users

Lloyd McKenzie