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 |
|---|---|
| UC1 | The doctor is authenticated by the portal |
| UC2 | The doctor will identify the user. Its covered now from OpenNCP Portal |
| UC3 | The doctor asks to create a HCER document, He also can see the patient summary document (TRCA and consent must be applied) |
| UC4 | The system will be able to generate a new type of document HCER. The system provides the correct UI to do this |
| UC5 | The system will create this new type of cda document and will upload it in the relevant NCP |
| UC6 | NCP-A must accept this document and provide info for the result |
| UC7 | Doctor can merge the HCER information into PatientSummary Document |
| UC8 | The doctor can query for HCER Documents of a patient |
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