Summary

  • 1 minute

In this module, you learned about the importance of interoperability (the ability of computer systems or software to exchange and use information) in the health and life sciences industry. You explored the FHIR service, its capabilities, and use cases. Additionally, you explored the FHIR service data and technical architecture and the integration with Healthcare data solutions in Microsoft Fabric.

You learned about the Fast Healthcare Interoperability Resources (FHIR®) standard for health data storage and exchange and how all FHIR resource types are defined with a set of elements. You also discovered how each resource instance on a FHIR server is distinguished with a unique set of information that's carried in those elements.

Additionally, you learned about the GitHub repositories for the open-source versions of Microsoft health data tools that can be beneficial if you're developing applications. Developers can take advantage of these open sources to build more secure, user-facing applications that interact with FHIR data.

You can explore the HL7 Implementation Guides with the following references:

  • FHIR Implementation Guides include associated documentation to clarify usage. Multiple implementation guides are available in FHIR to handle different tasks, such as constraints, customized operations, and management of bulk transfer of data. For more information, see Implementation Guide Registry.

  • HL7 FHIR® US Core - One implementation guide that you should become familiar with is the HL7 FHIR® US Core Implementation Guide full guide, Centers for Medicare & Medicaid Services (CMS) and the ONC Final Rule.

  • US Core profiles - Each profile has requirements, and guidance is provided. For more information, see the list and full details.

  • US Core Responder actor capabilities - US Core Server Capability Statement

  • The US Core Server Capability Statement in the FHIR documentation includes details for each profile. For example, you can review the patient profile to understand what's expected of a compliant client and server to ensure interoperability.