Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

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


Table of contents:

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 HCP

Secondary actors:

  • Patient identification, authentication & role authorization service;
  • The epSOS Patient Access translation service;

Diagram 1: Use case diagram

 

Requirements

.

Basic Service Functional Requirements

dgfh

Non-Functional Requirements

.

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.

Changes to the OpenNCP Architecture

Implementation Design

  • No labels