Philips HealthSuite Digital Platform and Interoperability

Transcription

1 Philips HealthSuite Digital Platform and Interoperability

2 Developing innovative solutions across the continuum of care Improving patient outcomes, provide better value, and expand access to care.

3 HealthSuite digital platform services Authorize Connect Store Host Securely identify and log all system users, authorize consent and ensure data privacy Manage, update, monitor, and remotely control smart devices and apps; deploy at scale with robust IoT tech Acquire, manage and archive clinical data from devices and apps through a secure cloud-hosted repository Managed infrastructure to deploy and continuously monitor app performance and systems health status Analyze Share Orchestrate Framework to build contextual predictive analytics and decision support algorithms and employ machine learning functionality Standards-based interoperability between enabled apps and devices with third-party systems via FHIR, HL7, DICOM, IHE profiles, etc. Tools for workflow optimization, rules management, routine task automation, and communications coordination

4

5

6 Patient Cross Referencing Hospital 1 Hospital 2 PIX/PDQ EMR 1 HL7 V2&V3 Patient Feed, patient add/update EMPI HL7 V2&V3 Patient Feed, patient add/update EMR 2 MPI Patient: Name: John Smith DOB: Gender: Male MRN: abcd^^ Patient aggregate: ID: Philips0001^^ Patient Fragments: [ Fragment1: { Name: John Smith DOB: Gender: Male MRN: abcd^^ }, Fragment2: { Name: Johnson Smith DOB: Gender: Male MRN: xyz^^ } ] Patient: Name: Johnson Smith DOB: Gender: Male MRN: xyz^^

7 Document Registry & Repository Hospital 1 HSDP IHE Service Hospital 2 XDS.b Reg/Rep EMR 1 ebxml Document Source EMPI ebxml Document Source EMR 2 XDS MPI Patient: Name: John Smith DOB: Gender: Male MRN: abcd^^ Patient s document(s): Type: CDA XDS.b Repository: Binary: CDA XML payload XDS.b Registry: Metadata: CDA Metadata Registry contains the MRN and EMPI ID of the Patient to whom the document belongs to. Patient: Name: Johnson Smith DOB: Gender: Male MRN: xyz^^ Patient s document(s): Type: CDA

8 Patient Cross-Ref with FHIR Step 1: EMPI Subscription for Patient in CDR Step 2: EMR1 adds Patient-1 with MRN1 into CDR Step 3: CDR sends a copy of the payload to EMPI Step 4: EMPI finds no matching patient(s), creates a new aggregate (with ATNA for Patient Add) Step 5: EMR2 adds Patient-2 with MRN2 into CDR EMR1 HL7V2 EMR2 Step 6: CDR sends a copy of the payload to EMPI Step 7: EMPI finds Patient-2 matches to Patient-1, and cross references them in same aggregate (with ATNA for Patient Add) Step 8: EMPI Updates CDR with Patient-1 linked to Patient-2 (with ATNA for Patient Update to CDR) Step 9: EMPI Updates CDR with Patient-2 linked to Patient-1 (with ATNA for Patient Update to CDR) CDR DB HL7 Broker FHIR API FHIR POST /Patient EMPI DB EMPI

9 CDR: Patient { _id1 identifiers{ MRN1 } link { _id2 _aggreid1 } } Deployment Scenario EMR1 HL7V2 EMR2 Patient { _id2 identifiers{ MRN2 } link { _id1 } } EMPI: Aggr: ^^123 Frag1: MRN1 Frag2: MRN2 CDR DB HL7 Broker FHIR API FHIR POST /Patient FHIR POST /Patient Translate to HL7V3 EMPI DB EMPI Translate to HL7V3 & cross reference

10 EMR Structured Data Capture 1. P&R IHE XDS.b Reg/Rep 2. FHIR Composition CDR FHIR Composition Public Health Reporting Workflow Form Filler SDC compliant form presentation 3. Retrieve Form 5. Return Form with pre-pop data IHE Services RFD 6. Submit Form 7. Submit Form 10. Archive Form 12. Query for Clarifications SDC compliant schema for transactions Form Processor SDC compliant form template 4. Retrieve CDA for pre-pop data 8. Return clarifications External Agencies like CDC etc (Form Receiver) 3. Get Form templates & configurations 13. Get 9. Store Clarifications 11. Archive Form config clarifications archives

11 RFD/SDC IHE Profile based infrastructure for Public Health Reporting NYSCR 325 Attributes CDA Use SDC for providing rich editing capabilities PRPH-Ca ~500 Attributes CDA Subset of NAACCR Attributes aligned with Meaningful use case 2 NAACCR Most comprehensive attributes (>1000) S & I Framework Uses SDC Profile Newer specification

12 Questions Thank you for attending our presentation!