Please enable JavaScript.
Coggle requires JavaScript to display documents.
Intelliguard - EPIC Integration - Coggle Diagram
Intelliguard - EPIC Integration
EPIC
Well know tool that's used by Hospitals to manage patient information
50-60% of Hospitals in the US
Confirm Stats
Epic gained 55 hospitals in 2019 and now has 29% of the hospital market. That's up from 28% last year, according to KLAS.
Medical Staff will enter medication given to a patient. Example: 200ml fentanyl
Complex system that needs a specially trained staff member make changes to it's configuration and screens
Epic allows for one chart to follow patients throughout the multiple areas in which they receive care
Integration
Two way communication
Information entered in EPIC is sent to IG Enterprise
Information entered in IG Enterprise is sent to EPIC
Implemented
NService
Bus to send messages to MIRTH and process in coming messages from MIRTH
What is MIRTH?
MIRTH is a service implemented by IG that knows how to translate and convert the
HL7
messages coming from EPIC
Convert the messages to XML
used it to check the syntax for the messages sent/to and from EPIC
HL7
is a Medical Communication Standard (Message Format)
Integration Types
EPIC is a HUGE application with multiple integration points/Types. The focus for this integration were the following:
Grand Central - Admission/Discharge/Transfer of Patients
Surgical Scheduling
Dosage information / Administering of Drugs
Goal
Implement the integration of one client successful
Use that success/experience to on-board and integrate with other hospitals that already use Intelligurard's Dispensers
Adds another layer of accountability
Stealing, Billing, and other loop holes in the process of dispensing and administering medications
Reporting and Reconciliation
Success/Outcome
IG was able to generate an
Integration Guild
that they can share with clients that looking to integrate
A successful implementation that IG can leverage as a success story to get more Hospitals/Clients on board
Challenges
Hospitals may use EPIC in different ways. For example: How the name and populate input fields.
Allow free from fields
There was some trial and error
With the
Integration Guide
Hospitals can make the necessary changes to facilitate integration with IG's products
Coordinating with Hospital Staff on changes that needed to be made on their end
Some fields can be exported and some can't
NPI vs Doctor EPIC Identifier
Figuring out what was the best fields/data to send
Addressing Custom changes (basically hacks) that were made in EPIC by the administrators
Coordinating with Hospital Staff to agree on message format/standard (What will be sent and what will be received by the systems)
Agree on what fields that would be sent back and mapped to existing EPIC fields
HL7
Referring to the EPIC HL7 documentation to validate the fields and message structure
EPIC HL7 is slightly different from the standard HL7
Free Form Data
what works for EPIC may not work for another system that ingest Hl7 messages because of the slight difference and Free from fields
Hospital will decide on what events that want to trigger on and what messages to send when that event occurs
HL7 pipe delimited
Don't manually or programmatically try to parse the HL7 message
Use existing tools like MIRTH
Define rules on where to send specific messages
Retries
Most system require an Acknowledgment. MIRTH will hand that
Handles Duplicate Messages
Because the main system didn't receive an acknowledgement in time
The problem
A staff can dispense medication (take medication from the secured tray) and either give a patient some of the medication or none at all
This results in drugs goes unaccounted for
IG solved part of this problem with a
Waste Witness
feature that requires someone to "witness" that remaining drugs being disposed off
Information on how much medication was given to a patient is entered to EPIC
Blog
SEO
Health Care
Message
We know how to do it
Marketing
Is it ground breaking ?
Make Provider Lives Easy
Reduce the Manual Process
They were able to flag incorrect processes and flag for training
Highlights Training Areas
Reduce Liability
What's in it for the client/hospital
See most of the other
branch
Audits
Expired Meds in the Trays
Record Keeping
EPIC becomes the Source of Truth
EPIC also integrates with other systems like 3M devices
Why would someone want this integration?
It's a huge part of Hospital eco-systems
Prevent double/manual entries. For Example: Drug Administration. (Auto enter into EPIC - From the IG System)
Liability Issues
Reduce Errors (Human Errors via Manual entry)
Reduce Paper Processes
Waste Witness
Hospital Modernization
They are slow moving entities
BLOG
Thesis
Point A
Events and Messages
Coordinating with the Hospital
Message Mapping
Integration Guild
Point B
Message Content
Messaging Standards
HL7
EPIC HL7 vs HL7
Point C
Message Handling
Sending and Receiving Messages
Error Handling
Using Existing Tools like MIRTH
Conclusion