Approach to enable your IT systems for FHIR (HL7 standards) compliance
- 1. APPROACH TO ENABLE YOUR IT SYSTEMS FOR FHIR (HL7 STANDARDS) COMPLIANCE
- 2. Introduction to FHIR Fast Healthcare Interoperability Resources 1600 MEMBERS 50 COUNTRIES 500+ MEMBERS Specification to standardize data formats and APIs for securely accessing Electronic Health Records
- 3. Health Care Professionals / Consumers Patient Clinical Impression Diagnostic Report Medication Statement Observation Medication Request Allergy Intolerance Medication Administration Procedure Example - Common Entities
- 4. Why do we need FHIR ? Empowers Healthcare Practitioners Enables “Patient-first” approach Enhances Healthcare experience through Mobile Apps and Cloud Regulatory requirement - CMS Allows interoperability of healthcare software and device vendors
- 5. Common Use Cases Digitized Diagnostics (Labs) Reports Healthcare Mobile Apps Enrollment and Claims Chatbots/App based Appointment Scheduling Health Wearable Smart Devices Clinical Decision Support Systems AI and ML based Bio-Research / Clinical Research Clinical Data Repository Smart Hospital Management Systems Claims verification and Processing Payer to Payer Data Exchange Insurance Cover verification Admission and Discharge Notification Incentives and offers based on Health data Bundled Offerings through Partners
- 6. Industry Adoption of FHIR 1600 MEMBERS 50 COUNTRIES 500+ MEMBERS
- 7. Common Challenges in FHIR Implementation Fragmented data across disparate systems Heavy dependency on Legacy systems Integration challenges with legacy and modern Cloud and Mobile-centric solutions Cost of modernization and associated risks IT Complexity leading to long time to market for any changes - Inflexible IT Use of IT merely as a support system instead of re-inventing / enhancing the Customer Experience
- 8. How to digitally transform your IT systems for FHIR compliance 1 Define your purpose and vision of digital transformation. Answer the “Why” 2 Identify the customer journeys and their touchpoints for each initiative in your transformation journey. 3 For each touchpoint in the customer journey, audit the challenges/pain areas in securely making data available. Identify opportunities to transform / expose legacy. 4 Define an integration-centric target technology architecture for secure data exposure. Ex: Cloud Native, API Management, etc. Redefine your IT Security policy for FHIR compliance. 5 Establish an Integration Framework, Governance Principles, Demand Management and Operating Model. Align your SDLC
- 9. Hybrid Cloud Native Integration Platform for Digital Healthcare API Gateway Developer Portal (Content Manager) Container Orchestration Platform Containerised Microservices API Interface Review Automation Tool Enterprise Repository Design-Time Governance Tools Mobile Apps Online Web, Cust Care and Portals Cloud (SaaS) Applications Content Partners Internet of Things Third Party B2B Applications Public Developers (API Economy) CURRENT AND FUTURE CHANNELS Development Tools and Accelerators Service Mesh Micro-Gateway Microservices Monitoring Distributed Transaction Tracing Runtime Management & Automation Frameworks Existing Integration Infrastructure (ESB, Webservices, etc) Billing Appointment Management Hospital Information Systems (HIS) Identity Management Clinical Data Repository (CDR) Imaging & Document Management Systems Electronic Medical Record HR & Payroll Systems Healthcare Systems – Legacy / Third-party systems Data Layer Transactional Data (System of Record) Batch Data (Feeds) Reference Data Analytics / Reporting Business Intelligence Data from third-party systems Datawarehouse API Stub API Test Automation Tool API Interface Documentation Generation Tool Identity Management (Existing Infra) Continuous Integration & Continuous Deployment Tools (CI/CD) Deployment Automation Tool DevSecOps Tools API Security Testing Tool Event-driven, Batch & File- based Integration (Apache Kafka) Async APIs, Events
- 10. Legacy Enterprise Service Bus Messaging Middleware Traditional Web Services (SOAP, XML) Legacy Data Integration & Analytics XML & SOA Gateways MicroServices Micro-Gateways Service Mesh Micro-Integrator GraphQL APIs Backend for Front-ends (BFF) Legacy Business Process Management Batch and FTP-based File Transfer Managed File Transfer Customer Journey Mapping Robotic Process Automation Legacy Operations - Logging, Monitoring & Health check UDDI based Service Registry High-performance Messaging (Kafka) Serverless Async APIs DevSecOps Distributed Transaction Traceability (System Observability) AI-Ops Tools Chaos Engineering Site Reliability Engineering Building Blocks of Legacy Integration to Cloud Native Architecture Data Virtualization Cloud-based Data Platforms Citizen Integrators Internal Developer Portal Service Mesh CI/CD Artifact Repository iPaaS & Hybrid Integration Platform Cloud-Native Architectural Model mBaaS Containerization & Orchestration Cloud-friendly ESBs Container Management Bare-Metal Integration Infrastructure (Servers) iPaaS Serverless Hybrid Cloud Private Cloud and Containerization Identity and Access Management Legacy Event Processing Events Streams Processing (Kafka Streams) Complex Event Processing API Management Self-service Developer Portal Edge Servers (For IoT Integration) Cloud-based Identity Management (IDaaS) Federated Identity management – SaaS & On-Premise AI-based Adaptive Security Tools Privacy and Consent Management Tools
- 11. DigitMarket suite of Products Interoperability Kit for Healthcare Data Exchange API Test Automation Tool Starter Pack API Gateway & Management Visual Integration Tool Deployment Automation Tool Stubbing Automation Tool Microservice templates for common use cases FHIR-based templates in Coupler tool to accelerate southbound integration Pre-configured FHIR data models within DigitMarket API Manager Legacy Transformation Patterns and Principles
- 12. Hospital Hospital Insurance Companies Hospital Data Gateway Powered by Hospital Management Systems A new patient visits a hospital (first visit) Hospital registers the user into the hospital management system. User data is made securely accessible to different hospital departments User undertakes medical tests in the Lab as advised by Doctors Lab technician updates results in the hospital management system User accesses his/her diagnostics reports on his/her smartphone / tablet. Also, accesses his/her insurance details. Hospital Data Gateway Powered by Cross-Hospital Data Interchange FHIR-compliant data Exchange with Insurance • Product and System Integration offered by THIS to API- enable hospital management systems • DigitMarket API Manager provides FHIR-compliant starter kit that includes pre-configured northbound interfaces • Coupler integration product provides visual tooling to transform and map FHIR northbound interfaces to your legacy hospital management systems • Third-party diagnostic Labs and other healthcare services access patient data through FHIR-compliant APIs through the secure API gateway, powered by DigitMarket API Manager to serve the patient. Insurance and other parties securely access and exchange data in compliance to FHIR User can use his/her data across hospitals that participate in the Digital Healthcare offering FITMENT OF DIGITMARKET TOOLS – HEALTHCARE DATA EXCHANGE
- 13. FHIR – “Enabling Digital Ecosystems” Diagnostic Centers Alternate Medicines Pharmacies Hospitals Health Smart- Device Distributors Health Insurance Doctors Digital Health Ecosystem Fitness Trainers Dietitians and Diet Food suppliers Healthy food delivery Transport Accommodation Blogging sites Complimenting Businesses & Other Platforms + Your Customers Delivery Partners Returns Processing Service Fulfillment Online Consulting Fulfilment services +