Loading...
Help
Login
Busy
Search
epSOS - Issues
 
Select object
Results (1 / 1)
Id Issue Status Priority Type Date Assigned To Label
31Value set epSOSPersonalRelationship without dataset bindingClosedNormalRequest for Information/Education2016-03-17 17:53:46Giorgio Cangioli
 
 M1 
 
Request for Information/EducationValue set epSOSPersonalRelationship without dataset binding
Idepsos-issue-31
StatusClosed
PriorityNormal
Last Tracking2016-03-17 17:53:46  by  Giorgio Cangioli
Current AssigneeGiorgio Cangioli
Current Labels
    
 (M1) Milestone 1 
    
Concerns
Value Set
epSOSPersonalRelationship (epSOSPersonalRelationship)
/
NameepSOSPersonalRelationshipDisplay NameepSOSPersonalRelationship
Version2013-06-03StatusDraft
Version Label913-20091020IdepSOSPersonalRelationship
Description
The Value Set is used (optionally) to code the type of contact relationship between a person and the patient.
Source Codesystems
2.16.840.1.113883.5.111Role Codehttp://terminology.hl7.org/CodeSystem/v3-RoleCode
Values
Level/TypeCodeDisplay NameCodesystemDescription
0-L
AUNT
aunt
2.16.840.1.113883.5.111
0-L
CHILD
child
2.16.840.1.113883.5.111
0-L
CHLDADOPT
adopted child
2.16.840.1.113883.5.111
0-L
CHLDFOST
foster child
2.16.840.1.113883.5.111
0-L
CHLDINLAW
child in-law
2.16.840.1.113883.5.111
0-L
COUSN
cousin
2.16.840.1.113883.5.111
0-L
DAU
natural daughter
2.16.840.1.113883.5.111
0-L
DAUADOPT
adopted daughter
2.16.840.1.113883.5.111
0-L
DAUC
daughter
2.16.840.1.113883.5.111
0-L
DAUFOST
foster daughter
2.16.840.1.113883.5.111
0-L
DAUINLAW
daughter in-law
2.16.840.1.113883.5.111
0-L
DOMPART
domestic partner
2.16.840.1.113883.5.111
0-L
FAMMEMB
family member
2.16.840.1.113883.5.111
0-L
FRND
unrelated friend
2.16.840.1.113883.5.111
0-L
FTH
father
2.16.840.1.113883.5.111
0-L
FTHINLAW
father-in-law
2.16.840.1.113883.5.111
0-L
GGRPRN
great grandparent
2.16.840.1.113883.5.111
0-L
GRNDCHILD
grandchild
2.16.840.1.113883.5.111
0-L
GRPRN
grandparent
2.16.840.1.113883.5.111
0-L
MTH
mother
2.16.840.1.113883.5.111
0-L
MTHINLAW
mother-in-law
2.16.840.1.113883.5.111
0-L
NBOR
neighbor
2.16.840.1.113883.5.111
0-L
NCHILD
natural child
2.16.840.1.113883.5.111
0-L
NIENEPH
niece/nephew
2.16.840.1.113883.5.111
0-L
PRN
parent
2.16.840.1.113883.5.111
0-L
PRNINLAW
parent in-law
2.16.840.1.113883.5.111
0-L
ROOM
roomate
2.16.840.1.113883.5.111
0-L
SIB
sibling
2.16.840.1.113883.5.111
0-L
SIGOTHR
significant other
2.16.840.1.113883.5.111
0-L
SON
natural son
2.16.840.1.113883.5.111
0-L
SONADOPT
adopted son
2.16.840.1.113883.5.111
0-L
SONC
son
2.16.840.1.113883.5.111
0-L
SONFOST
foster son
2.16.840.1.113883.5.111
0-L
SONINLAW
son in-law
2.16.840.1.113883.5.111
0-L
SPS
spouse
2.16.840.1.113883.5.111
0-L
STPCHLD
step child
2.16.840.1.113883.5.111
0-L
STPDAU
stepdaughter
2.16.840.1.113883.5.111
0-L
STPSON
stepson
2.16.840.1.113883.5.111
0-L
UNCLE
uncle
2.16.840.1.113883.5.111
Legenda: Type L=leaf, S=specializable, A=abstract, D=deprecated. NullFlavors to appear in @nullFlavor attribute instead of @code.

/
-
/
-

Events
TrackingClosed2016-03-17 17:53:46: Tracking by Giorgio Cangioli
    
 M1 
Description
Modified the binding for the /ClinicalDocument/participant/associatedEntity/code 
TrackingOpen2015-11-18 10:44:30: Tracking by Giorgio Cangioli
    
 M1 
Description

Expected to be used for the /ClinicalDocument/participant/associatedEntity/code template (1.3.6.1.4.1.19376.1.5.3.1.2.4 Patient Contact)

(to be better evaluated if also for the guardian/code)

Assignment2013-11-28 17:20:28: Assigned To Giorgio Cangioli by Alexander Henket
Description
The only element that comes close is "The role of the person: contact person or legal guardian", but as it says in the description that needs two concepts that are not intrinsically part of this PersonalRelationship value set. My fear is that we're somehow missing something in the dataset
TrackingOpen2013-10-16 13:52:13: Tracking by Alexander Henket
Description
Issue:

This value set does not have a clear binding to anything in the dataset. Advice needed for mapping.

    
Labels
PreviewCodeHTML colorDisplay NameDescription
 
 TBA 
TBATBATo be approved
To be discussed and approved
 
 M1 
M1M1Milestone 1
Milestone 1 – before the EXPAND-athon 9-12 December 2015 Lisbon
 
 M2 
M2M2Milestone 2
Milestone 2 – final results to be delived at the end of EXPAND
 
 M3 
M3M3Milestone 3
Milestone 3 – end of the HL7 International Project
 
 M4 
M4M4Milestone 4
Milestone 4 – for consideration in the future / desiderata
 
 WJ 
WJWJChanges Word/JIRA
Changes in the Word Specification/Open a JIRA issue
 
 TID 
TIDTIDTemplate ID
Template-ID changes throughout the specification