Тематический план

• Use FHIR in 10 Minutes with Unified Care Record

  Use FHIR in 10 Minutes with Unified Care Record

  Content Type
  Exercise

  Duration
  10m

  Level
  Introductory

  InterSystems HealthShare Unified Care Record® creates a unified, community-wide health record as the foundation for coordinated, value-based care and population health management. Regardless of the original format of data, HealthShare allows other applications to make HL7® FHIR® requests, ensuring efficient delivery of care.

  With Unified Care Record and FHIR, you can:

  • Optimize application performance by providing access to all data from multiple electronic medical records (even from legacy interfaces) as FHIR resources.
  • Aggregate data for an individual or population as a FHIR representation.
  • Use the built-in FHIR repository to allow applications to leverage all data for patient care, value-based care, quality improvement, research, and other use cases.
  • Optimize development time by requesting the capability statement to quickly identify FHIR support within Unified Care Record.

  Learning Objectives

  • Make a FHIR request to retrieve patient data from Unified Care Record.
  • Retrieve the FHIR capability statement to see available data and functionality.
  • Explore patient observations, including BMI data.

  
  

  Prerequisites

  • None

  
  
  

  Watch the video to learn about Unified Care Record or get hands-on with FHIR searches in the exercise below!
  

  
  

  • Mark me "complete" for this exercise.

    Недоступно, пока не выполнено: Ваше поле Индивидуальный номер не пустое
• Launch Unified Care Record

  Launch Unified Care Record

  When you are ready to try the below exercise, you can get immediate access, free of charge, with no download required.

   You must be logged in to launch this Unified Care Record lab.

  • Log in with your existing account.
  • Don't have an InterSystems account? Create a new account.

  
  
• Start the Exercise

  Start the Exercise

  Imagine you are building an application that will make it easier for clinicians to help patients with diabetes. To do this, you need to request and display results for hemoglobin a1c tests, which measure the average level of blood sugar over the past two to three months.

  In this exercise, you will make a FHIR request to Unified Care Record for a sample patient. After testing these queries, you could later build them into your application.

  Easily make a FHIR request to retrieve data from Unified Care Record

  1. Verify the Virtual Machine has launched, starting a demo instance of Unified Care Record on an Ubuntu system.
  2. Click the fit-to-screen icon () at the top.
     In this VM, your credentials will allow you to make FHIR requests but do not provide access to HealthShare management pages.
  3. Open Postman using the icon () on the left.
     We will first request the Patient resource for Alec DuBuque and later add to it.
  4. Set the following:
     • Transaction Method: GET
     • Request URL: http://ubuntu:52773/csp/healthshare/hsods/fhir/r4/Patient?family=DuBuque&given=Alec
  5. Add headers:
     • Authorization: Select Basic Auth. Enter the following credentials:
     • Username: fhir
     • Password: demo7
     • Accept: application/fhir+json
     • Content-Type: application/fhir+json;charset=UTF-8
  6. Send the request and examine the response payload bearing Alec DuBuque’s Patient resource in a FHIR bundle. Note that Alec's Patient Resource ID is 100000005.
     Now, let's perform another query to obtain Alec's five most recent HbA1c results. Here we are retrieving Observation resources that satisfy several search parameters.
  7. Update the previous query and replace the resource query with:

     Observation?patient=100000005&code=4548-4&_sort=-date&_count=5

  This FHIR query makes use of the following four search parameters on the Observation resource to obtain the desired results:

  • patient: A resource-specific parameter for specifying the patient subject of a given Observation resource. The Patient resource id in the query corresponds to the patient record we want to retrieve.
  • code: A resource-specific parameter for indicating the observation type code. In this case, 4548-4 used in the FHIR query is the LOINC code for Hemoglobin A1c in blood.
  • _sort: A standard parameter for sorting, with the optional hyphen (-) prefix indicating decreasing order (in STU3 syntax). The -date sort rule used in this query sorts resources based on their effectiveDateTime values, starting with the most recent Observation.
  • _count: A standard parameter for specifying how many results are to be returned by the FHIR server in a single page. Note that the total field returned in the FHIR bundle displays the total number of results before applying _count.

  For more information on performing searches using the FHIR RESTful API, please consult the online FHIR specification.

  
  

  Retrieve FHIR Capability Statements to design additional queries
  

  Want to try other FHIR requests? You can retrieve the full FHIR capability statements to see what's supported for both STU3 and R4 to continue to explore FHIR with Unified Care Record.

  1. Using Postman, send the following request to view the FHIR STU3 capability statement. STU3 is an earlier version of HL7 FHIR.
     Transaction Method: GET
     URL: http://ubuntu:52773/csp/healthshare/hsods/fhir/stu3/metadata
     Headers:
     • Accept: application/fhir+json;
     • Content-type: application/fhir+json;charset=UTF-8
  2. Retrieve the capability statement for the FHIR R4 server. R4 is the latest version of FHIR and the first with normative resources. In Unified Care Record, both the R4 and STU3 routes draw from the same data.
     Transaction Method: GET
     URL: http://ubuntu:52773/csp/healthshare/hsods/fhir/r4/metadata
     Headers:
     • Accept: application/fhir+json;
     • Content-type: application/fhir+json;charset=UTF-8
  3. Compare the results from the STU3 and R4 capability statements. You can learn more about capability statements on the HL7 website.
  
  

  Challenge: Retrieve BMI data
  

  Use the capability statement and the syntax for FHIR queries above to challenge yourself. See if you can make a FHIR request and get Alec's Body Mass Index (BMI).
  
  

  Body Mass Index, often abbreviated BMI, is defined as the body mass (weight) divided by the square of the body height, and is usually expressed in units of kg/m2, resulting from mass in kilograms and height in meters. Commonly accepted BMI ranges are underweight: under 18.5 kg/m2, normal weight: 18.5 to 25, overweight: 25 to 30, obese: over 30. Source: https://en.wikipedia.org
• What's Next?

  What's Next?

  • Learn how to store and share FHIR data with Unified Care Record (learning path, 2h 45m).

  • Share Your Feedback!