Upload
heinz-dommert
View
56
Download
1
Embed Size (px)
Citation preview
Copyright © 2009 Siemens Medical Solutions USA, Inc. All rights reserved.
Siemens Confidential
Soarian Interoperability
Design & Integration of Workflows among Soarian Applications Scheduling ClinicalsFinancials Enterprise Document Management
Copyright © 2009 Siemens Medical Solutions USA, Inc. All rights reserved.
Siemens ConfidentialPage 2
Interoperability – versus Interfaces
Interface Supports mapping of unmatched data Transported via an external interface engine such as OPENLink Data modification and mapping Uses HL7 mapping
Interoperability Through Global Session Manager GSM data is matched SF to SC uses Message Exchange Subsystem MXS to communicate Can only be modeled no customization or mapping Designed using XML
Copyright © 2009 Siemens Medical Solutions USA, Inc. All rights reserved.
Siemens ConfidentialPage 3
Interoperability – similar configuration & tasks
Person IdentifierFinancials Clinical EDMPerson # MPI # Imaging
Enrollee #
Medical Record #
Medical Record #
Imaging MR#
ECD # Patient Acct ID
Imaging Encounter #
Encounter # Alternate Visit ID
Imaging Encounter #
Imaging Guarantor #
Tasks Security
Launched through Global Session Manager GSM
Tokens give rights to perform tasks Technology
Firewalls GSN & MXS configuration and
validation INI files (Soarian Financials)
Application Profile changes are required to
activate interoperability
Copyright © 2009 Siemens Medical Solutions USA, Inc. All rights reserved.
Siemens ConfidentialPage 4
A View of the SF Security World
Super User
ABC ERGroup
ABC IPGroup
ABC EROU
ABC IPOU
ABC IPHPO
ABC ERHPO
Super UserGroup
IP User
ER User
Toke
nsTo
kens
Toke
nsTo
kens
Taskpad/Active Directory
Users Groups
SF Security Tool
Tokens OUs EPs or BOsbelong to granted Within containing
RBP
Hyp
erlin
ks o
n U
I
Copyright © 2009 Siemens Medical Solutions USA, Inc. All rights reserved.
Siemens ConfidentialPage 5
Interoperability – Coordination & Implementation
Copyright © 2009 Siemens Medical Solutions USA, Inc. All rights reserved.
Siemens ConfidentialPage 6
Interoperability with Soarian Scheduling3.3 or prior
Copyright © 2009 Siemens Medical Solutions USA, Inc. All rights reserved.
Siemens ConfidentialPage 7
Interoperability – Soarian Scheduling / Financials workflow
Soarian Scheduling Portal – from Soarian Financials
Soarian Schedule Appointments – from Soarian Financials
Soarian Scheduling Manage Appointments - from Soarian Financials
Copyright © 2009 Siemens Medical Solutions USA, Inc. All rights reserved.
Siemens ConfidentialPage 8
Interoperability – Scheduling design
Copyright © 2009 Siemens Medical Solutions USA, Inc. All rights reserved.
Siemens ConfidentialPage 9
Interoperability – Scheduling integration
Preliminary Encounter sent to Soarian Scheduling viaMessaging Services•Patient Context•Doctor / Encounter •Encounter / ECD#
Sends back mapped EP/EL on HL7 transaction
Copyright © 2009 Siemens Medical Solutions USA, Inc. All rights reserved.
Siemens ConfidentialPage 10
Interoperability – SS workflow Soarian
FinancialsInterface / Data
TransferSoarian
Scheduling User logs in selects, patient enters encounter data and selects new appointment option
Sends preliminary data and context
Patient & Preliminary encounter
User, patient encounter context
Verify user security, store preliminary data and open Scheduling appt. screen
User schedules appt. for patient
Apply appt. creation rules and create new appt. for encounter
New appt. HL7 Check for medical necessity, send appt. to SF
Send encounter association for appt.
Encounter association
HL7
Store
encounter ID with appt.
Copyright © 2009 Siemens Medical Solutions USA, Inc. All rights reserved.
Siemens ConfidentialPage 11
Interoperability with Soarian Clinicals
Copyright © 2009 Siemens Medical Solutions USA, Inc. All rights reserved.
Siemens ConfidentialPage 12
Interoperability – Soarian Clinicals / Financials workflow
Order Entry – from Soarian Financials
Charge Batch Entry – from Soarian Clinicals
Check- out (Discharge) - from Soarian Clinicals
Transfer - from Soarian Clinicals
Assign level of care - from Soarian Clinicals
Copyright © 2009 Siemens Medical Solutions USA, Inc. All rights reserved.
Siemens ConfidentialPage 13
Interoperability – Clinicals design
Synchronize
Synchronize
Copyright © 2009 Siemens Medical Solutions USA, Inc. All rights reserved.
Siemens ConfidentialPage 14
Interoperability - Clinicals integration
The SF to SC ADT interface is required
HPO Organization and HCUs must match (be synchronized)
SF HPO Entity ID must match SC HCU Entity Abbreviation If matching on EP ensure that SF Encounter Provider ID in the
HPO Master File matches the SC HCU external Abbreviation For matching on Clinical Services ensure that SF user-defined
Clinical Service Mnemonic matches SC HCU external Abbreviation
Copyright © 2009 Siemens Medical Solutions USA, Inc. All rights reserved.
Siemens ConfidentialPage 15
Interoperability – SF Order Entry workflow
1. Create shell account (MXS) to establish patient in Soarian Clinicals
2. Subsequent full transaction (via model interface) will complete elements for SC account
3. Matching EP or Clinical Services to HCU defines where to create Messaging Services transaction for shell account
4. Activate SF Adaptability options to enable workflow Transmits EP or Clinical Service value for Check-in of
Outpatients or ER patients Includes order entry flow at Quick Check-in
Copyright © 2009 Siemens Medical Solutions USA, Inc. All rights reserved.
Siemens ConfidentialPage 16
Interoperability – SF Order Entry (Outpatient) workflow
Copyright © 2009 Siemens Medical Solutions USA, Inc. All rights reserved.
Siemens ConfidentialPage 17
Interoperability – SC Charge Batch Entry workflow
Copyright © 2009 Siemens Medical Solutions USA, Inc. All rights reserved.
Siemens ConfidentialPage 18
Interoperability – SC Transfer / Discharge / Level of Care workflow
• Shows basic patient info, current level of care and field to change level of care
• Select assign level of care
Copyright © 2009 Siemens Medical Solutions USA, Inc. All rights reserved.
Siemens ConfidentialPage 19
Interoperability with Enterprise Document Manager
Copyright © 2009 Siemens Medical Solutions USA, Inc. All rights reserved.
Siemens ConfidentialPage 20
Interoperability - EDM design
Entity codes must be synchronized for interoperability to work
Soarian Master Patient Index MPI must be the same as the EDM Enrollee Corp ID
SF user can launch EDM via links (i.e. check-in, encounter, scheduler)
SF Revenue Management user can launch EDM from Patient Financial Overview PFO home page
Copyright © 2009 Siemens Medical Solutions USA, Inc. All rights reserved.
Siemens ConfidentialPage 21
Interoperability – EDM design
Copyright © 2009 Siemens Medical Solutions USA, Inc. All rights reserved.
Siemens ConfidentialPage 22
Interoperability – EDM design
Copyright © 2009 Siemens Medical Solutions USA, Inc. All rights reserved.
Siemens ConfidentialPage 23
Interoperability - EDM integration
EDM interoperability supports three types of authentication methods Basic Authentication GSM Authentication IIC Authentication
Assumes GSM enabled in Soarian and EDM, passwords are irrelevant relative to GSM
Whether User IDs have to match between GSM and SC depends on which application is being used EDM/HIM and Soarian must be the same IF GSM is used with Soarian Portal user IDs may not have to
match and could be mapped
Copyright © 2009 Siemens Medical Solutions USA, Inc. All rights reserved.
Siemens ConfidentialPage 24
Interoperability – SF to EDM workflow
Copyright © 2009 Siemens Medical Solutions USA, Inc. All rights reserved.
Siemens ConfidentialPage 25
Interoperability – Patient Context from EDM to SC workflow
Copyright © 2009 Siemens Medical Solutions USA, Inc. All rights reserved.
Siemens ConfidentialPage 26
Interoperability – Touch points
* Enterprise cross-application terminology i.e. SC Patient Type = SF HPO Type