Problem Statement
The HCER supports the patient summary extension use case In this use case, after a PS is retrieved by country B, country A is informed on the healthcare encounter in country B, so country A is able to update the history of treatment events (according to its own policies).
Users Involved
Physician/Doctor
List Of Features
Use Case NR | Title | To be implemented in OpenNCP |
---|
UC1 | The doctor is authenticated by the portal | Basic functionality already present in OpenNCP portal and in epsos-web. - Check if additional rights need to be assigned to the doctor role for enabling HCER.
- Make sure that TRC-STS is ready to handle the extra rights for HCER.
|
UC2 | The doctor will identify the user. Its covered now from OpenNCP Portal | Functionality already present in OpenNCP portal and in epsos-web. XCPD binding. |
UC3 | The doctor asks to create a HCER document, He also can see the patient summary document (TRCA and consent must be applied) | Assumption: Use case starts by fetching the patient summary. Then a HCER can be created as a modification of the fetched PS. Reuse the eP+eD idea for the user interface in the portal. Extension in a later sprint: If the patient does not have a PS, a HCER can be created from scratch. |
UC4 | The system will be able to generate a new type of document HCER. The system provides the correct UI to do this | - Guidelines for the new document type of HCER, start from https://service.projectplace.com/pp/pp.cgi/r844355914
- User Interface for filling the HCER document (OpenNCP Portal and epsos-web)
|
UC5 | The system will create this new type of cda document and will upload it in the relevant NCP | - Method for constructing a valid CDA document (OpenNCP Portal and epsos-web) according to the guidelines formulated in UC4 implementation.
- Web service call from the portal to NCP-B client connector for submitting the HCER. Reuse the XDR (eD and consent) implementation.
- NCP-B client connector: WSDL extension for HCER.
- NCP-B client connector: processing of a web service call with HCER payload from the portal.
- Web service call from the NCP-B to NCP-A with HCER payload. Reuse the XDR (eD and consent) implementation.
|
UC6 | NCP-A must accept this document and provide info for the result | - Add new document class code to XDRServiceImpl: document type detection, call to national connector gateway, audit log method.
- Extend ncp-a interface: add HCER methods.
- Define exception classes and error codes for HCER processing.
- Extend assertion validator and defaultpolicymanager: add HCER class code and any additional permission codes.
|
UC7 | Doctor can merge the HCER information into PatientSummary Document | Implemented as part of UC4 implementation. |
UC8 | The doctor can query for HCER Documents of a patient | Assumption: it is the responsibility of the country A to integrate the previously submitted HCER to the patient's PS. Therefore the doctor can query PS for getting HCER information. |
What must it be implemented
- Guidelines for the new document type of HCER
- User Interface for filling the HCER document (OpenNCP Portal)
- Method for constructing a valid CDA document (OpenNCP Portal)
- Method for accepting HCER documents (NCP-A, national connector part)
- Method for merging HCER documents into Patient Summary (NCP-A). This can be decided in NCP-A method that will accept HCER document
Questions / Open Issued
- A new document type must be addressed for HCER Document
- It has to be decided which type of Audit Message will be used for logging this action