Embed Size (px)
DESCRIPTION
Test Procedure Example. Scenario 1- Push/Directed Exchange (Share all, Share partial) . Test Procedure. Per Scenario Per user story Sending System Receiving System Steps based on the user stories References to IG conformance Primary focus on privacy metadata. Inspection testing. - PowerPoint PPT Presentation
Citation preview
Test Procedure Example
Scenario 1- Push/Directed Exchange (Share all, Share partial)
Test Procedure
• Per Scenario– Per user story• Sending System• Receiving System
• Steps based on the user stories• References to IG conformance – Primary focus on privacy metadata
Choreography User Story 1: Setup and Testing the Sending EHR system
«Business trigger»Patient Requests Disclosure
Patient was notified of 42 CFR Part 2 privacy
1. Clerk records privacy consentin EHRS allowing Patient X data
to be transmitted to thedesignated PCP.
«EHR Data»Privacy Consent
Preferences
«Sending System» ADATP EHR SystemAlcohol and Drug Abuse Treatment Program (ADATP)
Verify the privacy consent is persisted by the EHR
2. Provider sets up Patient Xdata to transmitted to the PCP
upon discharge.
Data is missing or incomplete
3. Provider discharge Patient X
«Outbound Message»Data specified to be sent to the
PCP
Verify data disclosed and intended recipient match the privacy consent preferences
4. EHRS sends PatientX data electronicallyto the intended PCP
Complete scenario
Metadata or data is incorrect/incomplete.
The specific trigger for an electronic transmissionis triggered may vary across systems.
confidentiality = R (Restricted)purpose = treatmentintended recipient = Patient X PCPadditional obligation= do not redisclosedata set = all data
3.1.1.1.1. Identify information that is restricted/protectedby policy3.1.1.1.3. Add privacy metadata to health information disclosed to other organizations 5.4. Provide Patient Data and Restrictions on Use of Data
3.6. Section Level Tagging 3.7.2. Conformance Criteria for Segmentation Vocabularies 3.8.2. Purpose of Use Value Set 3.8.3. Healthcare Facility Type Codes 3.8.6. Use of Obligation Codes 3.8.6.1. Obligation Code Value Set7.1. Sending a set of clinical documents with differing levels of tagging 7.2. Sending a discharge summary in a care transition
«Test Suite» Sending System Testing
Verify disclosure was logged by the sending system
Log disclosureevent
Logging failed
fail
pass
fail
failedpass
pass
Choreography User Story 1: Setup and Testing the Sending EHR system
«Business trigger»Patient Requests Disclosure
Patient was notified of 42 CFR Part 2 privacy
1. Clerk records privacy consentin EHRS allowing Patient X data
to be transmitted to thedesignated PCP.
«EHR Data»Privacy Consent
Preferences
«Sending System» ADATP EHR SystemAlcohol and Drug Abuse Treatment Program (ADATP)
Verify the privacy consent is persisted by the EHR
2. Provider sets up Patient Xdata to transmitted to the PCP
upon discharge.
Data is missing or incomplete
3. Provider discharge Patient X
«Outbound Message»Data specified to be sent to the
PCP
Verify data disclosed and intended recipient match the privacy consent preferences
4. EHRS sends PatientX data electronicallyto the intended PCP
Complete scenario
Metadata or data is incorrect/incomplete.
The specific trigger for an electronic transmissionis triggered may vary across systems.
confidentiality = R (Restricted)purpose = treatmentintended recipient = Patient X PCPadditional obligation= do not redisclosedata set = all data
3.1.1.1.1. Identify information that is restricted/protectedby policy3.1.1.1.3. Add privacy metadata to health information disclosed to other organizations 5.4. Provide Patient Data and Restrictions on Use of Data
3.6. Section Level Tagging 3.7.2. Conformance Criteria for Segmentation Vocabularies 3.8.2. Purpose of Use Value Set 3.8.3. Healthcare Facility Type Codes 3.8.6. Use of Obligation Codes 3.8.6.1. Obligation Code Value Set7.1. Sending a set of clinical documents with differing levels of tagging 7.2. Sending a discharge summary in a care transition
«Test Suite» Sending System Testing
Verify disclosure was logged by the sending system
Log disclosureevent
Logging failed
fail
pass
fail
failedpass
pass Inspection testing
Set up
Choreography User Story 1: Setup and Testing the Sending EHR system
«Business trigger»Patient Requests Disclosure
Patient was notified of 42 CFR Part 2 privacy
1. Clerk records privacy consentin EHRS allowing Patient X data
to be transmitted to thedesignated PCP.
«EHR Data»Privacy Consent
Preferences
«Sending System» ADATP EHR SystemAlcohol and Drug Abuse Treatment Program (ADATP)
Verify the privacy consent is persisted by the EHR
2. Provider sets up Patient Xdata to transmitted to the PCP
upon discharge.
Data is missing or incomplete
3. Provider discharge Patient X
«Outbound Message»Data specified to be sent to the
PCP
Verify data disclosed and intended recipient match the privacy consent preferences
4. EHRS sends PatientX data electronicallyto the intended PCP
Complete scenario
Metadata or data is incorrect/incomplete.
The specific trigger for an electronic transmissionis triggered may vary across systems.
confidentiality = R (Restricted)purpose = treatmentintended recipient = Patient X PCPadditional obligation= do not redisclosedata set = all data
3.1.1.1.1. Identify information that is restricted/protectedby policy3.1.1.1.3. Add privacy metadata to health information disclosed to other organizations 5.4. Provide Patient Data and Restrictions on Use of Data
3.6. Section Level Tagging 3.7.2. Conformance Criteria for Segmentation Vocabularies 3.8.2. Purpose of Use Value Set 3.8.3. Healthcare Facility Type Codes 3.8.6. Use of Obligation Codes 3.8.6.1. Obligation Code Value Set7.1. Sending a set of clinical documents with differing levels of tagging 7.2. Sending a discharge summary in a care transition
«Test Suite» Sending System Testing
Verify disclosure was logged by the sending system
Log disclosureevent
Logging failed
fail
pass
fail
failedpass
pass
References to IG conformance
criteria
References to IG conformance
criteria (functional)
SendingSystem
Choreography User Story 1: Setup and Testing the Receiving System
«Receiving System» PCP EHR System
1. Process transmission
2. User requestsinformation, the systemdisplays CDA documents
Patient X data and privacy metadata
Verify that the data is persisted correctly in the receiving system
Missing/incomplete data
Verify that the privacy notice is displayed
Document(s) are invalid, missing information, missing privacy notice
Rendered Patient X data and privacy metada
Procedure complete
3.1.1.2.1. Process privacy metadata associated health information received from other organizations.
3.6. Section Level Tagging 3.7.2. Conformance Criteria for Segmentation Vocabularies 3.8.2. Purpose of Use Value Set 3.8.3. Healthcare Facility Type Codes 3.8.6. Use of Obligation Codes 3.8.6.1. Obligation Code Value Set7.1. Sending a set of clinical documents with differing levels of tagging 7.2. Sending a discharge summary in a care transition
«Test Suite» Receiving SystemTesting
Receive directed transmission
passed
passed
References to IG conformance
criteria
References to IG conformance
criteria (functional)
Inspection testing
Receiving System
Business Process User Story 1: Sending EHR Testing Procedure
«Test» Validate Privacy ConsentPersistence
«Test» Validate disclosed data«Test» Validate Disclosure
Logging
Verify disclosure was logged by the sending system
Logging failed
2. Verifiy CDA R2Header
3. Verify (optional)Section Level Tagging
1. Verify ConsentPersistence
4. Verify (optional)Entry-level Tagging
5. Verify Purposeof Use Value Set
6. Verify (optional)Healthcare Facility Type
Codes
7. Verify the use ofObligation Codes
failed
Setti
ng u
p th
e te
st…
.
Business Process User Story 1: Receiving System Testing Procedure
«Test» Validate Inbound Data Persistence«Test» Validate data displayed
1. Verify CDA headermetadata is
persisted
7.Verify Data Contents and PrivacyRe-Diclosure Notification
2. Verify (optional) SectionLevel Tag Persistence
3. Verify (optional) Entry LevelTag Persistence
4. Verify the Purposeof Use is persisted
correctly
5. Verify (optional) HealthcareFacility Type Code persistence
6.Verify the persistence ofObligation Codes
Test
Ste
ps…
.
Choreography User Story 1.A: Setup and Testing the Sending System
«Sending System» ADATP EHR System «Test Suite» Sending System Testing
«Business Trigger»Patient needs specialist referral
1. Clerk records privacyconsent in EHRS allowingfor part of the protected
data to be disclosed.
«EHR Data»Privacy Consent
Preferences
Verify privacy consent is persisted in the EHR system
Data missing or incomplete.
2. Provider sendsinformation along with
referral/consult to Specialist
«Outbound Message»Data specified to be sent to
the Specialist
Verify data disclosed and intended recipient match privacy consent
Metadata or Data incomplete or incorrect.
3. Log disclosure event
Complete scenario
Verify disclosure was logged
Logging failedpass
fail
pass
pass
fail
fail
Setti
ng u
p th
e se
ndin
g EH
R te
st…
.
Business Process User Story 1.A: Sending System Testing Procedure
«Test» Validate Privacy ConsentPersistence
«Test» Validate disclosed data subset«Test» Validate disclosure
logging
Verify disclosure was logged
Logging failed
1. Verify ConsentPersistence
2. Verify CD R2Header
3. Verify (optional)Section Level Tagging
4. Verify (optional) EntryLevel Tagging
5. Verify Purposeof Use
6. Verify (optional) HealthcareFacility Type Codes
7. Verify the user ofObligation Codes
8. Verify partial data set
fail
Send
ing
EHR
Test
Pro
cedu
re S
teps
Choreography User Story 1.A: Setup and Testing the Receiving System
«Receiving System» Specialist EHR System «Test Suite» Receiving System Actor Testing
Receive directed transmission
1. Processtransmission
«EHR Data»Patient data and privacy metadata
Verify that the data is persisted correctly in the receiving system Missing/incomplete
data
2. User requestsinformation, the
system displays CDAdocuments
«EHR Display»Rendered Patient data and privacy metadata
Verify that the privacy notice is displayed
Document(s) are invalid, missing information, missing privacy notice
Procedure completed
pass
pass
fail
Setti
ng u
p th
e te
st…
.
Collaboration User Story 1.A: Receiving System Testing Procedure
«Test» Validate Inbound Data Persistence
1. Verify CDA headermetadata is peristed
2. Verify (optional) SectionLevel Tag Persistence
3. Verify (optional) EntryLevel Tag Persistence
4. Verify the Purpose ofUse is Persisted correctly
5. Verify (optional)Healthcare Facility Type
Code persistence
6. Verify Obligation Codespersistence
«Test» Validate data displayed
7. VerifyPartialData Disclosed
8. Verify DataContents
Rece
ivin
g EH
R Te
st P
roce
dure
Ste
ps
Test
Inspection testing• Identifies testable
capability and specifies criteria
• Scenario and user story specific
• Reference to IG
![Product Introduction: MX283027A Wireless Network Device ... · [Example of Rx test procedure]*4 Set DUT to Rx mode.*1 Switch test signal path to Rx test system. Input WLAN test signals](https://img.dokumen.tips/doc/110x75/5eac6d7e7b9e9d4c094a4c69/product-introduction-mx283027a-wireless-network-device-example-of-rx-test.jpg)
