1. Testing Procedures for DS4P Summary testing approach, addressing requirements traceability, and Scenario 4 update

2. What’s new? An approach to testing that focuses DS4P-specific aspects – Based on complex/composite privacy policies Identify those aspects that enables interoperability – Simple privacy metadata – NEW to DS4P – Reuse of existing transports – Reuse of existing best-practices for trigger, logs, provenance, etc. Requirement Traceability – Organized to focus on the DS4P-specific criteria Scenario 4 – Title 38 Pull Scenarios 2, 3, 5,6 – Due next Monday

3. Privacy Policies and Interoperability Privacy Policies are typically composites of simple, basic policies Composite privacy policies (e.g. 42CFR Part)comprise of several basic, computable data sharing policies Privacy metadata used to represent simple data sharing policies: Confidentiality level Purpose of use/disclosure Information source is a covered substance abuse treatment Consent required for disclosure/re-disclosure – Privacy metadata allows loosely-coupled systems and organization to exchange the most meaningful metadata related to the data shared among systems/organizations Information exchanged may reference basic data sharing policies as privacy metadata – Confidentiality Code – Purpose of Use Code – Obligation Code – Refrain Policy Code 42 CFR Part 2 Purpose = Treatment Obligation= Require Consent Confidentiality = Restricted Basic Data Sharing Policy Composite Privacy Policy

4. Privacy Metadata used in Information Exchange to specify simple data exchange policies across organizations For treatment purpose No re-disclosure Restricted Summary Document Transport Metadata Document Section

5. Senders determine what information is protected and marks it “restricted” in the document Restricted document Summary Document

6. DS4P Specifics are the focus of our inspection testing We need to specify the OID

7. Summary Conformance Statements can be organized into – Data segmentation specific – Transport- specific – Generic best practice E.g. use ATNA

9. Conformance Criteria are used as traceability requirements Conformance statements related to confidentiality codes Conformance statements related to facility codes

10. Errors are easy to spot: obligation code intended to use obligation or refrain policy? Repetitive reference the same value set could be avoided

11. Confidentiality Code Functional Obligation/Refrain Purpose of use Data Criteria Privacy Consent Provenance Extensions – entry-level Data Segmentation Conformance Criteria Sender/Receiver Policy-based functionality

13. Patient changes mind and…

14. … the new preferences recorded…

15. … applied to segmentation.

16. Sending System Test Procedure Change mind...

17. Receiving System Process Procedure repeated after the patient changes her mind...

18. Receiving System Test Procedure Change mind...