This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Remove constraint on entryRelationship within CDA-Body"
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
| − | {{CDA R3 | + | {{CDA R3 Approved Proposals}} |
Return to [[Structured Documents TC|SDTC]] page; Return to [[:category:CDA R3 Formal Proposals|CDA R3 Formal Proposals]] page. | Return to [[Structured Documents TC|SDTC]] page; Return to [[:category:CDA R3 Formal Proposals|CDA R3 Formal Proposals]] page. | ||
| Line 28: | Line 28: | ||
== Resolution == | == Resolution == | ||
| + | March 23, 2010: Agree with the need for full set of typeCodes in entryRelationship (and reference clone if it persists based on other proposals). Opposed: 0; Abstain: 0; In favor: 6. | ||
Latest revision as of 20:42, 23 March 2010
Return to SDTC page; Return to CDA R3 Formal Proposals page.
| Submitted by: Frank Oemig | Revision date: 29.09.09 |
| Submitted date: 16.07.09 (proposal), 29.09.09 (formal proposal) | Change request ID: <<Change Request ID>> |
Issue
- CDA R2 provides a link between entry on level 3. The typeCode of this entryRelationship is limited to ActRelationshipEntryRelationship. The same should be done with reference from the entries to external references. The limitation prevents from using richer semantics. Especially links to external documents when used with fine granular information would help to indicate concrete relationships.
Recommendation
- Allow all typeCodes to be used.
Rationale
Discussion
Recommended Action Items
Resolution
March 23, 2010: Agree with the need for full set of typeCodes in entryRelationship (and reference clone if it persists based on other proposals). Opposed: 0; Abstain: 0; In favor: 6.
