Versions Compared

Old Version 65

changes.mady.by.user Marcelo Fonseca

Saved on

compared with

New Version Current

changes.mady.by.user Licinio Kustra Mano

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Section
bordertrue
Column

Column

The purpose of this page is to provide a better clarification on the specification of the implementation of the Patien Access Service on the OpenNCP scope.

Note

To discuss this page please use the following issue:

Jira Legacy
serverJIRA (openncp.atlassian.net)
serverId5eab37ce-f509-3cbb-9925-c13d0f8d6d44
keyPT-178

______________________________

PAC Service Implementation Overall Status

Gadget
preferencesprojectOrFilterId=filter-10803&statType=statuses&sortBy=natural&sortDirection=asc&includeResolvedIssues=true&isConfigured=true&refresh=30
authorMarcelo Fonseca
urlhttps://openncp.atlassian.net/rest/gadgets/1.0/g/com.atlassian.jira.gadgets:stats-gadget/gadgets/stats-gadget.xml

Column
width30
Table of contents:

Table of Contents
stylesquare

1. Scenarios Clarification

Goals

The goals of the main actor, the patient, in UC.PAC.1 is to access and understand what the Health Professional has recorded in the PS or eP, in order to:

  • Participate in his or her own care, and/or to improve the information he or she gives to a New Health Professional;

Actors

The actors involved in the epSOS PAC Use Case are:

...

Diagram 1: Use case diagram

2. Requirements

Actions & Steps

StepsActions
1

(This step is in the National Domain, and is a prerequisite for the PAC service)

  • The patient affiliated in Country A requests access to PS or eP in Country A, by contacting the Country A National Patient Access Service
  • The patient identifies himself
  • The National Patient Access system verifies the patient’s authorization
  • The National Patient Access system retrieves the document
2

The Patient requests an epSOS translation of the retrieved document

3

The National Patient Access system passes the request to the epSOS NCP in Country A

4

The epSOS NCP in Country A provides a dialogue for selecting the source and target language (Language A, Language B)

5

The National Patient Access system sends the document (in Language A) to the epSOS NCP in Country A

6

The NCP-A transforms (transcodes) the document indicated (or received) from Patient Access system into a translatable epSOS pivot document and then makes this pivot document available to the translation responsible.

7

The translation responsible retrieves the epSOS MTC of Language B

8

The translation responsible translates the pivot document and makes the translated document in language B available to the NCP of country A

9

The NCP of country A conveys the information translated into the interface of the National Patient Access system

10

The patient accesses the translated document in his specific device display

11

The use case is finished/closed


EXCEPTIONS

  • The translation responsible does not have access to the epSOS MTC of language B.
  • The translation responsible informs NCP of country A of the failure.
  • The NCP A cannot inform the Patient Access System about the failure.

Basic Service Functional Requirements

FR01Patient Access Basic Requirement
Description

The Patient must have the possibility to access his/her own medical information available at his/her national PA service ( affiliation’s country) and get it translated into any epSOS country language Specific PA services asks first its NCP-A for PS/eP translation service. As a consequence NCP-A requests a translation. Each translation request to an NCP-A must include these parameters

1. Affiliation country where the Patient has identified/authenticated himself
2. Language of the Patient accessing the PA Interface
3. Selected output language ( translation language requested )
4. Language of document (the health information) accessed

Associated Goals
  • Existing PS/eP in epSOS network must be available to patients either in his own language or in any of the languages of the participating PNs. After the identification of the patient who requests healthcare, in country A or B, the patient requests through a simple action (just a click) the visualization of the PS/eP in the selected language (that one that fits either with his own language or with that of the health care professional).
  • The patient must be able to access his usual national Patient Access service.
  • National PA service asks NCP-A for the list of available translations service , and this list is sent and presented to specific Patient access service including for each access date/time of access.
Actors

1. Patient
2. Specific national patient access service
3. NCP A

Preconditions
  • Pre-existence of national Patient access service
  • Pre-existence of epSOS NCPs, at both sides at the country having Patient access and in the output language requested by the patient.

...

FR08

Consultation of PoC through the patient access service -  OPTIONAL

Description

For this service the steps in the country National Domain are the same as above for eP/PS. For the realm of epSOS the National Patient Access system retrieves the PoC through the NCP or from the epSOS website.

The patient must be able to consult available PoC in the area where he is interested in for any type of health care providers (e.g. hospitals, healthcare centers and pharmacies).

It is a Browsing function returning the list of all PoC in the specified territory value set.

The patient triggers the event; the requested Point of Care in an area is the origin of the event; the Service consumer is NCP that triggered the event

Associated Goals
  • Give guided access to epSOS web site maps/PoC.
  • Guided offer of a collection of retrieved PoC in www.epSOS.eu
Actors
  • Patient = Active participant
  • Passive participant /object= Directory/Value set of epSOS PoC www.epSOS.eu
  • Patient Access system calls NCP-A for this service
Preconditions
  • Availability of PoC in the requested area (not mandatory). Return value may be zero.
  • Correct PoC maintenance in www.epsos.eu is under responsibility of the NABs

Service Legal Requirements

For service legal requirements please consult the D 1.4.3, page 112;

Service Security Requirements

For service security requirements please consult the D 1.4.3, page 114;

Service Clinical Requirements

For service clinical requirements please consult the D 1.4.3, page 115.

Service Usability and Data Presentation Requirements

For service usability and data presentation requirements please consult the D 1.4.3, page 117.

Additional Architecture NCP / Central Service requirements

For additional Architecture NCP / Central Service requirements please consult the D 1.4.3, page 122.

3. Clarification

The purpose of this topic is to clarify some remaining questions and doubts about the Patient Access specification of OpenNCP.

  • Can the service workflow be accomplished using the NCP-B + Portal-B?

4. Implementation Strategy Design

4.1. Overview

Multiple ways can be followed in order to implement the Patient Access service on the OpenNCP. The most direct one is to make use of existent components and implemented services. Others will require further development.

4.2. Solution A: Re-use the Portal-B + NCP-B as Patient Access and Translation Service

Basic solution diagram

In order to promote the maximum components re-use we can define the following table to map the required PAC service elements into the existent OpenNCP components:

...

StepsActionsOpenNCP actions and operations descriptionTo be implemented in OpenNCPRelated Profiles
1

(This step is in the National Domain, and is a prerequisite for the PAC service)

  • The patient affiliated in Country A requests access to PS or eP in Country A, by contacting the Country A National Patient Access Service
  • The patient identifies himself
  • The National Patient Access system verifies the patient’s authorization
  • The National Patient Access system retrieves the document
  • The patient will access to the Portal-B Patient section;
  • The portal will use its "Portal-B" capabilities to query the Patient Documents based on the Patient Identifier, using the NCP-B;
  • The retrieved (as whole document) or available (as list) documents are presented to the user;
  • The patient may retrieve the document (if it isnt yet) or move to next step;

A Portal-B Patient Section, with the following aspects:

  1. New Patient Role;
  2. Section navigation filtered, according to user role;
  3. Default document search, constrained to the user id (not possible to user other id);
XCPD, XCA
2

The Patient requests an epSOS translation of the retrieved document

  • (Portal GUI)

(Described further bellow)

 
3

The National Patient Access system passes the request to the epSOS NCP in Country A

  • Not required
  
4

The epSOS NCP in Country A provides a dialogue for selecting the source and target language (Language A, Language B)

  • The patient selects the target language for the document at the portal and requests the document;
  • The Portal performs a request to the NCP-B, also specifying the translation language selected by the patient;

Target language selection for translating a document at the Portal-B patient section;

  1. List of available languages must be displayed;
 
5

The National Patient Access system sends the document (in Language A) to the epSOS NCP in Country A

  • The NCP-B then requests the document at the NCP-A
Already supported;XCA
6

The NCP-A transforms (transcodes) the document indicated (or received) from Patient Access system into a translatable epSOS pivot document and then makes this pivot document available to the translation responsible.

  • The NCP-A request the document at the National Connector and transforms it to epSOS Pivot
Already supported;XCA
7

The translation responsible retrieves the epSOS MTC of Language B

  • (NCP-B operation, using TM)
Already supported by TM; 
8

The translation responsible translates the pivot document and makes the translated document in language B available to the NCP of country A

  • The NCP-B retrieves the document from NCP-A and translates it to the target language;

Adapt Client Connector to support language specification when retrieving a document;

  1. Include extra language parameter in the document retrieve request message;
XCA
9

The NCP of country A conveys the information translated into the interface of the National Patient Access system

  • The NCP-B returns the document to the Portal;
Already supported;XCA
10

The patient accesses the translated document in his specific device display

  • The Portal displays the document using the specific XSLT resources

Adapt portal to support multiple XSLT for each language;

Possibly add PDF production feature (for easier portability and printing);

 
11

The use case is finished/closed


EXCEPTIONS

  • The translation responsible does not have access to the epSOS MTC of language B.
  • The translation responsible informs NCP of country A of the failure.
  • The NCP A cannot inform the Patient Access System about the failure.
   
Implementation Mapping with existent Workflows

Assumptions - Example

  • Country B is Greece;
  • Country A is Italy;

Existing Portal-B workflow

PAC Workflow

Pharmacist accesses Greek Portal-B

Italian Patient accesses Italian Portal-B

1. hcp asserion

1. hcp asserion (needs to be specified new role and permissions for patient). I am not sure if patient is an HCP (healthcare point)

2. identification service (finds an Italian patient)

2. identification service (the system automaitically identifies itself, the patient stores to the portal the personal identifiers needed for matching with the patient)

3. TRC Assertion

3. TRC Assertion (the system automatically creates a trca with purpose of treatment, new role has to be defined)

4. patient service

4. patient service (the system automatically retrieves list of documents)

5. Consent handling if needed

5. Retrieval and display of document (translation of document not needed, it's in italian language already, no transformation needed)

6. Retrieval of document (translation of document in country b language - greek in this occasion)

6. Consent handling must be part of ncp-a in order to allow patient to see its own data

...

So if the patient role had permissions on patient service he could probably see his documents

Implementation Issues / Tasks:

Portal-B

Gadget
filterIdfilter-10800
isConfiguredtrue
preferencesfilterId=filter-10800&num=10&columnNames=summary%7Cdescription%7Cissuekey%7Cpriority%7Cassignee%7Cstatus&isConfigured=true&refresh=30
columnNamessummary|description|issuekey|priority
authorMarcelo Fonseca
num10
width100%
refresh30
urlhttps://openncp.atlassian.net/rest/gadgets/1.0/g/com.atlassian.jira.gadgets:filter-results-gadget/gadgets/filter-results-gadget.xml

...

Gadget
filterIdfilter-10801
isConfiguredtrue
preferencesfilterId=filter-10802&num=10&columnNames=summary%7Cdescription%7Cissuekey%7Cpriority%7Cassignee%7Cstatus&isConfigured=true&refresh=30
columnNamessummary|description|issuekey|priority|assignee|status
authorMarcelo Fonseca
num10
width100%
refresh30
urlhttps://openncp.atlassian.net/rest/gadgets/1.0/g/com.atlassian.jira.gadgets:filter-results-gadget/gadgets/filter-results-gadget.xml

Considerations
  • In this scenario we will re-use all the existent components to meet the PAC Service requirements;
  • Some security issues need to be taken into account, in order to restrict the retrieval of "patient-only" documents;

 

4.3. Solution B: Newly create Patient Access and Translation Service components

In this option we would need to expose an additional service for translation purposes only at NCP-A, skipping the re-use of NCP-B.

(To be completed if required) 

 

4.4. Solution C: Use Transformation Manager and National Connector library as Portal dependencies

With this solution we would have the Portal communicating directly with the National Infrastructure, using the already implemented National Connector (by the OpenNCP PNs). The translation would be performed by the Transformation Manager, added also directly as a dependency of the Portal.

...

StepsActionsPortal actions and operations descriptionTo be implemented in the PortalRelated Profiles
1

(This step is in the National Domain, and is a prerequisite for the PAC service)

  • The patient affiliated in Country A requests access to PS or eP in Country A, by contacting the Country A National Patient Access Service
  • The patient identifies himself
  • The National Patient Access system verifies the patient’s authorization
  • The National Patient Access system retrieves the document
  • The patient will access to the Portal-B Patient section;
  • The portal will use its National Connector implementation dependency to query the Patient Documents based on the Patient Identifier;
  • The retrieved (as whole document) or available (as list) documents are presented to the user;
  • The patient may retrieve the document (if it isnt yet) or move to next step;

A Portal-B Patient Section, with the following aspects:

  1. New Patient Role;
  2. Section navigation filtered, according to user role;
  3. Default document search, constrained to the user id (not possible to user other id);
NI specific
2

The Patient requests an epSOS translation of the retrieved document

  • (Portal GUI)

(Described further bellow)

 
3

The National Patient Access system passes the request to the epSOS NCP in Country A

  • Not required
  
4

The epSOS NCP in Country A provides a dialogue for selecting the source and target language (Language A, Language B)

  • The patient selects the target language for the document at the portal and requests the document;

Target language selection for translating a document at the Portal-B patient section;

  1. List of available languages must be displayed;
 
5

The National Patient Access system sends the document (in Language A) to the epSOS NCP in Country A

  • Not required
  
6

The NCP-A transforms (transcodes) the document indicated (or received) from Patient Access system into a translatable epSOS pivot document and then makes this pivot document available to the translation responsible.

  • The Portal uses the Transformation Manager toEpsosPivo() operation to transform the document to epSOS Pivot
The Transformation Manager toEpsosPivot() invocation; 
7

The translation responsible retrieves the epSOS MTC of Language B

  • Transformation Manager operations, using the LTR, shared with the NCP;
Already supported by TM; 
8

The translation responsible translates the pivot document and makes the translated document in language B available to the NCP of country A

  • The Portal uses the Transformation Manager translate() operation to translate the document to the requested language

The Transformation Manager translate() invocation;

 
9

The NCP of country A conveys the information translated into the interface of the National Patient Access system

  • The Portal obtains the result of the Transformation Manager translate() operation
  
10

The patient accesses the translated document in his specific device display

  • The Portal displays the document using the specific XSLT resources

Adapt portal to support multiple XSLT for each language;

Possibly add PDF production feature (for easier portability and printing);

 
11

The use case is finished/closed


EXCEPTIONS

  • The translation responsible does not have access to the epSOS MTC of language B.
  • The translation responsible informs NCP of country A of the failure.
  • The NCP A cannot inform the Patient Access System about the failure.
   

5. Test Strategy Design

(To be defined after strategy validation)

6. References

Attachments
uploadfalse
patternsD1.4.*