View
3
Download
0
Category
Preview:
Citation preview
Philips HealthSuite Digital Platform and Interoperability
Developing innovative solutions across the continuum of care
Improving patient outcomes, provide better value, and expand access to care.
HealthSuite digital platform services
Analyze
Framework to build contextual predictive analytics and decision support algorithms and employ machine learning functionality
Orchestrate
Tools for workflow optimization, rules management, routine task automation, and communications coordination
Share
Standards-based interoperability between enabled apps and devices with third-party systems via FHIR, HL7, DICOM, IHE profiles, etc.
Authorize
Securely identify and log all system users, authorize consent and ensure data privacy
Connect
Manage, update, monitor, and remotely control smart devices and apps; deploy at scale with robust IoT tech
Store
Acquire, manage and archive clinical data from devices and apps through a secure cloud-hosted repository
Host
Managed infrastructure to deploy and continuously monitor app performance and systems health status
Hospital 1 Hospital 2
Patient Cross Referencing
MPI
HL7 V2&V3 Patient Feed, patient add/update
EMR 1 EMPI
EMR 2
PIX/PDQ
Patient: Name: John Smith DOB: 20141231 Gender: Male MRN: abcd^^1.2.3.4
Patient: Name: Johnson Smith DOB: 20141231 Gender: Male MRN: xyz^^4.5.6.7
Patient aggregate: ID: Philips0001^^9.9.9.9 Patient Fragments: [ Fragment1: { Name: John Smith DOB: 20141231 Gender: Male MRN: abcd^^1.2.3.4 }, Fragment2: { Name: Johnson Smith DOB: 20141231 Gender: Male MRN: xyz^^4.5.6.7 } ]
HL7 V2&V3 Patient Feed, patient add/update
Hospital 1 HSDP IHE Service Hospital 2
Document Registry & Repository
MPI
ebXML Document Source
EMR 1 EMPI
EMR 2
XDS.b Reg/Rep
Patient: Name: John Smith DOB: 20141231 Gender: Male MRN: abcd^^1.2.3.4 Patient’s document(s): Type: CDA
Patient: Name: Johnson Smith DOB: 20141231 Gender: Male MRN: xyz^^4.5.6.7 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.
ebXML Document Source
XDS
EMR1
HL7 Broker
FHIR API
EMPI
EMR2
FHIR POST /Patient
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 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)
HL7V2
CDR DB
EMPI DB
Patient Cross-Ref with FHIR
EMR1
HL7
Broker
FHIR API
EMPI
EMR2
FHIR POST /Patient Translate to HL7V3
FHIR POST /Patient
CDR: Patient { _id1 identifiers{ MRN1 } link { _id2 _aggreID1 } } Patient { _id2 identifiers{ MRN2 } link { _id1 } } EMPI: Aggr: 9.9.9.9^^123 Frag1: MRN1 Frag2: MRN2
Translate to HL7V3 & cross reference
HL7V2
CDR DB
EMPI DB
Deployment Scenario
Public Health Reporting Workflow
Form Filler
IHE Services RFD
Form
Processor
External Agencies like
CDC etc
(Form Receiver)
3. Retrieve Form
5. Return Form with
pre-pop data
6. Submit Form 7. Submit Form
8. Return clarifications
clarifications
9. Store Clarifications
archives
10. Archive Form
11. Archive Form
12. Query for Clarifications
config
3. Get Form templates & configurations
13. Get
EMR IHE
XDS.b Reg/Rep 1. P&R
4. Retrieve CDA for pre-pop data
SDC complaint form
template
SDC compliant form presentation
SDC complaint schema for transactions
CDR FHIR Composition
2. FHIR Composition
Structured Data Capture
RFD/SDC
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
S & I Framework
• Uses SDC Profile • Newer specification
• Most comprehensive attributes (>1000)
• IHE Profile based infrastructure for Public Health Reporting
Questions Thank you for attending our presentation!
Recommended