Siemens utilizes an unfortunately complicated system for building reusable order sets in their pharmacy system. UnlikeÂ Meditech where you can use formulary medications, enter them the way they appear on the order set, give the newly created order set a name and save it; Siemens Pharmacy requires that you first construct a series of “Predefined Common Orders” (PCOs) and use those as building blocks for each order set. PCOs are not only used as building blocks for order sets, but can be used to create shortcuts for medication order entry as well. Each PCO must have a unique name and be specific to the order set from which is hails. Reusing PCOs in multiple order sets creates maintenance issues when one order set makes a revision and the other does not.
A perfect example of this is the use of acetaminophen for mild pain as well as temperature. Do you know how often acetaminophen is used in hospitals? It’s a lot. Differences in frequency, route and reason for use can easily add up to several hundred PCO entries for acetaminophen alone. Multiply that by the number of medications used in a hospital setting and youâ€™ll get a large number of PCOs used both as shortcuts for order entry as well as building blocks for order sets.
PCO descriptions typically include the medication name, dose, route, frequency and reason for use, which can make searching for a specific PCO confusing and frustrating. There are several systems used to decrease the number of irrelevant PCOs appearing when performing a search, however only my method is presented here.
Naming a PCO – When a PCO is part of an order set, use the first few letters of the order set name as the first part of the PCO name. For example: Â acetaminophen 650mg po every 4 hours prn temp > 100.4 found in the Antepartum Admit Orders (AAO) order set would be AAOACE650PO. AAO for Antepartum Admit Orders, ACE for acetaminophen, 650 for the dose, and PO for the route. Other PCOs developed for the same order set would use a similar naming convention (i.e.Â AAOBETAIM for Betamethasone IM, AAOCLI900PB for Clindamycin 900mg IVPB, AAOLR for Lactated Ringers infusion, etc.). The ‘AAO’ prefix keeps the Antepartum Admit Order PCOs together when listed alphabetically.
PCO Description – Begin all PCO descriptions with â€˜OSâ€™, for â€œorder setâ€. This excludes the PCO from search strings containing only a part of the medication, i.e. â€˜aceâ€™ for acetaminophen. For the acetaminophen in the Antepartum Admit Orders example above, the description would read: â€˜OS APAP 650mg PO Q4HP T>100.4′.
The system is far from perfect, but works well for me.
3 thoughts on “Making PCOs easier to use in the Siemens Pharmacy System.”
Those of us fortunate enough to have worked in the MediTech system forever spend the rest of our days trying to find another system as good. The sad part is that we had our issues with MT back then…but they are a drop in the bucket compared to some other “hospital pharmacy” modules we are seeing. IMO the Siemens module is one of the least user/programmer friendly systems to date.
Hi DAnderson – I’ve been a pharmacist for a number of years and have had the opportunity to work with a few pharmacy information systems. I must agree that Siemens is one the least user/programmer friendly systems I’ve had to use/support. Unfortunately the cost of changing pharmacy systems prohibits most facilities from giving any serious thought to change. Thanks for stopping by and putting your thoughts in writing.
Thank you for your web posting. We will be implementing siemens pharmacy and it is helpful to know what we face and your very helpful direction to assist us. THANK YOU.