Soarian Interoperability

Editor's Notes

• #3: Interface uses external interface engine Interoperability uses internal interface engine OPENLink can be used for both
• #4: Integration requires that all identifiers be equal Behind the scene GSM passes credentials from parent to child system Security tokens must be setup in each system to support user authorization to perform tasks Special user formats have to be setup separately in ICO or ASP
• #5: Similar to the Operational Hierarchy a Organizational Units needs to be established Within the OU reside the HPO to group users for security access Users are grouped to access certain applications and functions
• #6: The technical consultant will be responsible for coordinating the implementation activities. The Applications IC will perform tasks in coordination with the Technical Consultant
• #8: SS Portal – enables the user to maintain master files and preferences, manage worklists and appointments SS Appointments – schedule appointment for new or existing encounter, single, multi or recurring/series SS Manage Appointments – launches to the patients appt. screen in SS from SF to reschedule, cancel, pend, view, edit or confirm appoints. Revise Encounter – enables user to launch SS from SF to revise encounters and manage appointments
• #9: Encounter Provider/Encounter Location mapping can be loaded manually or can be extracted from SF and auto loaded to Scheduling Masterfiles impacted in Scheduling Health Professional Master – initialized via extract or conversion from SF or period updates for new docs included in encounter Service Catalog – extract or conversion if customer needs medical necessity or through interface which is scheduled or manually executed Both standard and user defined profiles, in Scheduling, will be impacted by the integration Patient type (SF HPO Type) Patient class (SF Encounter Type) Financial class (SF Payer Health Plan) Language Marital Status
• #10: Preliminary encounter sent from SF to Scheduling Patient Context and preliminary encounter sent via Massager Exchange Server User selects appointment time/dept/location Scheduling send back encounter on HL7 SIU transaction
• #13: Charge Batch Entry – enters charges directly into SF Check-out – discharge patient Transfer – move patients from one location to another Assign level of care – charge based on care level without having to transfer patient
• #14: SF HPO and SC HCU must be synchronized If matching on encounter provider: for check-out/order entry workflows ensure that SF assigned Encounter Provider ID is the HPO Master File (system ID) and matches the SC HCU external abbreviation If matching on Clinical Service: supporting check-out/order entry, make sure that SF user defined Clinical Service mnemonic matches the SC HCU External Abbreviation
• #19: Level of care can be changed to accurately charges based on acuity Retroactive charges will occur if time/date reflects changes Transfer used for bed control and census balancing
• #22: Documents can be stored at the ECD or encounter level Person leel documents can be stored at the MRN
• #23: Patient Access – documents are looked at the MRN or encounter level Patient Accounting – access documents for Guarantor or claims
• #27: SF to EDM – OMS must be setup to route artifacts Clinical Services are roles identified in the Master file maintenance