Capturing Data with Forms

Collecting data is often the first step of any medical visit. The various forms, documents, and questionnaires needed by a clinic may differ based on their needs, but will always exist as an initial and crucial point of contact. Whether it’s insurance paperwork or a patient history questionnaire, quick and easy access to patient information is the backbone of expedient care.

Open Postman

Objective of this Collection

We’ll explore FHIR’s mechanism for describing clinical forms, the Questionnaire resource, and the additional capabilities enabled by Commure’s support for the Structured Data Capture (SDC) specification. The collection will demonstrate how to request forms to be partially-filled with answers from existing data and how new or updated information in a form can be turned into the appropriate FHIR resources.

Scenario Summary

In this scenario, a provider will be filling out a digital form to capture a patient’s insurance information.

First, the provider uses a search interface to find the patient by name, then selects to start a new response to an insurance coverage form. The client application uses the extended operation Questionnaire/\$populate, which returns a partially-filled QuestionnaireResponse. Once completed, the extended operation QuestionnaireResponse/\$extract is invoked for the completed form. This returns a new or updated Coverage resource that is submitted by the application, ensuring that the data is available in the expected record.

FHIR Concepts Covered

FHIR offers a very effective set of resources and tools to work with questionnaires. The scenario presented here is a simplified example to introduce FHIR’s resources. We will interact with the following resources: Questionnaire (a specification of the content and behavior of a form; aka “form template”), QuestionnaireResponse (answers to questions defined by a Questionnaire)

Additionally, this scenario provides an introduction to:

  • The extended operation Questionnaire/$populate, to pre-fill data into a form.
  • The extended operation QuestionnaireResponse/$extract, to create or update resources from answers to questions in a form.
  • Basic FHIR search queries to find a patient by name & retrieve associated records .


To navigate a scenario using the Postman collection you will need to

  1. Sign in here and accept Commure’s Terms and Conditions.
  2. Authenticate (To have more information about it read the postman documentation, our documentation or see our authentication collection).
  3. Set up the initial FHIR data you need using the first request of the collection
  4. 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