Hey Ann,
You should have me on speed dial!
I dimly recall that it is a major CPRS release that did the changes. Therefore, if I were you, I would go back CPRS by CPRS version and see what they added as new features.
I did a search for you:
sam@wv4:/var/www/html/foia-vista/Patches_By_Application/OR-ORDER ENTRY_RESULTS REPORTING$ grep -i "IMO" *.txt *.TXT
Entered in error patch for ORDER ENTRY-3-360.txt: NON-IMO INPT MEDS'.
OR-3_SEQ-437_PAT-377.txt:Routine Name: ORIMO
or-3_seq-260_pat-243.txt: was unanimous agreement that displaying the "Date/Time Wanted" in the
or-3_seq-260_pat-243.txt: --Sort by Status/Exp Date (IMO first on Inpt)
or-3_seq-260_pat-243.txt: --IMO Order Schedule Expanding Inappropriately - When copying an IMO
or-3_seq-260_pat-243.txt: order to a new IMO order, the schedule was expanding.
or-3_seq-260_pat-243.txt: Resolution: Developers changed this because IMO orders should not expand
or-3_seq-260_pat-243.txt: --IMO Order Assigned to Incorrect Location - Previously, when was signing
or-3_seq-260_pat-243.txt: IMO orders for a patient who was admitted while the CPRS session was
or-3_seq-260_pat-243.txt: some of the IMO orders from the signature list, these orders were
or-3_seq-260_pat-243.txt: --IMO Clinic Determination
or-3_seq-260_pat-243.txt: Resolution: To help determine if a location is an authorized IMO
or-3_seq-260_pat-243.txt: entry is marked as an IMO location. If the location is marked as an IMO
or-3_seq-260_pat-243.txt: location, then CPRS allows the user to place IMO orders.
or-3_seq-260_pat-243.txt:Routine Name: ORIMO
OR-3_SEQ-288_PAT-280.TXT: PSPO 850: Using (IMO) and Appt Crosses Midnight, Appt. Not
OR-3_SEQ-288_PAT-280.TXT: orders in an Inpatient Medication for Outpatient (IMO) clinic, such as an
OR-3_SEQ-288_PAT-280.TXT: outpatient clinic or an Inpatient Medication for Outpatient (IMO) clinic,
OR-3_SEQ-288_PAT-280.TXT: for an IMO clinic.
OR-3_SEQ-288_PAT-280.TXT: when the user is ordering in an IMO clinic to Clinic Infusion Order
OR-3_SEQ-294_PAT-338.TXT: VA Maryland HCS (Baltimore), MD
OR-3_SEQ-309_PAT-362.TXT:Subject: SCHEDULE CHANGE ERROR FOR IMO ORDERS
OR-3_SEQ-309_PAT-362.TXT: Medications for Outpatients (IMO) Clinic the system is not checking that
OR-3_SEQ-309_PAT-362.TXT: HD0000000622440 - No schedule change warning for IMO orders
OR-3_SEQ-309_PAT-362.TXT: HD0000000622440 - No schedule change warning for IMO orders
OR-3_SEQ-309_PAT-362.TXT: However, if the order was entered for an IMO Clinic location, this warning
OR-3_SEQ-309_PAT-362.TXT: (IMO) display group during the renew action. If the NAME (#.01) field in
OR-3_SEQ-323_PAT-320.TXT: VA Maryland HCS, (Baltimore) MD
OR-3_SEQ-359_PAT-402.TXT: Inpatient Medications for Outpatients (IMO) order that is considered a
OR-3_SEQ-359_PAT-402.TXT: orders (IMO)
OR-3_SEQ-359_PAT-402.TXT: orders (IMO)
OR-3_SEQ-359_PAT-402.TXT: outpatient medications that are checked against active clinical IMO
OR-3_SEQ-359_PAT-402.TXT: Modified the API DT^ORKPS1 to include IMO orders as part of duplicate
OR-3_SEQ-362_PAT-350.TXT: 37. INC000000172679 Problem with IMO order
OR-3_SEQ-362_PAT-350.TXT: The root problem is with the fact that IMO was never intended to handle
OR-3_SEQ-362_PAT-350.TXT: Clinic Orders (the replacement for IMO) will handle clinic orders for
OR-3_SEQ-362_PAT-350.TXT:Routine Name: ORIMO
OR-3_SEQ-363_PAT-424.TXT:Routine Name: ORIMO
OR-3_SEQ-369_PAT-423.TXT: 5. CPRS 30B (OR*3*350) included functionality related to what was IMO but
OR-3_SEQ-374_PAT-420.TXT: VA Maryland Healthcare (Baltimore, Loch Raven & Perry Point)
OR-3_SEQ-378_PAT-436.TXT: as an "IMO" clinic, the order will disappear from the BCMA Virtual Due
OR-3_SEQ-378_PAT-436.TXT: administration of inpatient medications (IMO).
OR-3_SEQ-378_PAT-436.TXT: that if the location is set to a clinic "IMO" location, the provider will
OR-3_SEQ-380_PAT-458.TXT: VA Maryland HCS (Baltimore, MD)