This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Add ProfileId to ClinicalDocument"
Jump to navigation
Jump to search
Rene spronk (talk | contribs) (New page: {{CDA R3 Open Proposals}} Return to SDTC page; Return to CDA R3 Formal Proposals page. {|width=100% cellspacing=0 cellpa...) |
Rene spronk (talk | contribs) |
||
| Line 13: | Line 13: | ||
== Issue == | == Issue == | ||
| − | The templateId of the CDA Header Act is current used for multiple purposes. One of those purposes is the identification of the implementation guide that a CDA instance complies with. | + | The templateId of the CDA Header Act is current used for multiple purposes. One of those purposes is the identification of the implementation guide that a CDA instance complies with. |
| + | |||
| + | HL7 has two attributes to | ||
| + | #identify the [[Profile]] ([[Implementation Guide|implementation guide]]) an instance complies with ([RIM Definition for the Message class]) | ||
| + | #identify the Template (a [[LIM]]) a pat of the instance complies with ([http://www.hl7.org/v3ballot2008sep/html/infrastructure/rim/rim.htm#InfrastructureRoot-templateId-att RIM definition]) | ||
== Recommendation == | == Recommendation == | ||
| − | *Create RIM proposal to add a ProfileId attribute | + | *Create RIM proposal to add a ProfileId attribute to the ClinicalDocument class. |
| − | + | *A Template differs from a Profile. There should be a separate attribute to identify the profile. | |
| + | *This would allow the implementation guide (which is essentially a set of templates AND a series of non-software processable business rules) to be identified in a different way than a template. | ||
== Rationale == | == Rationale == | ||
Revision as of 06:47, 5 February 2009
Return to SDTC page; Return to CDA R3 Formal Proposals page.
| Submitted by: Rene Spronk | Revision date: 2009-01-21 |
| Submitted date: <<Submit Date>> | Change request ID: n.a. |
Issue
The templateId of the CDA Header Act is current used for multiple purposes. One of those purposes is the identification of the implementation guide that a CDA instance complies with.
HL7 has two attributes to
- identify the Profile (implementation guide) an instance complies with ([RIM Definition for the Message class])
- identify the Template (a LIM) a pat of the instance complies with (RIM definition)
Recommendation
- Create RIM proposal to add a ProfileId attribute to the ClinicalDocument class.
- A Template differs from a Profile. There should be a separate attribute to identify the profile.
- This would allow the implementation guide (which is essentially a set of templates AND a series of non-software processable business rules) to be identified in a different way than a template.
Rationale
Discussion
Recommended Action Items
- Implement the recommendation
Resolution
(Resolution is to be recorded here and in the referenced minutes, which are the authoritative source of resolution).
