Justification and Objectives
The numbers of service delivery encounters required by individuals as well as the failure to deliver
and coordinate needed services, are significant sources of frustration and errors and are drivers of
health care expenditures. Effective care planning and care coordination for patients with complex
health problems and needs are needed throughout the world. Care planning is needed to manage
medically complex and/or functionally impaired individuals as they interact with the health care
system. The idea is to support collaborative care, which can be achieved by maintaining and sharing a
centralized care plan for the patient. This enables real-time coordination of the care as the patient goes
on to receive care from multiple care providers/teams and care settings.
This track will use R4 version of FHIR.
FHIR Starter Track
Proposed Track Lead
Amina Shaikh email@example.com
A webinar will be hosted on June 20, 2020, to share further participation information about this track.
A FHIR server to post careplan resources and other related resources. This could be a
participant’s proprietary server or any publicly available test server.
HL7 V2 interface:
This interface will be needed only in the scenario where the patient’s careplan data
is in HL7 v2 format.
Scenario 1 – Map to IHE Dynamic Care Plan Profile
Action: Build and test various use cases such as diabetes, pregnancy plan, etc. Map the patient’s
encounter, episode, condition, care plan and care team data to relevant FHIR Resources. Publish
these resources to FHIR server.
Precondition: The participants should have the relevant care plan data either through a real time app
or through an EMR feed such as a set of HL7 V2 messages.
Success Criteria: The FHIR resources should be published successfully to the FHIR server.
Security and Privacy Considerations
The test data should not be from any production site. De-identified patient data should be used. Clients may
have to support the authentication mechanism of the FHIR server they intend to test with.
What are participants expected to do?
→ Expected to fulfil the Client and Server roles.
- A client that is capable of sending all the required resources to the FHIR server, contributing to the dynamic care planning.
- FHIR Server that is capable of accepting the resources that can help build dynamic care planning.
- Ensure the resources are conformant to a dynamic care plan.
What is the pre-requisite knowledge required from participants
→ Participants are required to know the FHIR fundamentals.
What is the execution plan? Broad activities spread thought the duration of the event.
Friday 3rd July afternoon 1-2 hours plan.
→ Basic client-server integration test to be performed.
Saturday 4th July Full day 6-7 hours plan
→ Testing out different use cases based on the below transactions. Success Criteria: 100% execution for all the below transactions.
- Create a Patient Resource.
- Create a Care Plan.
- Search Care Plan.
- Retrieve Care Plan.
- Update Care Plan.
- Create a Care Team.
- Search for Care Team.
- Search for Care Team.
- Update Care Team.
Note: Patient, Care Plan, Care Team are the mandatory resources to be supported for this track.
Other resources that may be useful are encounter, episode of care, activity definition, plan definition, condition.
Sunday 5th July – 1.5 hours. ( Report out & demonstration )
→ End-to-End integrated demonstration of minimum 2 use cases.
What tools would be required by participants?
→ Postman or any other REST simulators, Interface designing tool (Mirth Connect, Rhapsody etc..)
Who should participate in the track?
- Implementers who are interested in testing the Centralized Care Plan scenarios.
- FHIR Specification contributors looking to enhance or optimize the care plan/care team resource.
- Clinicians/Healthcare researchers looking to understand the real-time care plan management and provide inputs.
What is the take away for those who join, for India & for the larger FHIR community?
→ Execution and a better understanding of the Centralized care plan management use case.