The purpose of this page is to provide a better clarification on the specification of the implementation of the Medication Related Overview Service on the OpenNCP scope.
______________________________
MRO Service Implementation Overall Status
1. Scenario Clarification
Purpose
The overall purpose to be achieved by this use case is to enable a foreign HCP to review the medical information of a patient consulting her, thereby securing an updated and more safe further treatment of the patient.
Use Case Actors
The actors involved in the epSOS MRO Use Case are:
Primary actors:
- The Patient
- A Prescriber
- A Dispenser
Secondary actors:
- Patient identification, authentication & role authorization service;
- The epSOS Patient Access translation service;
Diagram 1: Use case diagram
The following diagram illustrates the basic use case for the MRO service.
Figure 1. Process diagram of the medication distribution 2 (eP and eD) + distribution II (medication related overview).
Basic explanation of the Use case
- The patient, who is referred to (or reports himself to) a physician.
- When the decision is made that the patient has to take medication for treatment the physician, in his role as prescriber, issues a medication prescription that can be seen both as an order to a pharmacist as well as the agreement between the physician and the patient on the specific treatment with this medication. For doing this, the prescriber receives relevant historical medication information.
- The pharmacist, in his role as a dispenser of medication, receives the prescription, in some countries he receives relevant historical medication information, and dispenses the medication. The pharmacist then issues information about the dispensation, which serves two goals: it is added to the historical medication information, and it is used to update the status of the prescription (in some cases it lowers the amount of remaining items that can be given out from the prescription). The patient again, finally, receives the medication and takes care of the administration, with or without the intervention of family members and/or nurses.
2. Requirements
Actions and Steps
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Aliquam fermentum vestibulum est. Cras rhoncus. Pellentesque habitant morbi tristique senectus et netus et malesuada fames ac turpis egestas. Sed quis tortor. Donec non ipsum. Mauris condimentum, odio nec porta tristique, ante neque malesuada massa, in dignissim eros velit at tellus. Donec et risus in ligula eleifend consectetur. Donec volutpat eleifend augue. Integer gravida sodales leo. Nunc vehicula neque ac erat. Vivamus non nisl. Fusce ac magna. Suspendisse euismod libero eget mauris.
Ut ligula. Maecenas consequat. Aliquam placerat. Cum sociis natoque penatibus et magnis dis parturient montes, nascetur ridiculus mus. Nulla convallis. Ut quis tortor. Vestibulum a lectus at diam fermentum vehicula. Mauris sed turpis a nisl ultricies facilisis. Fusce ornare, mi vitae hendrerit eleifend, augue erat cursus nunc, a aliquam elit leo sed est. Donec eget sapien sit amet eros vehicula mollis. In sollicitudin libero in felis. Phasellus metus sem, pulvinar in, porta nec, faucibus in, ipsum. Nam a tellus. Aliquam erat volutpat.
Sed id velit ut orci feugiat tempus. Pellentesque accumsan augue at libero elementum vestibulum. Maecenas sit amet metus. Etiam molestie massa sed erat. Aenean tincidunt. Mauris id eros. Quisque eu ante. Fusce eu dolor. Aenean ultricies ante ut diam. Donec iaculis, pede eu aliquet lobortis, wisi est dignissim diam, ut fringilla eros magna a mi. Nulla vel lorem. Donec placerat, lectus quis molestie hendrerit, ante tortor pharetra risus, ac rutrum arcu odio eu tortor. In dapibus lacus nec ligula. Aenean vel metus. Nunc mattis lorem posuere felis. In vehicula tempus lacus. Phasellus arcu. Nam ut arcu. Duis eget elit id eros adipiscing dignissim.
Non-Functional Requirements
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Aliquam fermentum vestibulum est. Cras rhoncus. Pellentesque habitant morbi tristique senectus et netus et malesuada fames ac turpis egestas. Sed quis tortor. Donec non ipsum. Mauris condimentum, odio nec porta tristique, ante neque malesuada massa, in dignissim eros velit at tellus. Donec et risus in ligula eleifend consectetur. Donec volutpat eleifend augue. Integer gravida sodales leo. Nunc vehicula neque ac erat. Vivamus non nisl. Fusce ac magna. Suspendisse euismod libero eget mauris. Ut ligula. Maecenas consequat. Aliquam placerat. Cum sociis natoque penatibus et magnis dis parturient montes, nascetur ridiculus mus. Nulla convallis. Ut quis tortor. Vestibulum a lectus at diam fermentum vehicula. Mauris sed turpis a nisl ultricies facilisis. Fusce ornare, mi vitae hendrerit eleifend, augue erat cursus nunc, a aliquam elit leo sed est. Donec eget sapien sit amet eros vehicula mollis. In sollicitudin libero in felis. Phasellus metus sem, pulvinar in, porta nec, faucibus in, ipsum. Nam a tellus. Aliquam erat volutpat. Sed id velit ut orci feugiat tempus. Pellentesque accumsan augue at libero elementum vestibulum. Maecenas sit amet metus. Etiam molestie massa sed erat. Aenean tincidunt. Mauris id eros. Quisque eu ante. Fusce eu dolor. Aenean ultricies ante ut diam. Donec iaculis, pede eu aliquet lobortis, wisi est dignissim diam, ut fringilla eros magna a mi. Nulla vel lorem. Donec placerat, lectus quis molestie hendrerit, ante tortor pharetra risus, ac rutrum arcu odio eu tortor. In dapibus lacus nec ligula. Aenean vel metus. Nunc mattis lorem posuere felis. In vehicula tempus lacus. Phasellus arcu. Nam ut arcu. Duis eget elit id eros adipiscing dignissim.
Legal Requirements
For service legal requirements please consult the D 1.4.3, page 112;
Security Requirements
For service security requirements please consult the D 1.4.3, page 114;
Clinical Requirements
For service clinical requirements please consult the D 1.4.3, page 115.
Additional Architecture NCP / Central Service requirements
For additional Architecture NCP / Central Service requirements please consult the D 1.4.3, page 122.
3. Implementation Strategy Design
Overview
The chosen implementation strategy will make use of the existent Arquitecture and implemented profiles. Following you can fin a table that maps the required steps, in order to accomplish this service and the behaviour that will occur within the OpenNCP system.
Proposed Solution
Step | Actions | OpenNCP actions and operations description | To be implemented in the OpenNCP | Related Profiles |
---|---|---|---|---|
1 | Health professional identification and authentication |
| Already supported | XUA |
2 | The patient’s identity has to be validated in country B, the patient’s identifier(s) from country A must be used for retrieving the MRO. |
| Already supported | XCPD |
3 | The patient must agree with sending the MRO to country B (patient consent in country A). |
| Already supported, some light adjustment is needed. | XCA |
4 | Country B requests the MRO from country A. Country A processes this request and sends the MRO to country B. |
| Already supported, some adjustments are required in the client and server part, mostly at the NI interface level. The portal also requires some changes in order to dispolay the MRO correctly. | XCA |
4. Implementation Issues / Tasks
Portal-B
Protocol Terminators
4. Testing Strategy
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Aliquam fermentum vestibulum est. Cras rhoncus. Pellentesque habitant morbi tristique senectus et netus et malesuada fames ac turpis egestas. Sed quis tortor. Donec non ipsum. Mauris condimentum, odio nec porta tristique, ante neque malesuada massa, in dignissim eros velit at tellus. Donec et risus in ligula eleifend consectetur. Donec volutpat eleifend augue. Integer gravida sodales leo. Nunc vehicula neque ac erat. Vivamus non nisl. Fusce ac magna. Suspendisse euismod libero eget mauris.
Ut ligula. Maecenas consequat. Aliquam placerat. Cum sociis natoque penatibus et magnis dis parturient montes, nascetur ridiculus mus. Nulla convallis. Ut quis tortor. Vestibulum a lectus at diam fermentum vehicula. Mauris sed turpis a nisl ultricies facilisis. Fusce ornare, mi vitae hendrerit eleifend, augue erat cursus nunc, a aliquam elit leo sed est. Donec eget sapien sit amet eros vehicula mollis. In sollicitudin libero in felis. Phasellus metus sem, pulvinar in, porta nec, faucibus in, ipsum. Nam a tellus. Aliquam erat volutpat.
Sed id velit ut orci feugiat tempus. Pellentesque accumsan augue at libero elementum vestibulum. Maecenas sit amet metus. Etiam molestie massa sed erat. Aenean tincidunt. Mauris id eros. Quisque eu ante. Fusce eu dolor. Aenean ultricies ante ut diam. Donec iaculis, pede eu aliquet lobortis, wisi est dignissim diam, ut fringilla eros magna a mi. Nulla vel lorem. Donec placerat, lectus quis molestie hendrerit, ante tortor pharetra risus, ac rutrum arcu odio eu tortor. In dapibus lacus nec ligula. Aenean vel metus. Nunc mattis lorem posuere felis. In vehicula tempus lacus. Phasellus arcu. Nam ut arcu. Duis eget elit id eros adipiscing dignissim.
5. Documentation and References
Documents