1 / 6

IG Development Working Session

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

dalton-nielsen
Download Presentation

IG Development Working Session

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. IG Development Working Session September 4th, 2013

  2. 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

  3. Agenda 3

  4. II05 Payload – Submit Completed Form Data from EHR System to External Data Repository

  5. II05 Service – Submit Completed Form Data from EHR System to External Data Repository

  6. 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

More Related