Difference between revisions of "CDA R3 allow HXIT in patient attributes"
| 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 31: | Line 31: | ||
== Resolution == | == Resolution == | ||
April 6, 2010 SDWG: Grahame will update wiki page with recommendations. | April 6, 2010 SDWG: Grahame will update wiki page with recommendations. | ||
| + | Sept 9, 2010: Committee will need to better understand use of HXIT, particularly as it applies to Header elements. Will add this proposal to workplan for now, without necessarily approving the use case. We need to determine if HXIT can be constrained in Header, and if so, where and how we would do it. Opposed: 0; abstain: 0; in favor: 13. | ||
Latest revision as of 15:07, 9 September 2010
Return to SDTC page; Return to CDA R3 Formal Proposals page.
| Submitted by: Nick Radov | Revision date: <<Revision Date>> |
| Submitted date: 09/20/2009 | Change request ID: <<Change Request ID>> |
Issue
Within a clinical document it's sometimes useful to know when particular patient attribute values were valid. For example, an old MRN could be superseded by a new format, people frequently move to new addresses, women get married and change family names, etc.
CDA R2 supports the EN.validTime property for names, but it doesn't allow use of the HXIT generic type extension for II, AD, and TEL values. It would be nice if CDA R3 could support HXIT attributes for other data types.
Recommendation
In CDA R3, allow use of the HXIT.validTime property for all of the identity and demographic attributes of the Patient and Person RIM classes.
Rationale
Discussion
We may get some of this automatically by virtue of using data types R2.
Recommended Action Items
Resolution
April 6, 2010 SDWG: Grahame will update wiki page with recommendations. Sept 9, 2010: Committee will need to better understand use of HXIT, particularly as it applies to Header elements. Will add this proposal to workplan for now, without necessarily approving the use case. We need to determine if HXIT can be constrained in Header, and if so, where and how we would do it. Opposed: 0; abstain: 0; in favor: 13.
