1 / 6

Data Provenance –Use Case (Discovery) Ahsin Azim– Use Case Lead Presha Patel – Use Case Lead

Data Provenance –Use Case (Discovery) Ahsin Azim– Use Case Lead Presha Patel – Use Case Lead. Proposed Use Case & Functional Requirements Development Timeline. Sections for Review. Today we will be reviewing: Pre/Post Conditions Introduce: Actors & Roles Activity Diagrams Base Flows.

grover
Download Presentation

Data Provenance –Use Case (Discovery) Ahsin Azim– Use Case Lead Presha Patel – Use Case Lead

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 –Use Case (Discovery) Ahsin Azim– Use Case Lead Presha Patel – Use Case Lead

  2. Proposed Use Case & Functional Requirements Development Timeline

  3. Sections for Review Today we will be reviewing: Pre/Post Conditions Introduce: Actors & Roles Activity Diagrams Base Flows Double click the icon to open up the Word Document with the sections for review

  4. Pre/Post Conditions • Post Conditions • Receiving system has incorporated provenance information into its system and association of the provenance information to the source data is persisted • Sending and receiving systems have recorded the transactions in their security audit records Preconditions • Where it exists, the assembling software, is integrated into systems such as EHRs, PHRs, and HIEs – indicating the type of information for a receiver to use as provenance for calculating reliability, and the organization or person responsible for deploying it • There exists an Access Control System that allow the assembler to perform necessary tasks for predecessor artifacts and newly assembled artifacts • All systems generating or consuming any artifact are capable of persisting the security labels received and data segmentation based the security labels assigned by the artifact generator, which may be an assembler

  5. A look ahead: Data Provenance Next Week • July 24th, 2014 – All Hands Community Meeting (2:30-3:30) • Review Actors & Roles, Activity Diagrams and Base Flows Provide your comments on the bottom of this page http://wiki.siframework.org/Data+Provenance+Use+Cases

  6. Support Team and Questions Please feel free to reach out to any member of the Data Provenance Support Team: • Initiative Coordinator: Johnathan Coleman: jc@securityrs.com • OCPO Sponsor: Julie Chua: julie.chua@hhs.gov • OST Sponsor: Mera Choi: mera.choi@hhs.gov • Subject Matter Experts: Kathleen Conner: klc@securityrs.com and Bob Yencha: bobyencha@maine.rr.com • Support Team: • Project Management: Jamie Parker: jamie.parker@esacinc.com • Use Case Development: Presha Patel: presha.patel@accenture.comand Ahsin Azim: ahsin.azim@accenturefederal.com • Harmonization: Rita Torkzadeh:rtorkzadeh@jbsinternational.com • Standards Development Support: Amanda Nash: amanda.j.nash@accenturefederal.com • Support: Lynette Elliott:lynette.elliott@esacinc.com and Apurva Dahria: apurva.dahria@esacinc.com

More Related