DRAFT VERSION!
1. Emergency workflow according with epSOS specifications
In this piece of the full PS workflow we can understand the following:
| # | Step | Option | Observation |
|---|---|---|---|
| 1 | HCP confirms that he checked the correctness of patient's ID details (Port-B) | YES | With the selected option the HCP should then choose if it is an emergency case or not. We will proceed to follow the diagram as if it was one. |
| 2 | Emergency case (button to confirm or deny) | YES | With the selected option the system should send a request to the Patient's country right away, avoiding ask for previous consent. It is up to Country-A to provide or not the information, based on Emergency situation policy. |
The next steps will depend on the Country-A Emergency situation policy. But the important part that is taken from the specs is the folllowing:
- The value XSPA Purpose of Use of the TRC (Treatment Relationship Confirmation) Assertion should be EMERGENCY;
- There should be produced an Audit Message stating the occurrence;
2. OpenNCP implementation
2.1. Portal Implementation
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.
2.1.1. Portuguese modified version
In the Portuguese modified version we adapted the workflow to be more aligned with the specs. It has the following behaviour:
- Select the "document search" for the chosen patient;
- Select if it is an EMERGENCY or NOT EMERGENCY situation;
- If it is an EMERGENCY you are transported imediatly to document search result (depending, of course, on Country A decision);
- if it is NOT AN EMERGENCY you must specify if the patient has given previous consent. The next workflow will depend on the selected option;
This steps can be explained by the following animated picture:
This modification was achieved mainly by changing the default confirmation page (viewPatientConfirmationForDocuments.xhtml), that now contains the following code:
<!DOCTYPE html PUBLIC "-W3CDTD XHTML 1.0 TransitionalEN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"
xmlns:h="http://java.sun.com/jsf/html"
xmlns:f="http://java.sun.com/jsf/core"
xmlns:ui="http://java.sun.com/jsf/facelets"
xmlns:p="http://primefaces.org/ui">
<h:head>
</h:head>
<body>
<h:form>
<p:panel header="#{translationBean.report_summary}">
<table>
<tr>
<td><b><h:outputText
value="#{translationBean.patient_data_givenname}" /></b></td>
<td> </td>
<td><h:outputText value="#{myBean.selectedPatient.name}" /></td>
</tr>
<tr>
<td><b><h:outputText
value="#{translationBean.patient_data_surname}" /></b></td>
<td> </td>
<td><h:outputText value="#{myBean.selectedPatient.familyName}" /></td>
</tr>
<tr>
<td><b><h:outputText
value="#{translationBean.patient_data_street_address}" /></b></td>
<td> </td>
<td><h:outputText value="#{myBean.selectedPatient.address}" /></td>
</tr>
<tr>
<td><b><h:outputText
value="#{translationBean.patient_data_code}" /></b></td>
<td> </td>
<td><h:outputText value="#{myBean.selectedPatient.postalCode}" /></td>
</tr>
<tr>
<td><b><h:outputText
value="#{translationBean.patient_data_city}" /></b></td>
<td> </td>
<td><h:outputText value="#{myBean.selectedPatient.city}" /></td>
</tr>
<tr>
<td><b><h:outputText
value="#{translationBean.patient_data_country}" /></b></td>
<td> </td>
<td><h:outputText value="#{myBean.selectedPatient.country}" /></td>
</tr>
</table>
</p:panel>
<p:panel
header="Confirmar com o doente (acesso aos seus dados clínicos):" id="confirmationPanel">
<p:outputPanel id="customPanel">
<td><b><h:outputText value="Atendimento:" /></b></td>
<p:selectOneRadio id="customRadio"
value="#{confirmationBean.purposeOfUse}" layout="custom">
<f:selectItem itemLabel=" EMERGENTE (não é possível obter o consentimento)"
itemValue="EMERGENCY" />
<f:selectItem itemLabel=" NÃO URGENTE"
itemValue="TREATMENT" />
<p:ajax update="confirmationPanel"/>
</p:selectOneRadio>
<h:panelGrid columns="2">
<p:radioButton id="opt2" for="customRadio" itemIndex="0" />
<h:outputLabel for="opt2" value=" EMERGENTE (não é possível obter o consentimento)" />
<p:radioButton id="opt1" for="customRadio" itemIndex="1" />
<h:outputLabel for="opt1" value=" NÃO URGENTE" />
</h:panelGrid>
</p:outputPanel>
<p:outputPanel rendered="#{confirmationBean.purposeOfUse=='TREATMENT'}" id="customPanel2">
<td><b><h:outputText
value="Deu consentimento prévio?" /></b></td>
<p:selectOneRadio id="customRadio2"
value="#{confirmationBean.confirm}" layout="custom">
<f:selectItem itemLabel="Yes" itemValue="Yes" />
<f:selectItem itemLabel="No" itemValue="No" />
</p:selectOneRadio>
<h:panelGrid columns="2">
<p:radioButton id="opt11" for="customRadio2" itemIndex="0" />
<h:outputLabel for="opt11" value=" Sim" />
<p:radioButton id="opt22" for="customRadio2" itemIndex="1" />
<h:outputLabel for="opt22" value=" Não" />
</h:panelGrid>
</p:outputPanel>
<p:commandButton id="submitButton"
value="Confirmar"
ajax="false"
action="/viewDocuments.xhtml?faces-redirect=true&javax.portlet.faces.PortletMode=view&javax.portlet.faces.WindowState=normal"
disabled="#{confirmationBean.purposeOfUse==null}"
onclick="customRadio.selectValue('')">
<p:resetInput target="confirmationPanel" />
<f:setPropertyActionListener value="#{confirmationBean.purposeOfUse}"
target="#{myBean.purposeOfUseForPS}" />
<f:setPropertyActionListener value="#{confirmationBean.confirm}"
target="#{myBean.previousConsent}" />
<f:setPropertyActionListener value="null"
target="#{confirmationBean.purposeOfUse}" />
<f:setPropertyActionListener value="null"
target="#{confirmationBean.confirm}" />
</p:commandButton>
<p:commandButton id="cancelButton" value="Cancelar" ajax="false"
action="/view1.xhtml?javax.portlet.faces.PortletMode=view&javax.portlet.faces.WindowState=normal" />
</p:panel>
</h:form>
</body>
</html>
2.2. Assertion type
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.
2.3. Audit message
In the current implementation there is no Audit Message whe the Emergency workflow is triggered;
The non-functional requirement NFR06 - Audit Trail, present int the document D3.2.2 "Final definition of functional service requirements" states the following:
"Extraordinary and/or emergency accesses must be specially marked in order to facilitate the local management of those."
Therefore an extra audit message needs to be triggered in this particular situations.
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.