70 likes | 157 Views
<insert Profile Proposal Name>. Brief Profile Proposal for 2009/10 presented to the IT Infrastructure Planning Committee <insert profile author here> <insert date here>. The Problem.
E N D
<insert Profile Proposal Name> Brief Profile Proposal for 2009/10 presented to the IT Infrastructure Planning Committee <insert profile author here> <insert date here>
The Problem • Current XDS Metadata requires a set of metadata that is appropriate for XDS Document Registries but is not possible to generate in all XDR and XDM cases, particularly when the document source is not an EHR or equivalent (see use case) • In some case (motivated by Nationwide Health Information Network Direct Project use cases) the XDR/XDM packager is working with documents expressed as a byte stream, and must create a metadata package. • Failure to address this issue in this cycle will require the Direct Project to propose use of non-conformant metadata that is not on a standards track to make conformant
Use Case • Dr. Smith is referring a patient to Dr. Jones. Dr. Smith’s referral coordinator uses her e-mail or web e-communication application to write a textual summary of the referral and attaches a set of PDF formatted scanned documents. Dr. Smith’s office does not use a complete EHR; the competition for this workflow is the Fax machine. The web application sends an XDR SOAP message to Dr. Jones’ system.
Proposed Standards & Systems • This proposal relates to XDS Metadata, which we recommend re-terming XD* Metadata (as it is used for other profiles as well) • We recommend the creation of at least two levels of conformant metadata • Current XDS metadata • Minimal metadata • We foresee the need for other possible levels. E.g. • PatientID exists, but other required metadata does not • Use of metadata to package data not associated with a single specific patient • As currently specified, the use case is not achievable with conformant metadata
Discussion • Level of effort is minimal, particularly if the suggestions of the Direct Project are used as a starting point: • http://nhindirect.org/XDD+Specification • Arien Malec will serve as proposal editor: • Arien Malec • Arien.malec@nhindirect.org • (510) 761-6473 • Other relevant comments