DECOR Information for Project: epSOS (epsos-)

Scenarios

 PS (Patient Summary) 2012‑05‑02
The two use cases must be understood as an access to the PS.
  1. an occasional visitor in country B, for example someone on holiday or attending a business meeting. The distinguishing characteristic is that this type of visit is irregular, infrequent, and may not be repeated. This is a type of incidental encounter where the Health Care professional may have no previous record of the person seeking care.
  2. the person is a regular visitor to country B, for example someone who lives in one country but works in another country. The distinguishing characteristic is that this type of visit is regular, frequent, and the person seeking care may be accustomed to using services in the country where he or she works as a matter of personal convenience. This is a type of occasional situation where the Health Care professional may have some information available from previous encounters, therefore the patient could have a medical record locally stored in country B, and maybe a PS in country B plus in country A. If this is the case, both PSs should be available for the HCP to be consulted.

Name Id
PS (Patient Summary) 2.16.840.1.113883.2.4.3.11.60.30.3.1
Description
The two use cases must be understood as an access to the PS.
  1. an occasional visitor in country B, for example someone on holiday or attending a business meeting. The distinguishing characteristic is that this type of visit is irregular, infrequent, and may not be repeated. This is a type of incidental encounter where the Health Care professional may have no previous record of the person seeking care.
  2. the person is a regular visitor to country B, for example someone who lives in one country but works in another country. The distinguishing characteristic is that this type of visit is regular, frequent, and the person seeking care may be accustomed to using services in the country where he or she works as a matter of personal convenience. This is a type of occasional situation where the Health Care professional may have some information available from previous encounters, therefore the patient could have a medical record locally stored in country B, and maybe a PS in country B plus in country A. If this is the case, both PSs should be available for the HCP to be consulted.
doublearrow Transaction group id: 2.16.840.1.113883.2.4.3.11.60.30.4.1
Name Request PS/Return PS
Description In this first step or hop, HCP B will request the PS from country A by sending the request to his NCP B that routes the request to the next hop
You need SVG support in your browser for this image
Content
arrowright Transaction id: 2.16.840.1.113883.2.4.3.11.60.30.4.11
Name Request PS of country A
Description Once the identity of the patient is validated, the HCP of country B requests, with the consent of the patient (FR04), the PS of country A that can be visualized by HCP interface
Trigger Consult PS of country A
Dependencies Patient is identified, and has given consent
Model ClinicalDocument 
Label requestPS-step1 
Actor - Sender (organization)
Name HCP B
Description Health Care Provider B
Actor - Receiver (device)
Name NCP B
Description National Contact Point B
Representing template
Source data set 2.16.840.1.113883.2.4.3.11.60.22.1.1 epSOS Demo Data Set
arrowleft Transaction id: 2.16.840.1.113883.2.4.3.11.60.30.4.12
Name Return PS of country A
Description The NCP of country B conveys the PS of country A to HCP interface
Model ClinicalDocument 
Label returnPS-step1 
Actor - Sender (device)
Name NCP B
Description National Contact Point B
Actor - Receiver (organization)
Name HCP B
Description Health Care Provider B
Representing template
Template id 1.3.6.1.4.1.12559.11.10.1.3.1.1.3 (DYNAMIC) 
Source data set 2.16.840.1.113883.2.4.3.11.60.22.1.1 epSOS Demo Data Set
Contained concepts
Concept Card/Conf Id
folder Patient Data
1 .. 1 mandatory epsos-dataelement-5
Information about the patient
treetree folder Identification
1 .. 1 mandatory epsos-dataelement-6
Country ID, unique for the patient in that country. Example: ID for United Kingdom patient
treeblank treetree   National Health Care patient ID
1 .. 1 mandatory epsos-dataelement-7
Country ID, unique for the patient in that country.
treetree folder Personal Information
1 .. 1 mandatory epsos-dataelement-8
Personal information about the patient
treeblank treetree folder Full Name
1 .. 1 mandatory epsos-dataelement-9
The full name of the patient
treeblank treeblank treetree   Given name
1 .. 1 mandatory epsos-dataelement-12
The Name of the patient (Example: John). This field can contain more than one element
treeblank treeblank treetree   Family Name/Surname
1 .. 1 mandatory epsos-dataelement-13
This field can containe more than one element.
treeblank treetree   Date of Birth
1 .. 1 mandatory epsos-dataelement-10
The date of birth of the patient. This field may contain only the year if day and month are not available
treeblank treetree   Gender
0 .. 1 epsos-dataelement-11
It must contained a recognized valid value for this field.
treetree folder Contact Information
0 .. * epsos-dataelement-26
Contact information of the patient, including information of the contacts of the patient.
treeblank treetree folder Address
0 .. 1 epsos-dataelement-27
Address of the patient
treeblank treeblank treetree   Street
0 .. 1 epsos-dataelement-51
Name of street where the patient lives
treeblank treeblank treetree   Number of Street
0 .. 1 epsos-dataelement-52
House number where the patient lives
treeblank treeblank treetree   City
0 .. 1 epsos-dataelement-55
City where the patient lives
treeblank treeblank treetree   Postal Code
0 .. 1 epsos-dataelement-53
Postal code where the patient lives
treeblank treeblank treetree   State or Province
0 .. 1 epsos-dataelement-56
State or province where the patient lives
treeblank treeblank treetree   Country
0 .. 1 epsos-dataelement-54
Country where the patient lives
treeblank treetree   Telephone No
0 .. * epsos-dataelement-28
Telephone number of the patient
treeblank treetree   E-mail
0 .. * epsos-dataelement-29
E-mail address of the patient
treeblank treetree folder Preferred HCP to contact
0 .. 1 epsos-dataelement-30
Preferred Health Care Professional to contact. A foreign HCP may need a contact (HCP/legal organization) who knows the patient
treeblank treeblank treetree folder Full Name
0 .. 1 epsos-dataelement-46
Name of the HCP/name of the legal organization. If it is an HCP, the structure of the name will be the same as described in ‘Full name’ (Given name, family name/surname)
treeblank treeblank treeblank treetree   Given Name
0 .. 1 epsos-dataelement-47
The Name of the HCP (Example: John). This field can contain more than one element
treeblank treeblank treeblank treetree   Family Name/Surname
0 .. 1 epsos-dataelement-48
This field can contain more than one element.
treeblank treeblank treetree   Telephone No
0 .. * epsos-dataelement-41
Telephone number of the HCP/name of the legal organization
treeblank treeblank treetree   E-mail
0 .. * epsos-dataelement-43
E-mail address of the HCP/name of the legal organization
treeblank treetree folder Legal Organization to contact
0 .. 1 epsos-dataelement-31
Legal organization to contact about patient. A foreign HCP may need a contact (HCP/legal organization) who knows the patient
treeblank treeblank treetree   Organization Name
0 .. 1 epsos-dataelement-33
Name of the organization
treeblank treeblank treetree   Telephone No
0 .. * epsos-dataelement-49
Telephone number of the organization
treeblank treeblank treetree   E-mail
0 .. * epsos-dataelement-50
E-mail address of the organization
treeblank treetree folder Contact Person/legal guardian
0 .. * epsos-dataelement-34
Contact or guardian of the patient
treeblank treeblank treetree   Role of that person
0 .. 1 epsos-dataelement-35
The role of the person: contact person or legal guardian
treeblank treeblank treetree folder Full Name
0 .. 1 epsos-dataelement-36
Full name of the contact person or guardian
treeblank treeblank treeblank treetree   Given Name
0 .. 1 epsos-dataelement-37
The Name of the person (Example: John). This field can contain more than one element
treeblank treeblank treeblank treetree   Family Name/Surname
0 .. 1 epsos-dataelement-38
This field can contain more than one element.
treeblank treeblank treetree   Telephone No
0 .. * epsos-dataelement-39
Telephone number of the person
treeblank treeblank treetree   E-mail
0 .. * epsos-dataelement-40
E-mail address of the person
treetree folder Insurance Information
0 .. 1 epsos-dataelement-14
Information about the insurance of the patient
treeblank treetree   Insurance Number
0 .. 1 epsos-dataelement-15
European Health Insurance Code (EHIC) number of the patient
folder Clinical Data
0 .. * epsos-dataelement-16
Clinical information of the patient
treetree folder Medical Problems
0 .. * epsos-dataelement-82
treeblank treetree folder Surgical Procedures in the past six months
0 .. * epsos-dataelement-91
treeblank treeblank treetree   Procedure description
0 .. 1 epsos-dataelement-92
Describes the type of procedure that has been executed as part of the healthcare event.
treeblank treeblank treetree   Procedure Id (code)
0 .. 1 epsos-dataelement-93
Normalized identifier
treeblank treeblank treetree   Procedure Date
0 .. 1 epsos-dataelement-94
Date when procedure was performed
folder Patient Summary Data
1 .. 1 mandatory epsos-dataelement-62
Information about the PS itself
treetree   Country
1 .. 1 mandatory epsos-dataelement-63
Name of country A
treetree folder Patient Summary
1 .. 1 mandatory epsos-dataelement-64
treeblank treetree   Date Created
1 .. 1 mandatory epsos-dataelement-65
Data on which PS was generated
treeblank treetree folder Author HCP
0 .. 1 epsos-dataelement-67
To highlight if the data is collected manually by an HCP or is collected automatically form different sources (eg: hospital doctor repository, GPs...etc) through predetermine clinical rules.
treeblank treeblank treetree   Identification
1 .. 1 mandatory epsos-dataelement-22
Unique identification of the Health Care Professional.
treeblank treeblank treetree folder Full Name
1 .. 1 mandatory epsos-dataelement-19
The full name of the Health Care Professional
treeblank treeblank treeblank treetree   Given Name
1 .. 1 mandatory epsos-dataelement-20
The Name of the HCP (Example: John). This field can contain more than one element
treeblank treeblank treeblank treetree   Family Name/Surname
1 .. 1 mandatory epsos-dataelement-21
This field can contain more than one element.
treeblank treeblank treetree folder Healthcare Facility
0 .. 1 epsos-dataelement-23
Information about the healthcare facility where the health care professional works
treeblank treeblank treeblank treetree   Identifier
1 .. 1 mandatory epsos-dataelement-25
Unique identification of the healthcare facility
treeblank treeblank treeblank treetree   Name
1 .. 1 mandatory epsos-dataelement-24
Name of the healthcare facility

Scenario Summary

Scenarios 1
Transaction groups 1
Transactions 2

Transactions per Actor

Transactions for Actor organization: HCP A

Role Type Transaction Model Representing template

Transactions for Actor organization: HCP B

Role Type Transaction Model Representing template
  Group Request PS/Return PS    
Sender initial    Request PS of country A ClinicalDocument
Receiver back    Return PS of country A ClinicalDocument 1.3.6.1.4.1.12559.11.10.1.3.1.1.3 (DYNAMIC)

Transactions for Actor device: NCP A

Role Type Transaction Model Representing template

Transactions for Actor device: NCP B

Role Type Transaction Model Representing template
  Group Request PS/Return PS    
Receiver initial    Request PS of country A ClinicalDocument
Sender back    Return PS of country A ClinicalDocument 1.3.6.1.4.1.12559.11.10.1.3.1.1.3 (DYNAMIC)

Data sets, codes, OIDs and Rules: this information is used for rendering and validation purposes.