Healthcare records are increasingly becoming digitized. As patients move around the healthcare ecosystem, their electronic health records must be available, discoverable, and understandable. Further, to support automated clinical decisions and other machine-based processing, the data must also be structured and standardized. This is becoming a matter of interest for institutes such as government agencies and regional bodies, and we are already seeing rules and regulations come into action. Fast Healthcare Interoperability Resources (FHIR®) is a next-generation standard framework created by HL7 combining the best features of previous HL7 standards. FHIR® leverages the latest web standards and focuses on ease of implementability. In this deck, Nirmal will introduce WSO2 Healthcare Integration Platform and demonstrate how it boosts developer productivity when exposing FHIR® APIs.

1. Towards Greater Interoperability With A
Proven Integration Platform and FHIR®
August 26, 2020

2. The Interoperability Problem

3. 3
Patient journey

4. The Challenge is
Creating a comprehensive, longitudinal view of a
patient’s health history
4

5. 5
Why is it important?
Patients to make a better
decision on selecting a
healthcare provider
Patients to select the best
health coverage plan
Inform providers to support
better health outcomes
Overcome silos of health
data

6. Regulation

7. The Interoperability and Patient Access Final Rule
7
CMS-9115-F was introduced by the
Centers for Medicare & Medicaid Services
(CMS) to enable better access to health
information for patients, improve
interoperability, and unleash innovation.
The finalized new policies will be enforced
on July 1, 2021.
Data to be exposed via FHIR APIs;
- Claims & Encounter data
- Clinical data
- Provider directory
- Drug formulary
CMS Rule

8. 8
What is Fast Healthcare Interoperability Resources?
Source: http://hl7.org/

9. 9
Why FHIR is better?
Strong focus on
implementation
Interoperability
out-of-the-box
Leverage latest
web standards
Support for
RESTful services
architecture
Concise and easily
understood
specification
Human-readable
serialization
format for ease of
use by developers

10. 10
FHIR components

11. 11
FHIR v4.0.1 resources
Source: http://hl7.org/
Patient FHIR resource

12. Solutions

13. FHIR API Facade
(Real-time transformations)
FHIR repository based FHIR server
(can be slightly outdated)
13
The two main architectural patterns

14. WSO2 Open Healthcare Platform

15. 15

16. 16
Autogenerative FHIR data transformation connectors

17. 17
Low code integrations

18. 18
HL7v2 to FHIR visual data mapping

19. 19
Autogenerative FHIR API Definitions

20. 20
Expose APIs to third party application developers

21. 21
Data TransformationAPI Management
FHIR Accelerators
Connect Systems
FHIR Resource
Connectors
Cerner
Connector
Epic
Connector
FHIR Swagger 2.0
Definitions
FHIR OpenAPI 3.0
Definitions
FHIR Resource
Validation
Auto-generative FHIR
CapabilityStatement
OpenID Connect/
OAuth 2.0
Data
Services
HL7
Transport
more .. more .. more ..
X12 to FHIR
Mapping
HL7v2 to FHIR
Mapping

22. In the near future..
22

23. 23
Bootstrap tool

24. Why a proven api-led integration
platform?

25. 25

26. wso2.com
Thanks!
Contact us at wso2.com/solutions/healthcare to get access to the sandbox environment
Webinar series at https://bit.ly/2EhBn07