CDA R3 Allow Entries for nonXMLBody
See CDA R3 Formal Proposals for instructions on using this form. Failure to adhere to these instructions may result in delays. Editing of formal proposals is restricted to the submitter and SDTC co-chairs. Other changes will be undone. Comments can be captured in the associated discussion page.
|Submitted by: Rick Geimer||Revision date: May 20, 2009|
|Submitted date: May 20, 2009||Change request ID: <<Change Request ID>>|
There are many cases where organizations have existing human readable content in the form of PDFs, etc. that they wish to exchange along with computable content. Currently CDA does not allow a nonXMLBody to contain entries, thus implementers must choose between their existing presentation format or the computable content.
- I propose allowing coded entries inside a nonXMLBody to facilitate the exchange of coded data along with non-XML content for human display.
- If we have already decided that non-XML content like PDFs are sufficient for display, why do we prohibit the ability to add coded content as well?
- I have heard some organizations outside the U.S. state that they are required to send pre-formatted files with actual readable signatures, etc. (someone at IHIC told me this...didn't catch their name, so it is strictly anecdotal).
- If approved, need to decide if sections are needed or not. They would only exist for grouping the entries, there would still likely be just one external file forming the human readable nonXMLBody.
Recommended Action Items
Feb 23 SDWG - not approved. If there is a need to capture entries, then one should use structuredBody. in favor: 9; opposed: 0; abstain: 0.