We use Empower EDIS in our ED and Paragon nearly everywhere else within the hospital. We have ADT messages flowing from Paragon to Empower, Lab and Rad Orders from Empower to Paragon and results back from Paragon to Empower. Those interfaces all do their jobs effectively.
We get constant complaints about the lack of communication between the systems for things like allergies and home med lists. Most of our Inpatients are admitted through the ED so we had issues with patients being asked all the same questions again when they were admitted. We implemented some processes where the Pharmacy consults with the patient to get all of that info and checks Paragon, Empower, and our ambulatory EHR to get an aggregated list and maintains that list in the appropriate system. It is essentially a human interface that requires duplication of effort.
Another challenge is Lab orders. If the ED orders 3 chemistry tests they come into Paragon as 3 separate accessions though there may be only a single sample. Orders originating in Paragon go through grouping logic that could put all 3 on one accession, but inbound interface orders do not use that logic. There are a few ways of dealing with it, but none of them are ideal.
Jim Roberts
Kittitas Valley Healthcare
--
You received this message because you are subscribed to the Google Groups "Paragon CIO" group.
To unsubscribe from this group and stop receiving emails from it, send an email to paragon-cio...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Is anyone using a third party ED system like Medhost or TSystem in place of the Paragon ED functionality?