Difference between revisions of "CareTeam FHIR Resource Proposal"
| Line 13: | Line 13: | ||
| − | = | + | =CareTeam= |
<!-- Resource names should meet the following characteristics: | <!-- Resource names should meet the following characteristics: | ||
Revision as of 17:20, 21 January 2016
This page documents a Pending FHIR Resource Proposal
Contents
- 1 CareTeam
- 1.1 Owning committee name
- 1.2 Contributing or Reviewing Work Groups
- 1.3 FHIR Resource Development Project Insight ID
- 1.4 Scope of coverage
- 1.5 RIM scope
- 1.6 Resource appropriateness
- 1.7 Expected implementations
- 1.8 Content sources
- 1.9 Example Scenarios
- 1.10 Resource Relationships
- 1.11 Timelines
- 1.12 gForge Users
CareTeam
Owning committee name
Contributing or Reviewing Work Groups
FHIR Resource Development Project Insight ID
Pending (HJB: Either use an existing project it fits under, or need a new project statement.)
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.
