Page tree
Skip to end of metadata
Go to start of metadata

view HL7 India Youtube Channel

Track Name

COVID19 Teleconsultation Track: Pandemic and Beyond


  1. To further FHIR standards among the programmer community, whether they are in healthcare or not. 
  2. To test out our concept and demonstrate a standards based Telemedicine Exchange Platform
  3. Purpose & Takeaways for the Participants attending the NCII Track:
    1. What’s the purpose of hosting this connectathon track?
      To further FHIR standards among the programmer community, by identifying India Specific Scenario of health interoperability and enable the ecosystem to adopt standards that lead to successful and meaningful implementations.
    2. What do you hope to achieve?
      To demonstrate power of innovative collaboration that is the core of NCII and begin the transformation starting with a Telemedicine Exchange Platform

      This track will use R4 version of FHIR(Participants from the FHIR Starter Track can come to COVID19 Teleconsultation Track after completing 4 FHIR Starter Sessions)
  4. Review the COVID19 Teleconsultation Track Details here:

About the COVID19 - Teleconsultation Track by Aniruddha Nene

Intended Audience

  1. Telemedicine Platform Companies, Hospitals, Clinics
  2. Developers / Architects
  3. Product manager
  4. Test engineer/Manager
  5. Students/learner (Health Informatics)
  6. Hospitals

Audience Feedback

Please make use of this form to share your feedback about the track: 

Related Tracks

  1. FHIR Starter Track
  2. FHIR India Profiling Track

Track Orientation & Schedules

30th May, 2020Track Kick-offSlides Here
15th June, 2020Track Standup W1 - Day 1
16th June, 2020Track Standup W1 - Day 2W1-Day 2 - Teleconsultation Track - HL7 India Connectathon.pdf
17th June, 2020Track Standup W1 - Day 3W1-Day 3 - Teleconsultation Track - HL7 India Connectathon.pdf
18th June, 2020Track Standup W1 - Day 4Activities being updated by Participants
19th June, 2020Track Standup W1 - Day 5Weekend Update and Next Steps
20th June, 2020Track Standup W1 - Day 6
21st  June, 2020SUNDAY OFFNo Meeting
22nd June, 2020Track Standup W2 - Day 7
23rd June, 2020Track Standup W2 - Day 8

Invitation to connect & discuss Hans on V2-FHIR mappings, project and track. This an opportunity to interact & learn from a Industry & HL7 veteran and #influencer .

About Buitendijk Hans
Hans is currently Co-Chair - Orders & Observations work group at HL7. He also leads the V2-to-FHIR project efforts among several other initiative.
Hans is a HL7 Veteran with over 26 years of association with HL7 in several key roles.
He works at Cerner Corporation as Director, Interoperability Strategy.

24th June, 2020Track Standup W2 - Day 9

Scenario 1:

  1. TSO will raise the ticket to the Teleconsultation Server
  2. Resources included in the Resource Bundle
    1. Task
    2. Patient
    3. Observation
    4. Condition
  3. On submission Task Status will be set as "Requested"
  4. TPO will request for open tasks
    1. Each TPO can request for only one task for each request (use query count = 1)
    2. If active task available, TPO updates the task reference number status = "In-Progress"
    3. TPO will query the associated patient information from the server, once the task has been locked (marked "In-Progress")
25th June, 2020Track Standup W2 - Day 10
26th June, 2020Track Standup W2 - Day 11
27th June, 2020Track Standup W2 - Day 12
28th June, 2020Track Standup W2 - Day 13 - SUNDAYThe Scenario 1 & Resource Identified
29th June, 2020Track Standup W3 - Day 14The Scenario 1 Presented - TSO & TPO Actors Identified
30th June, 2020Track Standup W3 - Day 15resource bundle shared, that will be used for the Connectathon
1st July, 2020Track Standup W3 - Day 16resource bundle shared (XML & JSON), that will be used for the Connectathon
2nd July, 2020Track Standup W3 - Day 17


  1. HAPI FHIR Server (R4) - Link
  2. COVID19 Teleconsultation Track Artefacts - Google Drive Link | COVID19 Teleconsultation Track - Github
    1. Track Task List
    2. Resource Data
    3. Sample Resources for the Track
    4. Scenario 1 Resource Mapping
    5. Scenario 1 Workflow Diagram
    6. Scenario 1 Solution Overview
    7. Scenario 1 Flow Sequence

Participants Tools

  1. Connection details to the HAPI FHIR Server
  2. FHIR Clients, Company based Open Source Applications
  3. Postman Client: Please download the POSTMAN Client on your respective systems:
  4. Fred:

  5. clinFHIR Patient Viewer:

  6. LHC FHIR Tools
  7. LHC Form Builder Tool:
  8. FHIR Client:
  9. INTEROpen, NHS:

Track Leads

Manick Rajendran

Aniruddha Nene

Kumar Satyam

Manish Sharma

Divyaratna Chiniwal

Ritika Jain

Track PoC Build Team


Divyaratna Chiniwal

Ritika Jain

Aparna Bhumkar

Raksha R

Bhaskar Krishnamurthy
Anurag Aggarwal
Raunaq Pradhan
Siriram Kailasam
Santosh Jami
Raja Sekhar Kommu 
Satya Itharaj

Track Participants 


Divyaratna Chiniwal

Ritika Jain

Aparna Bhumkar

Raksha R

Aditi Verma

Raj Kumar

Chinmay Athaley

Bhaskar Krishnamurthy
Jayakanth Kesan
Praveen Shivaprasad
Anurag Aggarwal
Raunaq Pradhan
Siriram Kailasam
Gokul Raj R
Astha Rai
Shilpa A
Suyash Choudhary
Mohammad Ali
Srinivasa Rao P
Santosh Jami
Shilpa Kumar
Debabrata Parida
Aditya Kumar Singh
Raja Sekhar Kommu 
Satya Itharaj

Final Track Schedule

Date - TimeActivityDuration | LocationComments

Friday 03rd Jul, 2020 

3.00PM to 4.20PM

Attend the Connectathon Opening Ceremony and meetings

3 hours |

Keynote Track

The Keynote

Friday 03rd Jul, 2020 

4.30PM to 6.00PM

Teleconsultation Track PoC Setup with the Participants1.30 hours | 

Teleconsultation Track

We will identify the participants who will be playing the role of a TSO or a TPO

Identify if the participants will be creating a PoC application for the connectathon, or will be using one of the identified tools

The Team will enable the Participants setup for the PoC Demonstration

04th Jul, 2020

09.00 AM to 10.00AM

Common Session

1 hour |

Keynote Track

The Keynote

04th Jul, 2020

10.15AM to 05.00PM

Teleconsultation Track Participants Attend the FHIR Starter Track Sessions6.45 hours  | 

FHIR Starter Track

04th Jul, 2020

05.00PM to 07.00PM

Teleconsultation Track PoC Setup with the Participants2 hours | 

Teleconsultation Track

05th Jul, 2020

08.00AM to 10.45AM

Teleconsultation Track PoC Showcase with the Participants2.45 hours | 

Teleconsultation Track

05th Jul, 2020 

11.00AM to 12.00PM 

Common Session

1 Hour |

Keynote Track

The Keynote

Scenario 1: Patient Request for Teleconsultation

The concept talks about the ability of a patient to request for a teleconsultation by herself or by a telemedicine service organization TSO on her behalf, and the NCII Aggregator Service enables the patient to be connected with the first available doctor with a Telemedicine Platform Organisation in a single click, even if the TSO and TPO are two different entities

User Story - Feature - Create Service TicketResource
Raghu shows symptoms of COVID19. He has had no history travel in the past 14 days. Radhu places a call to the nearby primary health center, since the lock down is in effect.

The Physician/ ASHA (TSO) worker performs a check on her app and finds Raghu in the need of a Teleconsultation Visit with a doctor. She raises the request on her system to book a teleconsultation visit for Raghu.

Refer the Slide Deck at the top of this page to get the list of fields that will be applicable for the Patient Resource or review our data sheet here

Patient Related FHIR Resources Created, relevant to the TSO usecase and app capabilities

Patient (M) 1..1

Encounter (M) 1..1

Observation(O) 0..*

Condition (O) 0..*

QuestionnaireResponse (O) 0..*

Upon registration, the TSO app connects with the NCII Server and registers Service Ticket with the NCII ServerTask Resource Bundle Created with the reference to Patient Raghu
User Story - Feature - Poll for Open Service TicketResource
NCII Server now has open Service Tickets for various PatientsTask Resource
TPO - Telemedicine Provider Organisations connected with the NCII Server now request for open dynamic visits. TPOs will send a request to find Service Tickets that have been successfully "Accepted" by the NCII Server
Once a TPO finds one Accepted (Open) Ticket, the TPO will mark the status of that one service ticket as "In-Progress"

Task Resource. Status = In-Progress &

Task Reviewer and other relevant fields will be updated by the TPO Organisation that is accepting the task

Once the Task has been assigned, the NCII Server will ensure that the task is completed within an hour of allocationTask.lastModified

User Story - Feature - TPO Response to Service TicketResource
Once the TPO has accepted a Service Ticket, the Service Ticket will be displayed as a Dynamic and Urgent List on the TPO App for the COVID19 Assigned Doctors Team. When the patient Raghu is displayed on the Doctors "Dynamic Patients" list, the Doctor will click on that Service Ticket that has been pulled by the TPO into their App

Task Resource

Patient Resource with Patient Resource bundle displayed to the doctor with the information captured by the TPO

or eServiceTicket Task Bundle

The Doctor will now initiate a teleconsultation visit with the patient. Once the doctor clicks on the Consult Now with patient button on their app, a unique URL will be generated and sent to the Patient Raghu on his mobile number provided.Service Task Response
Raghu will click on the URL that has been sent by the TPO to him, and he gets connected with the TPO assigned Doctor instantly
After consulting the Patient, the TPO Doctor will record the Risk Assessment and provide a Document Reference to now mark the closure of the Service Ticket that had been created for Raghu

Patient, Risk Assessment, Document Reference, Observation

Task.Status - Completed

or eTeleconsultationVisit Bundle


Medication Prescription (Rx)

Map the relevant resources here:

Laboratory Service

Radiology Exam

Followup Appointment


view HL7 India Youtube Channel

  • No labels