Domain Name: |
CR Number: |
|
|
|
Request Date: |
Document Version No: |
||
|
Bugzilla Number(s): |
16411, 18300, 18301, 18302, 18303, 18403, 18404, 20012, 20835, 20836, 20838, 20839 |
||
|
|
|
|
Change Title: |
Misc. Changes to MM 3.0.doc |
|
|
|
|
issue Description: |
Bugzilla Issue 16411 ============= List of Item Status values in Dispensing compliance does not match MIM vocabulary.
Bugzilla Issue 18300 ============= In message Prescription State List (Query By Requester) Query - QURX_MT000003UK01 parameters statusCompleted, statusCompletedClaimed, statusWithDispenser, statusWithDispenserActive are mandatory 1..1. This means that requester will have to supply this information but as per SRS these should be option 0..1
Bugzilla Issue 18301 ============= If PrescriptioneffectiveTime in Prescription State List Query Response - PORX_MT000004UK01 represents Issue Date as required bySRS then it should be specified so in the tabular of this message.
Bugzilla Issue 18302 ============= pertinentPrescriptionStatus should be mandatory 1..1 in Prescription State List Query Response - PORX_MT000004UK01
Bugzilla Issue 18303 ============= Description of requesterOrganizationType is incorrect in tabular view of Prescription Detail Query - QURX_MT000005UK01.
Bugzilla Issue 18403 ============= Message does not include place holder for Additional Information [to hold successful Cancel Request] as required by SRS
Bugzilla Issue 18404 ============= There is no interaction and message specified for Cancel (i.e. Withdraw) Protocol Supply.
Bugzilla Issue 20012 ============= On MIM 4.1.01 it says:
For Dispense Notification author:
SDS Organization Id details of the scoping GP practice. SHOULD IT BE PHARMACY? SDS Person Id details the person playing the Agent (dispenser) role SDS Role identifies a person fulfilling the specific role for a person (dispenser) that dispensed this prescription.
The same question applies to Prescription Request.
Bugzilla Issue 20835 ============= Vocab for PrescriptionTreatmentType requires updating
Current Vocab Definition
Code Definition 0001 Acute 0002 Repeat Prescribing 0003 Repeat Dispensing
Required Changes
Code Definition 0001 Acute – Non Controlled Drug 0002 Repeat Prescribing – Non Controlled Drug 0003 Repeat Dispensing – Non Controlled Drug 0004 Acute – Appliance or Device 0005 Repeat Prescribing – Appliance or Device 0006 Repeat Dispensing – Appliance or Device 0007 Acute – Schedule 5 Controlled Drug 0008 Repeat Prescribing – Schedule 5 Controlled Drug 0009 Repeat Dispensing – Schedule 5 Controlled Drug 0010 Acute – Schedule 4 Controlled Drug 0011 Repeat Prescribing – Schedule 4 Controlled Drug 0012 Repeat Dispensing – Schedule 4 Controlled Drug 0013 Acute – Schedule 3 Controlled Drug 0014 Repeat Prescribing – Schedule 3 Controlled Drug 0015 Intentionally left blank 0016 Acute – Schedule 2 Controlled Drug 0017 Repeat Prescribing – Schedule 2 Controlled Drug 0018 Intentionally left blank 0019 Acute – Schedule 1 Controlled Drug 0020 Repeat Prescribing – Schedule 1 Controlled Drug 0021 Intentionally left blank
Bugzilla Issue 20836 ============= Currently ETP is using a temporary interaction TEST_SUCCESS_PSIS_1234 to withdraw messages from PSIS queue.
Bugzilla Issue 20838 ============= PrescriptionAnnotation vocab contains 2 x instances of code "CP", one meaning "Charge Paid" and the other meaning "Cancellation Pending".
Bugzilla Issue 20839 ============= PrescriptionType and PrescriptionTreatmentType vocabs contain code descriptions "Intentionally left blank" and it is not clear to suppliers how these should be handled. |
|
|
|
|
Proposed solution |
Bugzilla Issue 16411 ============= Update values of ItemStatus codes to match those of BT spec.
Bugzilla Issue 18300 ============= Keep parameters statusCompleted, statusCompletedClaimed, statusWithDispenser, statusWithDispenserActive as mandatory 1..1, but change tabular view descriptions to "Default value: true"
Bugzilla Issue 18301 ============= Make effectiveTime = prescription issue date
Bugzilla Issue 18302 ============= Update model to make pertinentPrescriptionStatus mandatory 1..1 - will require message and query and response interactions to be reversioned.
Bugzilla Issue 18303 ============= Update tabular view description of requesterOrganizationType.
Bugzilla Issue 18403 ============= Add optional component element for successful Cancellation Request
Bugzilla Issue 18404 ============= Add Withdraw Protocol Supply Interaction (and Trigger Event) using existing ETP Withdraw message. Also change tabular views descriptions of PS and PA id’s to 18 character.
Bugzilla Issue 20012 ============= Correct author / legalAuthenticator atribute definitions in tabular views of following messages, as implied: Patient Prescription Release Request - PORX_MT121002UK30, Nominated Prescription Release Request - PORX_MT121001UK30, Dispense Notification - PORX_MT024001UK31, Dispense Claim Information - PORX_MT142001UK31 and Dispense Notification with Claim Information - PORX_MT142004UK31
Bugzilla Issue 20835 ============= Update vocab for PrescriptionTreatmentType as requested
Bugzilla Issue 20836 ============= Create new new interaction PSIS Withdraw Notification - PORX_IN161292UK01 for withdrawing messages that are sent to PSIS.
Bugzilla Issue 20838 ============= ETP Spine supplier and ETP business team have both confirmed that PrescriptionAnnotation codes are not used in ETP processing and that one can therefore be changed without any adverse effects.
Code "CP" for "Cancellation Pending" will therefore be changed to "CAP". Tabular view which references this as a fixed will also be updated, without version change.
Bugzilla Issue 20839 ============= Has been agreed with the ETP business team that the "Intentionally left blank" codes may be removed from PrescriptionType and PrescriptionTreatmentType |
|
|
|
|
actual solution: |
|
|
|
|
|
potential IMPACT if change not made: |
MM specifications will conflict with ETP SRS. |
|
|
|
|
target release: |
MIM 5.3 |
|
|
|
|
will there be any impact on other domains? |
No |
|
Change to CMET required? |
No |
|
Change to Clinical statement required? |
No |
|
backwards compatibility: |
Yes |