Telehealth Visit

Telehealth is the use of digital technology and communication in order to create, manage and obtain healthcare services electronically. Telehealth capabilities have provided critical access to care throughout the COVID-19 global health crisis. And in a post-pandemic world, telehealth will not only continue to support greater access to care for more people, but will give patients the optionality and convenience of care that they have now come to expect.

Open Postman

Objective of this Collection

Understand how Commure’s FHIR API can help you create an app to manage a telehealth visit, from appointment scheduling and prescribing medication to establishing a follow-up appointment.

Scenario Summary

In this scenario, you will understand how a telehealth visit is managed from the moment the appointment is scheduled days before the visit, to the processes that occur on the day on the appointment and the appointment itself. The scenario happens in the following three moments:

1. Appointment Scheduling:

Days to months before the patient’s visit, the Department Coordinator schedules appointments. The department coordinator knows all the department’s doctor’s schedules and availabilities. The Department Coordinator goes through the following journey:

1.1 The department coordinator checks the schedule.

1.2 The department coordinator creates an appointment.

1.3 When the patient and the doctor confirm the appointment, the system adds a generated secure meeting link to the appointment.

2. Clinic Flow Management:

On the day of the appointment, a Clinic Coordinator confirms the status of the appointments, prepares the patient for the visit, and informs updates. A Clinic Coordinator is responsible for ensuring the clinic flows smoothly, timely and performs the following user journey:

2.1 The care coordinator sees the status of visits.

2.2 The care coordinator assures that the patient fills out a pre-visit form.

2.3 The care coordinator informs the doctor of any updates.

3. Outpatient visit:

During the appointment, the doctor reviews the patient’s history, writes notes, requests the next appointment, orders a prescription, and closes the encounter. The doctor performs the following journey:

3.1 The doctor reviews the patient’s information.

3.2 The doctor and patient meet during the scheduled appointment.

3.3 The doctor prescribes a medication for the patient and requests a follow-up appointment.

Introducing FHIR

Fast Healthcare Interoperability Resources (FHIR) is a standard describing data formats and elements and an application programming interface for exchanging electronic health records. The standard was created by the Health Level Seven International (HL7®) health-care standards organization.

FHIR Concepts covered

FHIR offers a very effective set of resources to manage medical appointments. The scenario presented here introduces select FHIR resources and telehealth appointment workflows. We will interact with the following resources:

Patient, Practitioner, Schedule, Slot, Appointment, Medication Statement, Encounter, Endpoint, QuestionaireResponse, Condition, FamilyMemberHistory, Observation, Procedure, ServiceRequest, MedicationRequest.


To navigate a scenario using the Postman collection, you will need to have an existing Commure developer account.

  1. Sign in here and accept Commure’s Terms and Conditions.
  2. Import this collection to our Postman client (Click in the run in postman button in the top of this page).
  3. Authenticate (To have more information about it read the postman documentation, our documentation or see our authentication collection).
  4. Set up the initial FHIR data you need using the first request of the collection
  5. Go through the user journey performing each request in the collection

How to authenticate

Once you are signed in to an existing account, there are two ways to authenticate with Commure’s Server:

Alternative A:

Click the “View more actions” button of the Collection > Click “Edit” > Go to the variables tab and update only the tenant-id field (both initial value and current value) The tenant-id is the suffix on the baseurl when you sign in to the Commure’s Developer Platform. For example: in the tenant id is: 99750511. After updating this field please click “Update” at the bottom right corner of the window.

Now click again the “View more actions” button of the Collection > Click “Edit” > and this time, go to the authorization tab > select Oauth2 as the authorization method > Click “Get New Access Token” > Fill the fields with your tenant information.

Remember to remove the blank space between the Curly braces { {tenant-id}}

  • Callback url: http://localhost:1234/callback.
  • Auth url: https://api-{ {tenant-id}}
  • Access Token url: https://api-{ {tenant-id}}
  • client-id: smart_hello_world
  • Scope: openid email
  • Leave Client Secret and State empty.

After filling in the details, please Click in “Request Token” > In the next window Click “Use Token” > Once that window closes please click “Update”

Alternative B:

In your browser go to the /auth endpoint, and get the authorization token, then use the token as a bearer in every request you want to make to our servers.

Note: If you get a 404 SSL error, you forgot to set the tenant-id variable on the collections variables, or you have a wrong base url.

About us

Commure is building a system to accelerate healthcare software innovation. We believe that better software for doctors, nurses and patients - and ultimately for the healthcare system as a whole - will come from responsibly connecting the top minds in technology, medicine and design.


When using this collection you agree to Commure’s terms and conditions found here.


If you need help setting up, don’t hesitate to write us at