Care teams are groups of primary care staff members who collectively take responsibility for a set of patients. Care teams blend multidisciplinary skills, focusing several people’s insights, rather than a single physician’s, on each patient’s problems (AHRQ). A care team may consist of nurses, physicians, medical assistants, schedulers, and more. Care teams need efficient and secure tools in order to collaborate effectively and deliver better patient care.Open Postman
Objectives of this Collection
- Review how Commure’s FHIR® API can help you create applications to allow clinicians to view their patient lists, read, write, and share notes about individual patients.
- Review the basic concepts of FHIR.
This collection goes through the following user journey:
- A doctor uses a front end FHIR client application to view their care teams (via the CareTeam resource).
- The doctor selects a specific care team.
- The doctor selects a group of patients that belong to a specific care team (via the Group resource).
- The doctor selects a patient.
- The doctor reads the patient’s information and other doctors’ notes on the patient (via the ClinicalImpression resource).
- The doctor adds a new note to the patient (via the ClinicalImpression resource).
FHIR Concepts covered
FHIR offers a very effective set of resources to manage patients and groups of patients. The scenario presented here is a simplified example to introduce FHIR’s resources. We will interact with the following resources: Patient, Group, CareTeam, Practitioner, PractitionerRole, ClinicalImpression
To navigate a scenario using the Postman collection you will need to
- Sign in here and accept Commure’s Terms and Conditions.
- Authenticate (To have more information about it read the postman documentation, our documentation or see our authentication collection).
- Set up the initial FHIR data you need using the first request of the collection
- 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:
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 https://dashboard-99750511.developer.commure.com/smart/dashboard/ 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
- Callback url: http://localhost:1234/callback.
- Auth url:
- Access Token url:
- 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”
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.
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 email@example.com.