1 / 19

Data Provenance Tiger Team

Data Provenance Tiger Team. May 19 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

livia
Download Presentation

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 19th, 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 • See the TT Wiki page for links to G-Forge • No log-in required • Most current version of draft document will always be available there • Provide comments via the TT wiki page

  8. Requirements Review • CDA Source of Information - Guidelines and Strategy v1.0 092811_FOR RELEASE.pdf • Topics • Creating CDA • Use of CDA header elements • Authors and informants, e.g., primary document authors and contributors • Aggregator vs. author • Aggregate CDA • Traceability of parts as docs move across affinity domains • Lifecycle/lifespan parameters • Implications at the document, section and entry level

  9. Discussion points • Authoring Entities • Medical devices & software • Humans – Providers, administrative staff from various organizations, etc. • Validate the need to differentiate patient, provider, or payer information: • Revise the ParticipationFunction codes proposed to identify patient, payer, and providers sources • “PAT”, “PAYOR”, “PROV” <!-- @typeCode="PPRF" for Primary Perfomer--><participant typeCode="PPRF"><!-- @classCode="PAT“, "PAYOR" or "PROV" --><associatedEntityclassCode=“PAT"> • Record target • Identify all the patient identifiers in the document header instead of using an extension for secondary identifiers <id root=“…" extension=“…" assigningAuthorityName=“Organization"/> • Author vs. Aggregate • Author – to create new content • Aggregation – combine from existing sources • Algorithmically derived vs. “copy and paste” with new content

  10. Original CDA Documents • One document per organization Document Record Target: Patient id (primary and alternates) Document Author Device: Aggregation Software Represented organization Document Informant: Qualified Organization overrides Entry Informant: Sub-organization Sub-organization of… Represented organization Entry Author:Aggregation Software Entry Record:Org-specific patient id Secondary identifier may be redundant

  11. Original CDA Documents • One document per organization, author overriden Document Record Target: Patient id Document Author Device: Aggregation Software Represented organization Document Informant: Qualified Organization Document InformantProvider – Overrides individual provider, same org. Entry Informant : Identified Provider Represented organization Entry Author:Aggregation Software

  12. Aggregate CDA Documents • One document, auto-generated, from multiple organization and sub-organizations Primary identifier may be accompanied by secondary identifiers Document Record Target: Patient identifiers by organization Document Author Device: Aggregation Software Represented organization Document Informant: State HIE overrides Section Author Device: Software Represented organization Section Informant: Organization overrides Entry Informant: Sub-organization Represented organization Sub-organization of… Entry Author:Aggregation Software Assigning organization Entry Record:Org-specific patient id Secondary identifier may be redundant

  13. Data Provenance Tiger TeamNext Steps • Monitor wiki for updated draft based on todays work • Please use the comment capture form on the wiki • Requests for community input • Submit any potential requirement not previously discussed or included in draft IG for discussion on next meeting on the wiki Requirements page • Identify any other candidate source IGs for review • Next Meeting – Monday, June 2 @ 3:00PM ET

  14. Questions?

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

  16. Resources • Tiger Team wiki • http://wiki.siframework.org/Data+Provenance+Tiger+Team • G-Forge repository for draft model/IG • http://gforge.hl7.org/gf/project/cbcc/frs/?action=FrsReleaseBrowse&frs_package_id=240 • Main Initiative wiki • http://wiki.siframework.org/Data+Provenance+Initiative • HL7 project wiki • http://wiki.hl7.org/index.php?title=HL7_Data_Provenance_Project_Space

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

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

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