1 / 17

Data Provenance Tiger Team

Data Provenance Tiger Team. May 9 th , 2014. Johnathan Coleman - Initiative Coordinator Lynette Elliott – Tiger Team Support Bob Yencha – Subject Matter Expert Ioana Singureanu – Modeling Facilitator Kathleen Connor – Subject Matter Expert

zorina
Télécharger la présentation

Data Provenance Tiger Team

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. Data Provenance Tiger Team May 9th, 2014 Johnathan Coleman - Initiative Coordinator Lynette Elliott – Tiger Team Support Bob Yencha – Subject Matter Expert Ioana Singureanu – Modeling Facilitator Kathleen Connor – Subject Matter Expert Neelima Chennamaraja - Modeling Facilitator

  2. Agenda

  3. Meeting Etiquette • Please mute your phone when you are not speaking to prevent background noise. • All meetings are recorded. • Please do not put your phone on hold. • Hang up and dial back in to prevent hold music. • Use the “Chat” feature to ask questions or share comments. • Send chats to “All Participants” so they can be addressed publicly in the chat, or discussed in the meeting (as appropriate). Click on the “chat” bubble at the top of the meeting window to send a chat.

  4. Data Provenance Tiger TeamHL7 Project Scope Statement Update • Project Scope Statement (PSS) submitted for “Provenance for Clinical Document Architecture (CDA R2) Documents Implementation Guide” • Approved by HL7 US Task Force (4/29/14) • Discussed with Domain Experts Steering Division (DESD) on 5/5/14 in Phoenix. Feedback received from several WGs and incorporated into PSS • Revised PSS approved by HL7 Community Based Collaborative Care (CBCC) WG (5/7/14) with substantial input from Security WG • Revised PSS submitted to DESD for approval (voting to close no later than 5/28/14) • Next Steps: • Pending DESD approval, PSS will be submitted to Technical Steering Committee (TSC) for approval

  5. Data Provenance Tiger Team HL7 September 2014 Ballot Consensus/ End-to-end Review Data Provenance HL7 Project Scope Statement (May 18) HL7 Notification of Intent to Ballot (June 29) HL7 Ballot (Aug 8- Sept 8) HL7 WG Meeting (Sept 14-19) HL7 HL7 Ballot Reconciliation (Sept. 8-Nov. 21) HL7 DSTU Publication Dec. ‘14 HL7 Initial Content Deadline (Jul .13) Milestones HL7 Final Content Due (Aug. 3) Today

  6. Tiger Team Timeline

  7. Draft Guide and Model • Using MDHT for model development and publication production • Draft iterations will be posted to S&I wiki for comment – but recognize the development of an HL7 specification is subject to HL7 community consensus progress • Initial draft has boilerplate and example text, content to be developed as result of TT work • Will be edited to conform to HL7 publishing guidelines • Begin to capture working definitions, sync with HL7, et al, and parent initiative glossary

  8. Requirements Review • Metric for this ballot sprint: what can we support now? • Remainder to go to parking lot and main initiative • Focus on goals outlined in the HL7 Provenance PSS • What other aspects besides authorship, time and location of entry, etc, need to be exposed?

  9. Requirements Review • Review requirements and support in CDA at: • Header Level • Section Level • Entry / Clinical Statement Level • Landscape survey of Provenance related information in existing HL7 standards

  10. Proposed CDA Development Approach • Develop Provenance Class at entry level? • Review and adapt/adopt Provenance Class patterns from existing artifacts: • FHIR Provenance Resource • Order Response EventControlAct • FHIM Provenance Class • DS4P CDA Provenance Constraints • What else is avail in HL7?

  11. Data Provenance Tiger TeamNext Steps • Monitor wiki for updated draft based on todays work • Requests for community input • Submit any potential requirement not previously discussed or included in draft IG for discussion on next meeting • Identify any other candidate source IGs for review • Next Meeting – Monday, May 19 @ 3:00PM ET

  12. Questions?

  13. Data Provenance Tiger TeamBackground Slides The following slides are included as references and for quick access when/if needed

  14. Resources • Tiger Team wiki • http://wiki.siframework.org/Data+Provenance+Tiger+Team • Main Initiative wiki • http://wiki.siframework.org/Data+Provenance+Initiative • HL7 project wiki…

  15. Data Provenance Tiger Team Mission and Charter Tiger Team Mission and Charter To help achieve Data Provenance Initiative goals, the ONC Data Provenance Tiger Team will: • Accelerate the progress of the Initiative by getting a head start on standards harmonization. • Support the development of policy agnostic yet policy enablingtechnical standards that address prioritized initiative use case requirements.

  16. Data Provenance Tiger Team Scope • Focus on the initial set of standards required for Meaningful Use, and develop provenance-specific guidance and/or technical specifications for the initiative to use as building blocks in support of a more broadly applicable solution. • Assist the initiative with detailed analysis of candidate standards for system functional requirements and interoperable exchange of data as directed by the initiative. • Propose additional standards development activities to further initiative goals.

  17. Tiger Team Initial Targets • Develop a content specification for all CDA IGs to enhance Data Provenance support • Building blocks for re-use • Backwards compatible • Transport is out of scope for TT, but we will monitor and inform the work as necessary • Assume a generic workflow, e.g., Transitions of Care to guide analysis • Document the value sets and vocabulary bindings to support provenance-related CDA data element as required by the initiative

More Related