Difference between revisions of "201701 Care Plan"
Line 9: | Line 9: | ||
[[Patient_Care | Patient Care Workgroup]] | [[Patient_Care | Patient Care Workgroup]] | ||
− | Healthcare Services Platform Consortium (HSPC) | + | [http://hspconsortium.org Healthcare Services Platform Consortium (HSPC)] |
==Justification== | ==Justification== | ||
<!--Why is this an important track to include in the connectathon - include implementer need, impact on ballot, FMM readiness of the resources, etc. --> | <!--Why is this an important track to include in the connectathon - include implementer need, impact on ballot, FMM readiness of the resources, etc. --> | ||
− | This track is intended to advance the maturity of FHIR resources for care planning (i.e., [http://hl7.org/fhir/2016Sep/careplan.html | + | This track is intended to advance the maturity of FHIR resources for care planning (i.e., [http://hl7.org/fhir/2016Sep/careplan.html CarePlan], [http://hl7.org/fhir/2016Sep/careteam.html CareTeam] and [http://hl7.org/fhir/2016Sep/goal.html Goal]) and to document industry best practices for improving care coordination using shared care plans. This work will inform the development of a more comprehensive US Realm implementation guide and profiles for care planning based on FHIR release 3. |
+ | |||
+ | Short paragraph intro to benefits of shared care plans and links to ONC initiatives. | ||
+ | |||
+ | SMART on FHIR applications for provider and patient care planning. APIs vs document-based care coordination. | ||
+ | |||
+ | Relationship to DAF-Core / US Core IG and to Argonaut. | ||
Participants using both FHIR DSTU-2 and STU-3 are welcome! | Participants using both FHIR DSTU-2 and STU-3 are welcome! | ||
Line 22: | Line 28: | ||
::Zulip: Dave Carlson | ::Zulip: Dave Carlson | ||
+ | ==Expected participants== | ||
+ | The following organizations have indicated an interest in participating in this track: | ||
− | + | * VA – Dave Carlson | |
− | + | * HSPC – Dave Carlson | |
− | * Dave Carlson – | + | * 'Your organization here!' |
− | * | ||
==Roles== | ==Roles== | ||
Line 35: | Line 42: | ||
===Care Plan Responder=== | ===Care Plan Responder=== | ||
+ | * ''TODO'' link to HSPC sandbox with test data. | ||
===Care Plan Creator=== | ===Care Plan Creator=== | ||
+ | * from ProcessDefinition for care pathways | ||
===Care Team Requestor=== | ===Care Team Requestor=== | ||
− | + | * ""TODO"" link to HSPC sandbox with test data. | |
===Care Team Responder=== | ===Care Team Responder=== |
Revision as of 23:40, 10 October 2016
Care Plan and Care Team
Submitting WG/Project/Implementer Group
Healthcare Services Platform Consortium (HSPC)
Justification
This track is intended to advance the maturity of FHIR resources for care planning (i.e., CarePlan, CareTeam and Goal) and to document industry best practices for improving care coordination using shared care plans. This work will inform the development of a more comprehensive US Realm implementation guide and profiles for care planning based on FHIR release 3.
Short paragraph intro to benefits of shared care plans and links to ONC initiatives.
SMART on FHIR applications for provider and patient care planning. APIs vs document-based care coordination.
Relationship to DAF-Core / US Core IG and to Argonaut.
Participants using both FHIR DSTU-2 and STU-3 are welcome!
Proposed Track Lead
- Dave Carlson – VA
- E-mail: Dave.Carlson@BookZurman.com
- Zulip: Dave Carlson
Expected participants
The following organizations have indicated an interest in participating in this track:
- VA – Dave Carlson
- HSPC – Dave Carlson
- 'Your organization here!'
Roles
Please include information here regarding how much advance preparation will be required if creating a client and/or server.
Care Plan Requestor
Care Plan Responder
- TODO link to HSPC sandbox with test data.
Care Plan Creator
- from ProcessDefinition for care pathways
Care Team Requestor
- ""TODO"" link to HSPC sandbox with test data.
Care Team Responder
Scenarios
Scenario Step 1 Name
- Action:
- Precondition:
- Success Criteria:
- Bonus point: