60 likes | 135 Views
IG Development Working Session. September 4 th , 2013. Meeting Etiquette. From S&I Framework to Participants: Hi everyone: remember to keep your phone on mute . All Panelists. Remember: If you are not speaking, please keep your phone on mute
E N D
IG Development Working Session September 4th, 2013
Meeting Etiquette From S&I Framework to Participants: Hi everyone: remember to keep your phone on mute All Panelists • Remember: If you are not speaking, please keep your phone on mute • Do not put your phone on hold. If you need to take a call, hang up and dial in again when finished with your other call • Hold = Elevator Music = frustrated speakers and participants • This meeting is being recorded • Another reason to keep your phone on mute when not speaking • Use the “Chat” feature for questions, comments and items you would like the moderator or other participants to know. • Send comments to All Panelists so they can be addressed publically in the chat, or discussed in the meeting (as appropriate). 2
Agenda 3
II05 Payload – Submit Completed Form Data from EHR System to External Data Repository
II05 Service – Submit Completed Form Data from EHR System to External Data Repository
For discussion with All Hands WG • Response from the External Data Repository • To this date, a generic “acknowledgement” has been discussed as being in-scope for the SDC Use Case and IG development • What are the implications on our stakeholders / the Use Case? • Discuss and add a section in the IG regarding the acknowledgement and error conditions, rather than adding a new transaction • Error-handling is implementation-specific and complex per the needs of a domain-specific form • Considerations: maintaining data downstream, need for secondary form submission • Pre-Condition for data validation prior to sending? • Implications on the sender and/or the receiver? • All kinds of combinations for how this could be handled • A traceable receipt will be invaluable in development as well as production environments • Discuss use of CDA Consent Directive IG with XML Value Pairs • Would have to be separate items for the transaction to carry that information? Or would they be carried together as separate pieces under a transaction document • Data Segmentation for Privacy reinforces this use • Consent Directive can include sensitive information as well • What is the consideration from privacy/security community? • Transaction Metadata vs. Form Metadata • IHE Publication Cycle Understanding