Loading...
Help
Login
Busy
Search
epSOS - Issues
 
Select object
Results (1 / 1)
Id Issue Status Priority Type Date Assigned To Label
253Adapt conformancy of family and given elements conform the EXPAND specificationsFeedback neededNormalChange Request2018-01-09 12:38:14Mathias Ghys
 
Change RequestAdapt conformancy of family and given elements conform the EXPAND specifications
Idepsos-issue-253
StatusFeedback needed
PriorityNormal
Last Tracking2018-01-09 12:38:14  by  Christof Gessner
Current AssigneeMathias Ghys
    
Concerns
Template
epSOS CDA legalAuthenticator (epsos-template-109)
/
/
Template2.16.840.1.113883.3.1937.777.11.10.109 (2013-12-20) epSOS CDA legalAuthenticator
StatusDraft

/
-
/
-

Events
TrackingFeedback needed2018-01-09 12:38:14: Tracking by Christof Gessner
Description
OK. I removed the contain statement.

Note that the intention to make those fields mandatory will fail if not all enclosing elements are also mandatory. Otherwise, the sender can just use a nullFlavor on one of the enclosing levels.
TrackingFeedback needed2018-01-09 12:11:44: Tracking by Dr. Kai U. Heitmann
Description
It is now a containment AND an subsequent inline definition.
Suggest to remove the containment and to just leave the subsequent inline definition. If the subsequent inline definition is repeatedly used, follow Giorgio's suggestion also to create a separate template and include it there.
TrackingFeedback needed2018-01-09 11:47:35: Tracking by Giorgio Cangioli
Description
It is not clear to me what it has been done...I see for the hl7:assignedPerson both 
AND
  • included elements overlapping that template
I suggest to create a specialization of that template with names mandatory or remove the contains and define explicitly all the needed sub-elements of the assignedPerson 
TrackingClosed2018-01-09 11:02:20: Tracking by Christof Gessner
Edited byChristof Gessner (2018-01-09 11:09:14)
Description
I agree and support this change. In order to make this item mandatory, I also changed the enclosing assignedEntity to mandatory. (That's how I would read the EXPAND specs)

I also added the additional text from the EXPAND specs in the description, in order to support the implementers.
TrackingClosed2018-01-09 10:10:08: Tracking by Mathias Ghys
Assignment2018-01-09 10:05:09: Assigned To Mathias Ghys by Mathias Ghys
TrackingOpen2018-01-09 10:05:08: Tracking by Mathias Ghys
Description
Finding:

- In EXPAND, the elements are defined with conformancy 'R' and not 'RFNA', so in ART-DECOR the conformancy should change to 'M' to be consistent. This issue popped up in the gap analysis

Suggestion:

- change the conformancy

Further explanation:

-

    
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