| DESCRIPTION OF ENHANCEMENTS |
NOTE:
across the VistA applications.
prescriptions when that particular fill for resubmission has been
canceled.
8. E3R 18029 It is possible for the remote sites to input more
information into the NARRATIVE REFILLABLE RX (#1004), NARRATIVE
NON-REFILLABLE RX (#1005), and NARRATIVE FOR COPAY DOCUMENT (#1006) text
fields in the Outpatient Site file (#59), than can be printed at the
CMOPs.
Solution: The transmission process will now load only up to seven lines
(80 characters per line) of information from each of these fields. The
following warning message is also sent to the facility CMOP users when a
transmission has had to limit the number of lines being sent to the CMOP.
Subj: >>WARNING<< CMOP Outpatient Site narrative Instructions [#140709]
05/16/03@15:21 8 lines
From: Smith,John In 'IN' basket. Page 1
--------------------------------------------------------------------------
The following Outpatient Site file (#59) narrative field(s) exceed seven
lines.
NOTE:
This exceeds CMOP limits.
Lines beyond seven are not being sent to the CMOP.
Outpatient Site: TROY
NARRATIVE REFILLABLE RX 36 lines
NARRATIVE NON REFILLABLE RX 49 lines
NARRATIVE FOR COPAY DOCUMENT 16 lines
9. Problem: It has been found that during the building of a transmission
CMOP hosts will see the expected following error messages as the software
other VistA applications are able to perform edits, refills, copies, and
deletions of prescriptions that are being loaded into the CMOP
transmission.
Solution: The use of a new integration agreement with Order Entry /
Results Reporting (OE/RR) version 3 provides a way to let CMOP identify
the prescriptions that are being transmitted so that they will not be
processed by other VistA applications. A related OE/RR patch OR*3*183 has
been released that will complete the ability for CMOP to identify the
prescriptions.
will be installing data fields for the facilities in files that the CMOP
10. Problem: Prescriptions have been processed to the CMOPs when they
should have dropped out of CMOP processing because of the patient's
mailing status.
Solution: The code has been changed so that the prescriptions are dropped
out of CMOP suspense for patients who have an incompatable mailing status
for CMOP processing.
NOTE: There have been several fields added to the CMOP SYSTEM file (#550)
hosts do not have.
and the CMOP TRANSMISSION file (#550.2) to support the changes listed
for this patch.
Installing Data Dictionaries:
** ERROR IN DATA DICTIONARY FOR FILE # 550 **
Facilities are required to have installed PSO*7*126.
Data Dictionary not installed; Partial DD/File does not exist
** ERROR IN DATA DICTIONARY FOR FILE # 550.1 **
Data Dictionary not installed; Partial DD/File does not exist
** ERROR IN DATA DICTIONARY FOR FILE # 550.2 **
Data Dictionary not installed; Partial DD/File does not exist
CMOP hosts may ignore a portion of the installation instructions as they
pertain to functionalities found only at the remote facilities.
There is a partner patch that is being distributed previous to PSX*2*41.
NOTE: If you have batches (transmissions) that you are planning to
re-transmit, do so prior to installing PSX*2*41. The Re-transmit CMOP
Data [PSXR RETRANSMIT] option has been re-coded to match the new data
architecture being used in PSX*2*41 and will not be able to resend batches
prior to installation of PSX*2*41.
1. Problem: Controlled Substance (CS) and Non-Controlled Substance
(NON-CS) prescriptions are being mixed into the same batches when the
The partner patch is Outpatient Pharmacy V. 7.0 PSO*7*126. This will be
recovery process is cleaning up a broken transmission. The original
recovery process was written when there was only one type of prescription
being sent and it includes remnants of the previous transmission in
the current transmission.
Solution: The recovery process has been re-written to reset the
prescriptions to a state as if they were just queued waiting for
transmission.
2. Problem: There have been instances where the prescriptions of two
tested in the environmental checking phase of the installation and not in
patients have been merged into the same HL7 order in the CMOP RX QUEUE
file (#550.1).
Solution: The use of the CMOP RX QUEUE file (#550.1) has been redesigned
to be only used in the building of the HL7 order messages and it is
cleared out prior to and after each transmission. The access to the CMOP
RX QUEUE file (#550.1) is locked by the transmission job when it
first starts up and is released as the last step as the transmission
finishes.
the KIDs required patches section. Consolidated Mail Outpatient Pharmacy
3. Problem: Several sites have reported that they were not able to
re-direct the scheduling of their transmissions to another
Consolidated Mail Outpatient Pharmacy (CMOP). There are several fields
within the scheduling that have a database required criteria set. This
makes it difficult for the software to clear them and reset them.
Solution: The scheduling of transmissions has been redesigned to use the
Kernel Option Scheduling and its utilities. This streamlines the user
input and control of the scheduling of the transmissions. Transmissions
must now be scheduled no closer than two hours apart.
(CMOP) hosts are not required to install PSO*7*126. There is also a
4. Problem: The beginning message number within a transmission sometimes
differs from the notation within the message.
Solution: The use of the CMOP RX QUEUE file (#550.1) has been redesigned.
It is now cleared out prior to each transmission and each transmission
now starts with the number one.
5. Enhancement: Other Language - Data elements in the HL7 messages are
being activated that will enable the SIG and PMI sheets to be printed in
companion ORDER ENTRY / RESULTS REPORTING (OERR) patch OR*3*183 that is
another language. This is in co-ordination with the emerging Outpatient
Pharmacy V. 7.0 'Other Language' patch PSO*7*117.
6. Problem: It is possible to create duplicate active prescriptions
through the renewal and copy prescription functions if the prescription
is a part of a currently running CMOP transmission.
Solution: The transmission software has been modified so that the
setting of prescription status flags occurs in a manner that will keep
the renewal and copy functions from accessing prescriptions that are
needed to complete the locking and ownership/protection of prescriptions
being loaded into a CMOP transmission. A prescription may be locked by a
user and if so that prescription is skipped and a "RX OERR/CPRS Locked"
error is itemized with other correctable prescription errors and sent to
the holders of the "PSXMAIL" key.
7. Problem: A prescription that has been sent to CMOP, not filled, and
then is canceled locally is selectable for resubmission to the CMOP and
generates a program error when being processed.
Solution: The software has been amended to not allow the resubmission of
|
