6
Draft Dataset Requirements Will Be Reviewed On: September 4 th Data Provenance - All Hands Meeting

Draft Dataset Requirements Will Be Reviewed On: September 4 th Data Provenance - All Hands Meeting

Embed Size (px)

Citation preview

Page 1: Draft Dataset Requirements Will Be Reviewed On: September 4 th Data Provenance - All Hands Meeting

Draft Dataset Requirements

Will Be Reviewed On: September 4th Data Provenance - All Hands Meeting

Page 2: Draft Dataset Requirements Will Be Reviewed On: September 4 th Data Provenance - All Hands Meeting

Dataset Requirements Discussion

2

• For the purposes of this Use Case, the Dataset Requirements will focus on the data elements pertaining to provenance for the clinical data, including the handling of that data, recognizing that it may contain data from multiple sources– Who, When, Where, Type, Routing Information, Integrity/Authenticity, Sources

• In order to capture the provenance data elements, we propose that we discuss the data elements within these categories: Data Source, Transmitter, Assembler, and Composer. We recognize there may be overlap across these categories.

• As a reminder: – The Dataset Requirements define data from a functional standpoint, not from a

technical perspective– We will use this section to figure out to what extent the standards can adhere to the

requirements (not specifications) – The Dataset Requirements for the Use Case are standards agnostic

• The following slides serve as a starter set to begin the discussion and brainstorming of Dataset Requirements; this will eventually be put into a structured format in the Use Case document

Page 3: Draft Dataset Requirements Will Be Reviewed On: September 4 th Data Provenance - All Hands Meeting

Dataset Requirements - Source

3

• Who– Sending System; Sending System Organization; Author; Custodian; Attester; Role;

etc.

• When– Create Date; Create Time; etc.

• Where– Address; State; Zip; etc.

• Type– Software; Device; etc.

Question for Community: What are the important attributes of

provenance that the dataset must contain?

Page 4: Draft Dataset Requirements Will Be Reviewed On: September 4 th Data Provenance - All Hands Meeting

Dataset Requirements - Transmitter

4

• Who– Transmitter; Transmitter Organization; etc.

• When– Transmittal Date; Transmittal Time; etc.

• Where– Address; State; Zip; etc.

• Type– Software; Device; etc.

• Routing Information– Information sent to/from

• Integrity/Authenticity– In order to trust the data, do you need to know about how it was handled/who handled it/has

it been altered since it was created????

Page 5: Draft Dataset Requirements Will Be Reviewed On: September 4 th Data Provenance - All Hands Meeting

Dataset Requirements - Assembler

5

• Who– Assembler System; Assembler Organization; etc.

• When– Assembly Date, Assembly Time, etc.

• Where– Address; State; Zip; etc.

• Type– Software; Device; etc.

• Integrity/Authenticity– In order to trust the data, do you need to know about how it was handled/who handled it/has

it been altered since it was created????

• Sources– What is the provenance of the information that was assembled????

Page 6: Draft Dataset Requirements Will Be Reviewed On: September 4 th Data Provenance - All Hands Meeting

Dataset Requirements - Composer

6

• Who– Composer; Composer Organization; etc.

• When– Composition Date; Composition Time; etc.

• Where– Address; State; Zip; etc.

• Type– Software; Device; etc.

• Integrity/Authenticity– In order to trust the data, do you need to know about how it was handled/who handled it/has

it been altered since it was created????

• Sources– What is the provenance of the information that was assembled????