Skip to content

Commit

Permalink
update procedure yaml for 2023 svap
Browse files Browse the repository at this point in the history
  • Loading branch information
Jammjammjamm committed Nov 9, 2023
1 parent abd538c commit 47d3bd0
Showing 1 changed file with 116 additions and 24 deletions.
140 changes: 116 additions & 24 deletions lib/onc_certification_g10_test_kit/onc_program_procedure.yml
Original file line number Diff line number Diff line change
Expand Up @@ -78,6 +78,7 @@ procedure:
- 4.1.01
- 5.1.01
- 6.1.01
- 10.1.01
- 7.1.01
- 7.2.01
- 7.3.01
Expand Down Expand Up @@ -513,7 +514,8 @@ procedure:
adopted in § 170.213 and implementation specification adopted in
§ 170.215(a)(2).
If using US Core 3.1.1, 4.0.0, or 5.0.1, these resources include:
If using US Core 3.1.1, 4.0.0, 5.0.1, or 6.1.0 these resources include:
* “AllergyIntolerance”;
* “CarePlan”;
* “CareTeam”;
Expand All @@ -530,11 +532,18 @@ procedure:
* “Procedure”; and
* “Provenance”.
Additionally, the following resources must be supported if using US
Core 5.0.1:
The following resources must also be supported if using US Core 5.0.1:
* “Encounter”;
* “RelatedPerson”; and
* “ServiceRequest”
The following resources must also be supported if using US Core 6.1.0:
* "Encounter"
* "Coverage"
* "Specimen"
* "MedicationDispense"
* "RelatedPerson"; and
* "ServiceRequest"
TLV: |
[Both] The tester verifies the ability of the Health IT Module to
evaluate the authorization request and request end-user input, if
Expand All @@ -544,7 +553,8 @@ procedure:
associated with the profiles specified in the standard adopted in
§ 170.213 and implementation specification adopted in § 170.215(a)(2).
If using US Core 3.1.1, 4.0.0, or 5.0.1, these resources include:
If using US Core 3.1.1, 4.0.0, 5.0.1, or 6.1.0 these resources include:
* “AllergyIntolerance”;
* “CarePlan”;
* “CareTeam”;
Expand All @@ -561,11 +571,19 @@ procedure:
* “Procedure”; and
* “Provenance”.
Additionally, the following resources must be supported if using US
Core 5.0.1:
The following resources must also be supported if using US Core 5.0.1:
* “Encounter”;
* “RelatedPerson”; and
* “ServiceRequest”
The following resources must also be supported if using US Core 6.1.0:
* "Encounter"
* "Coverage"
* "Specimen"
* "MedicationDispense"
* "RelatedPerson"; and
* "ServiceRequest"
inferno_supported: 'yes'
inferno_tests:
- 1.3.02
Expand All @@ -580,8 +598,8 @@ procedure:
- 2.1.05
- 2.2.02
- 2.2.05
- 1.7.01 - 1.7.16
- 2.3.01 - 2.3.15
- 1.7.01 - 1.7.20
- 2.3.01 - 2.3.19
inferno_notes: |
Inferno verifies that end-user input is requested by requiring one app
launch have complete access to required resources and having one app
Expand Down Expand Up @@ -611,8 +629,8 @@ procedure:
- 2.1.05
- 2.2.02
- 2.2.05
- 1.7.01 - 1.7.16
- 2.3.01 - 2.3.15
- 1.7.01 - 1.7.20
- 2.3.01 - 2.3.19
inferno_notes: |
Inferno verifies that end-user input is requested by requiring one app
launch have complete access to required resources and having one app
Expand Down Expand Up @@ -643,8 +661,8 @@ procedure:
- 2.1.05
- 2.2.02
- 2.2.05
- 1.7.01 - 1.7.16
- 2.3.01 - 2.3.15
- 1.7.01 - 1.7.20
- 2.3.01 - 2.3.19
inferno_notes: |
Inferno verifies that end-user input is requested by requiring one app
launch have complete access to required resources and having one app
Expand Down Expand Up @@ -901,17 +919,17 @@ procedure:
- 9.9.10
- id: AUT-PAT-32
SUT: |
[EHR-Launch] The following must be supported if using US Core 5.0.1:
The health IT developer demonstrates the ability of the Health IT
Module to return an “Encounter” FHIR® resource that matches the
[EHR-Launch] The following must be supported if using US Core 5.0.1 or
6.1.0: The health IT developer demonstrates the ability of the Health
IT Module to return an “Encounter” FHIR® resource that matches the
encounter context provided in step AUT-PAT-9 of this section according
to the implementation specification adopted in § 170.215(a)(2).
TLV: |
[EHR-Launch] The following must be supported if using US Core 5.0.1:
The tester verifies the ability of the Health IT Module to return an
“Encounter” FHIR® resource that matches the encounter context provided
in step AUT-PAT-9 of this section according to the implementation
specification adopted in § 170.215(a)(2).
[EHR-Launch] The following must be supported if using US Core 5.0.1 or
6.1.0: The tester verifies the ability of the Health IT Module to
return an “Encounter” FHIR® resource that matches the encounter
context provided in step AUT-PAT-9 of this section according to the
implementation specification adopted in § 170.215(a)(2).
inferno_supported: 'yes'
inferno_tests:
- 3.3.13
Expand Down Expand Up @@ -1873,10 +1891,10 @@ procedure:
- 10.38.05 - 10.38.06
- 10.39.08 - 10.39.09
- 10.40.02 - 10.40.03
- 10.41.02 - 10.40.03
- 10.42.02 - 10.40.03
- 10.43.02 - 10.40.03
- 10.44.03 - 10.40.04
- 10.41.02 - 10.41.03
- 10.42.02 - 10.42.03
- 10.43.02 - 10.43.03
- 10.44.03 - 10.44.04
- 7.3.03
- 7.3.06 - 7.3.27
- 8.3.03
Expand Down Expand Up @@ -2373,6 +2391,80 @@ procedure:
- 7.3.06 - 7.3.27
- 8.3.03
- 8.3.06 - 8.3.27
- id: DAT-PAT-17
SUT: |
The health IT developer demonstrates the ability of the Health IT
Module to respond to requests for multiple patients’ data according to
the implementation specification adopted in § 170.215(a)(4) for all of
the FHIR® resources associated with the profiles and Data Elements
specified in and according to the standard adopted in § 170.213 and
implementation specification adopted in § 170.215(a)(2).
* “AllergyIntolerance”;
* “CarePlan”;
* “CareTeam”;
* “Condition”;
* “Coverage”
* “Device”;
* “DiagnosticReport”;
* “DocumentReference”;
* “Encounter”;
* “Goal”;
* “Immunization”;
* “Location” (if supported);
* “Medication” (if supported);
* “MedicationDispense”
* “MedicationRequest”;
* “Observation”;
* “Organization”;
* “Patient”;
* “Practitioner”
* “Procedure”;
* “Provenance”;
* “PractitionerRole” (if supported);
* “QuestionnaireReponse” (if supported);
* “RelatedPerson”;
* “Specimen”; and
* “ServiceRequest”
TLV: |
The health IT developer verifies the ability of the Health IT Module
to respond to requests for multiple patients’ data according to the
implementation specification adopted in § 170.215(a)(4) for all of the
FHIR® resources associated with the profiles and Data Elements
specified in and according to the standard adopted in § 170.213 and
implementation specification adopted in § 170.215(a)(2).
* “AllergyIntolerance”;
* “CarePlan”;
* “CareTeam”;
* “Condition”;
* “Coverage”
* “Device”;
* “DiagnosticReport”;
* “DocumentReference”;
* “Encounter”;
* “Goal”;
* “Immunization”;
* “Location” (if supported);
* “Medication” (if supported);
* “MedicationDispense”
* “MedicationRequest”;
* “Observation”;
* “Organization”;
* “Patient”;
* “Practitioner”
* “Procedure”;
* “Provenance”;
* “PractitionerRole” (if supported);
* “QuestionnaireReponse” (if supported);
* “RelatedPerson”;
* “Specimen”; and
* “ServiceRequest”
inferno_supported: 'yes'
inferno_tests:
- 7.3.03
- 7.3.06 - 7.3.34
- 8.3.03
- 8.3.06 - 8.3.34
- id: DAT-PAT-9
SUT: |
The health IT developer demonstrates the ability of the Health IT
Expand Down

0 comments on commit 47d3bd0

Please sign in to comment.