davinci_pas_test_kit 0.13.2 → 0.13.3
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- checksums.yaml +4 -4
- data/lib/davinci_pas_test_kit/client_suite.rb +13 -0
- data/lib/davinci_pas_test_kit/generated/v2.0.1/claim_inquiry/client_inquire_request_claim_inquiry_must_support_test.rb +0 -1
- data/lib/davinci_pas_test_kit/generated/v2.0.1/server_suite.rb +13 -0
- data/lib/davinci_pas_test_kit/generator/must_support_test_generator.rb +1 -3
- data/lib/davinci_pas_test_kit/generator/templates/suite.rb.erb +13 -0
- data/lib/davinci_pas_test_kit/requirements/{davinci-pas-test-kit_requirements.csv → davinci_pas_test_kit_requirements.csv} +227 -211
- data/lib/davinci_pas_test_kit/requirements/generated/davinci_pas_client_suite_v201_requirements_coverage.csv +123 -0
- data/lib/davinci_pas_test_kit/requirements/generated/davinci_pas_server_suite_v201_requirements_coverage.csv +240 -0
- data/lib/davinci_pas_test_kit/requirements/hl7.fhir.us.davinci-pas_2.0.1_requirements.xlsx +0 -0
- data/lib/davinci_pas_test_kit/version.rb +2 -2
- data/lib/davinci_pas_test_kit.rb +0 -1
- metadata +14 -16
- data/lib/davinci_pas_test_kit/requirements/davinci-pas-test-kit_out_of_scope_requirements.csv +0 -11
- data/lib/davinci_pas_test_kit/requirements/generated/davinci-pas-test-kit_requirements_coverage.csv +0 -214
- data/lib/inferno_requirements_tools/ext/inferno_core/runnable.rb +0 -22
- data/lib/inferno_requirements_tools/tasks/requirements_coverage.rb +0 -284
- data/lib/requirements_config.yaml +0 -17
|
@@ -0,0 +1,240 @@
|
|
|
1
|
+
Req Set,ID,URL,Requirement,Conformance,Actors,Conditionality,Not Tested Reason,Not Tested Details,Da Vinci PAS Server Suite v2.0.1 Short ID(s),Da Vinci PAS Server Suite v2.0.1 Full ID(s)
|
|
2
|
+
hl7.fhir.us.davinci-pas_2.0.1,1,https://hl7.org/fhir/us/davinci-pas/STU2/index.html#cms-exception,"When using PAS under the CMS granted exception (Request Number: HL7 FHIR Exception #2021031001), the implementer(s) **SHALL** disregard any requirements in this Implementation Guide to translate the PAS FHIR Bundle into or out of the X12 278.",SHALL,Server,true,,,"",""
|
|
3
|
+
hl7.fhir.us.davinci-pas_2.0.1,2,https://hl7.org/fhir/us/davinci-pas/STU2/index.html#cms-exception,"When using PAS under the CMS granted exception (Request Number: HL7 FHIR Exception #2021031001), the ... defined PAS FHIR request bundles **SHALL** be transmitted intact between the provider and payer.",SHALL,Server,true,,,"",""
|
|
4
|
+
hl7.fhir.us.davinci-pas_2.0.1,3,https://hl7.org/fhir/us/davinci-pas/STU2/index.html#cms-exception,"When using PAS under the CMS granted exception (Request Number: HL7 FHIR Exception #2021031001), the ... PAS FHIR response bundles **SHALL** be transmitted intact between the payer and the provider.",SHALL,Server,true,,,"",""
|
|
5
|
+
hl7.fhir.us.davinci-pas_2.0.1,5,https://hl7.org/fhir/us/davinci-pas/STU2/usecases.html#prior-authorization-process,The intermediary **SHALL** always exchange a FHIR bundle with the EHR,SHALL,Server,false,,,"2.1.1.02, 2.2.1.02, 2.3.1.02, 2.3.2.05, 3.1.1.02, 3.2.1.02","davinci_pas_server_suite_v201-Group02-pas_server_v201_approval_use_case-Group01-pas_v201_claim_operation_test_approval, davinci_pas_server_suite_v201-Group02-pas_server_v201_denial_use_case-Group01-pas_v201_claim_operation_test_denial, davinci_pas_server_suite_v201-Group02-pas_server_v201_pended_use_case-Group01-pas_v201_claim_operation_test_pended, davinci_pas_server_suite_v201-Group02-pas_server_v201_pended_use_case-Group02-pas_v201_claim_inquiry_operation_test_pended, davinci_pas_server_suite_v201-pas_server_v201_must_support_use_case-Group01-Group01-pas_v201_claim_operation_test_must_support, davinci_pas_server_suite_v201-pas_server_v201_must_support_use_case-Group02-Group01-pas_v201_claim_inquiry_operation_test_must_support"
|
|
6
|
+
hl7.fhir.us.davinci-pas_2.0.1,6,https://hl7.org/fhir/us/davinci-pas/STU2/usecases.html#prior-authorization-process,The intermediary **SHALL** convert the FHIR bundle to and from an X12 278 (and optionally to an X12 275) if necessary to meet the HIPAA transaction requirements,SHALL,Server,false,,,"",""
|
|
7
|
+
hl7.fhir.us.davinci-pas_2.0.1,7,https://hl7.org/fhir/us/davinci-pas/STU2/usecases.html#prior-authorization-process,The intermediary is responsible for obtaining a status of the PA request from the Payer (may use the X12 278 Inquiry) when requested by the EHR,SHALL,Server,false,,,"",""
|
|
8
|
+
hl7.fhir.us.davinci-pas_2.0.1,8,https://hl7.org/fhir/us/davinci-pas/STU2/usecases.html#prior-authorization-process,The intermediary **MAY** convert the X12 278 to and from a FHIR bundle and exchange it with a payer as long as the PA request and response are in an X12 278 format at some time between the exchange with the EHR and the payer,MAY,Server,false,,,"",""
|
|
9
|
+
hl7.fhir.us.davinci-pas_2.0.1,12,https://hl7.org/fhir/us/davinci-pas/STU2/additionalinfo.html,A payer may request additional information from the provider to support a prior authorization request by responding to the X12 278 Request with an X12 278 Response … [with o]ne or more codes in the PWK01 element,MAY,Server,true,Not Tested,Details of X12 messages will not be tested by Inferno.,NA,NA
|
|
10
|
+
hl7.fhir.us.davinci-pas_2.0.1,13,https://hl7.org/fhir/us/davinci-pas/STU2/additionalinfo.html,A payer may request additional information from the provider to support a prior authorization request by responding to the X12 278 Request with an X12 278 Response … [with o]ne or more of the approved LOINC codes Attachments – LOINC in the HI segment,MAY,Server,true,Not Tested,Details of X12 messages will not be tested by Inferno.,NA,NA
|
|
11
|
+
hl7.fhir.us.davinci-pas_2.0.1,14,https://hl7.org/fhir/us/davinci-pas/STU2/additionalinfo.html,A payer may request additional information from the provider to support a prior authorization request by responding to the X12 278 Request with an X12 278 Response ... [with a] single 102089-0 LOINC code in the HI segment to request information via a payer’s specific questionnaire.,MAY,Server,true,Not Tested,Details of X12 messages will not be tested by Inferno.,NA,NA
|
|
12
|
+
hl7.fhir.us.davinci-pas_2.0.1,15,https://hl7.org/fhir/us/davinci-pas/STU2/additionalinfo.html,"When this [102089-0 LOINC code in the HI segment] option is used [to request additional information], the TRN at the X12 278 header or line level associated with the 102089-0 LOINC code SHALL be the DTR context ID used to retrieve the appropriate questionnaire",SHALL,Server,true,Not Tested,Details of X12 messages will not be tested by Inferno.,NA,NA
|
|
13
|
+
hl7.fhir.us.davinci-pas_2.0.1,16,https://hl7.org/fhir/us/davinci-pas/STU2/additionalinfo.html,All of the additional information request codes SHOULD be used as input to a CDex task.,SHOULD,Server,true,,,"",""
|
|
14
|
+
hl7.fhir.us.davinci-pas_2.0.1,17,https://hl7.org/fhir/us/davinci-pas/STU2/additionalinfo.html,The CDex task [created to request additional information] will include all of the information required to enable CDex to assemble the required documentation and send it to the payer’s operation endpoint for attachments.,SHALL,Server,true,,,"",""
|
|
15
|
+
hl7.fhir.us.davinci-pas_2.0.1,18,https://hl7.org/fhir/us/davinci-pas/STU2/additionalinfo.html,"When the LOINC code 102089-0 is present, the associated TRNs SHALL also be exchange as Task.input. The following diagram defines the PAS, CDex, DTR workflow.",SHALL,Server,true,,,"",""
|
|
16
|
+
hl7.fhir.us.davinci-pas_2.0.1,19,https://hl7.org/fhir/us/davinci-pas/STU2/additionalinfo.html,"A separate task SHALL be created for each of the above attachment request types (PWK01, LOINC, questionnaire).",SHALL,Server,true,,,"",""
|
|
17
|
+
hl7.fhir.us.davinci-pas_2.0.1,20,https://hl7.org/fhir/us/davinci-pas/STU2/additionalinfo.html,The [PAS task profile](https://hl7.org/fhir/us/davinci-pas/STU2/StructureDefinition-profile-task.html) SHALL be used to convey PAS X12 278 Response information to CDex.,SHALL,Server,true,,,"",""
|
|
18
|
+
hl7.fhir.us.davinci-pas_2.0.1,25,https://hl7.org/fhir/us/davinci-pas/STU2/additionalinfo.html,"[When creating a Task instance to request additional information, t]he Task.requester.identifier and Task.owner.reference represents the Payer ID",SHALL,Server,true,,,"",""
|
|
19
|
+
hl7.fhir.us.davinci-pas_2.0.1,26,https://hl7.org/fhir/us/davinci-pas/STU2/additionalinfo.html,"[When creating a Task instance to request additional information, t]he Task.for references the Patient information.",SHALL,Server,true,,,"",""
|
|
20
|
+
hl7.fhir.us.davinci-pas_2.0.1,27,https://hl7.org/fhir/us/davinci-pas/STU2/additionalinfo.html,"[When creating a Task instance to request additional information, t]he Task.reasonReference references the [original] Prior Authorization request.",SHALL,Server,true,,,"",""
|
|
21
|
+
hl7.fhir.us.davinci-pas_2.0.1,28,https://hl7.org/fhir/us/davinci-pas/STU2/additionalinfo.html,The Task.input … ‘payerUrl’ slice represents the Payer endpoint URL that is used to submit attachments using the $submit-attachment operation,SHALL,Server,true,,,"",""
|
|
22
|
+
hl7.fhir.us.davinci-pas_2.0.1,29,https://hl7.org/fhir/us/davinci-pas/STU2/additionalinfo.html,The Task.input … ‘attachmentsNeeded’ slice communicates which attachments are needed using LOINC attachment or PWK01 codes,SHALL,Server,true,,,"",""
|
|
23
|
+
hl7.fhir.us.davinci-pas_2.0.1,31,https://hl7.org/fhir/us/davinci-pas/STU2/additionalinfo.html,The Task.input … ‘attachmentsNeeded’ slice contains an extension point to the prior authorization line number.,SHALL,Server,true,,,"",""
|
|
24
|
+
hl7.fhir.us.davinci-pas_2.0.1,32,https://hl7.org/fhir/us/davinci-pas/STU2/additionalinfo.html,The Task.input … ‘questionnairesNeeded’ slice contains an extension point to the prior authorization line number.,SHALL,Server,true,,,"",""
|
|
25
|
+
hl7.fhir.us.davinci-pas_2.0.1,33,https://hl7.org/fhir/us/davinci-pas/STU2/background.html#must-support,The HRex IG defines some [conformance expectations](http://hl7.org/fhir/us/davinci-hrex/conformance.html) that all Da Vinci IGs are expected to follow.,SHALL,Server,false,,,3,davinci_pas_server_suite_v201-pas_server_v201_must_support_use_case
|
|
26
|
+
hl7.fhir.us.davinci-pas_2.0.1,35,https://hl7.org/fhir/us/davinci-pas/STU2/background.html#must-support,PA Intermediary Systems **SHALL** be capable of processing all data elements that are marked as Must Support on the Claim Request,SHALL,Server,false,,,3.1.2,davinci_pas_server_suite_v201-pas_server_v201_must_support_use_case-Group01-Group02
|
|
27
|
+
hl7.fhir.us.davinci-pas_2.0.1,36,https://hl7.org/fhir/us/davinci-pas/STU2/background.html#must-support,PA Intermediary Systems **SHALL** be capable of processing all data elements that are marked as Must Support on the … Claim Inquiry,SHALL,Server,false,,,3.2.2,davinci_pas_server_suite_v201-pas_server_v201_must_support_use_case-Group02-Group02
|
|
28
|
+
hl7.fhir.us.davinci-pas_2.0.1,37,https://hl7.org/fhir/us/davinci-pas/STU2/background.html#must-support,PA Intermediary Systems **SHALL** be capable of returning resource instances containing any of the data elements that are marked as Must Support on the Claim Response,SHALL,Server,false,,,3.1.3.02,davinci_pas_server_suite_v201-pas_server_v201_must_support_use_case-Group01-Group03-pas_server_submit_response_v201_claimresponse_must_support_test
|
|
29
|
+
hl7.fhir.us.davinci-pas_2.0.1,38,https://hl7.org/fhir/us/davinci-pas/STU2/background.html#must-support,PA Intermediary Systems **SHALL** be capable of returning resource instances containing any of the data elements that are marked as Must Support on the Claim ... Inquiry Response.,SHALL,Server,false,,,3.2.3.02,davinci_pas_server_suite_v201-pas_server_v201_must_support_use_case-Group02-Group03-pas_server_inquire_response_v201_claiminquiryresponse_must_support_test
|
|
30
|
+
hl7.fhir.us.davinci-pas_2.0.1,43,https://hl7.org/fhir/us/davinci-pas/STU2/background.html#must-support,"If these [non-must support] data elements are included in a Claim Request or Claim Inquiry, the receiving PA Intermediary System **MAY** ignore those elements.",MAY,Server,true,,,"",""
|
|
31
|
+
hl7.fhir.us.davinci-pas_2.0.1,44,https://hl7.org/fhir/us/davinci-pas/STU2/specification.html#integration-with-other-implementation-guides,[Servers] **SHALL** also support the US Core R4 profiles for Condition,SHALL,Server,false,,,"",""
|
|
32
|
+
hl7.fhir.us.davinci-pas_2.0.1,46,https://hl7.org/fhir/us/davinci-pas/STU2/specification.html#integration-with-other-implementation-guides,[Servers] **SHALL** also support the US Core R4 profiles for … Observation,SHALL,Server,false,,,"",""
|
|
33
|
+
hl7.fhir.us.davinci-pas_2.0.1,48,https://hl7.org/fhir/us/davinci-pas/STU2/specification.html#integration-with-other-implementation-guides,[Servers] **SHALL** also support the US Core R4 profiles for … Procedure,SHALL,Server,false,,,"",""
|
|
34
|
+
hl7.fhir.us.davinci-pas_2.0.1,50,https://hl7.org/fhir/us/davinci-pas/STU2/specification.html#integration-with-other-implementation-guides,[Servers] **SHOULD** support any other [US Core] profiles relevant to the types of prior authorizations they process.,SHOULD,Server,false,,,"",""
|
|
35
|
+
hl7.fhir.us.davinci-pas_2.0.1,53,https://hl7.org/fhir/us/davinci-pas/STU2/specification.html#integration-with-other-implementation-guides,Servers supporting this implementation guide **SHOULD** also comply with the Da Vinci [Coverage Requirements Discovery (CRD)](http://www.hl7.org/fhir/us/davinci-crd) implementation guide,SHOULD,Server,false,,,"",""
|
|
36
|
+
hl7.fhir.us.davinci-pas_2.0.1,55,https://hl7.org/fhir/us/davinci-pas/STU2/specification.html#integration-with-other-implementation-guides,Servers supporting this implementation guide **SHOULD** also comply with the Da Vinci... [Documentation Templates and Rules (DTR)](http://www.hl7.org/fhir/us/davinci-dtr) implementation guide,SHOULD,Server,false,,,"",""
|
|
37
|
+
hl7.fhir.us.davinci-pas_2.0.1,56,https://hl7.org/fhir/us/davinci-pas/STU2/specification.html#integration-with-other-implementation-guides,[Servers] claiming conformance to this IG **SHALL** comply with the [Security and Privacy page in the Da Vinci HRex guide](http://hl7.org/fhir/us/davinci-hrex/security.html).,SHALL,Server,false,,,"",""
|
|
38
|
+
hl7.fhir.us.davinci-pas_2.0.1,63,https://hl7.org/fhir/us/davinci-pas/STU2/specification.html#summary,The [server] system on which the [[Claim submit](https://hl7.org/fhir/us/davinci-pas/STU2/OperationDefinition-Claim-submit.html)] operation is invoked will convert the Bundle into an ASC X12N 278 and 0..* additional unsolicited 275 transactions and execute them all against the target payer system.,SHALL,Server,false,,,"",""
|
|
39
|
+
hl7.fhir.us.davinci-pas_2.0.1,64,https://hl7.org/fhir/us/davinci-pas/STU2/specification.html#summary,[The server] will then take the resulting 278 response [from the X12 transactions created from the prior authorization submission] and convert it into a response FHIR [Bundle](https://hl7.org/fhir/us/davinci-pas/STU2/StructureDefinition-profile-pas-response-bundle.html) containing a [ClaimResponse](https://hl7.org/fhir/us/davinci-pas/STU2/StructureDefinition-profile-claimresponse.html) and associated resources.,SHALL,Server,false,,,"2.1.1.03, 2.2.1.03, 2.3.1.03, 3.1.1.03","davinci_pas_server_suite_v201-Group02-pas_server_v201_approval_use_case-Group01-pas_server_v201_pas_response_bundle_validation_test, davinci_pas_server_suite_v201-Group02-pas_server_v201_denial_use_case-Group01-pas_server_v201_pas_response_bundle_validation_test, davinci_pas_server_suite_v201-Group02-pas_server_v201_pended_use_case-Group01-pas_server_v201_pas_response_bundle_validation_test, davinci_pas_server_suite_v201-pas_server_v201_must_support_use_case-Group01-Group01-pas_server_v201_pas_response_bundle_validation_test"
|
|
40
|
+
hl7.fhir.us.davinci-pas_2.0.1,65,https://hl7.org/fhir/us/davinci-pas/STU2/specification.html#summary,All of this [server processing of prior authorization requests] **SHOULD** happen synchronously with a maximum of 15 seconds between the user initiating the prior authorization request and seeing the resulting response - i.e. including network transmission time for request and response. (Less time is better.),SHOULD,Server,false,,,"",""
|
|
41
|
+
hl7.fhir.us.davinci-pas_2.0.1,66,https://hl7.org/fhir/us/davinci-pas/STU2/specification.html#summary,"In the event that the prior authorization cannot be evaluated and a final response returned within the required timeframe, a response in which one or more of the requested authorization items are ‘pended’ will be returned.",SHALL,Server,true,,,"2.1.1.02, 2.2.1.02, 2.3.1.02, 3.1.1.02","davinci_pas_server_suite_v201-Group02-pas_server_v201_approval_use_case-Group01-pas_v201_claim_operation_test_approval, davinci_pas_server_suite_v201-Group02-pas_server_v201_denial_use_case-Group01-pas_v201_claim_operation_test_denial, davinci_pas_server_suite_v201-Group02-pas_server_v201_pended_use_case-Group01-pas_v201_claim_operation_test_pended, davinci_pas_server_suite_v201-pas_server_v201_must_support_use_case-Group01-Group01-pas_v201_claim_operation_test_must_support"
|
|
42
|
+
hl7.fhir.us.davinci-pas_2.0.1,72,https://hl7.org/fhir/us/davinci-pas/STU2/specification.html#prior-authorization-submission,The payer endpoint is responsible for any internal routing based on which processing organization handles the decisions.,SHALL,Server,false,,,"",""
|
|
43
|
+
hl7.fhir.us.davinci-pas_2.0.1,89,https://hl7.org/fhir/us/davinci-pas/STU2/specification.html#prior-authorization-submission,Systems that do not process such [non-must support] elements [in the [PASBundle](https://hl7.org/fhir/us/davinci-pas/STU2/StructureDefinition-profile-pas-request-bundle.html) for prior authorization submission] **SHALL** ignore unsupported elements unless they are ‘modifier’ elements,SHALL,Server,true,,,"",""
|
|
44
|
+
hl7.fhir.us.davinci-pas_2.0.1,90,https://hl7.org/fhir/us/davinci-pas/STU2/specification.html#prior-authorization-submission,[Server] system[s] MAY treat the presence of … [a] [non-must support] element [in the [PASBundle](https://hl7.org/fhir/us/davinci-pas/STU2/StructureDefinition-profile-pas-request-bundle.html) for prior authorization submission] as an error.,MAY,Server,true,,,"",""
|
|
45
|
+
hl7.fhir.us.davinci-pas_2.0.1,91,https://hl7.org/fhir/us/davinci-pas/STU2/specification.html#prior-authorization-submission,Details on how to map the FHIR Bundle to the relevant X12N 278 and 275 messages are expected to be published by ASC X12N. The mapping [by the payer system] for the 278 Request and Response will be whatever is currently mandated by HIPAA and the mapping for the 278 Inquiry and Response will be the compatible version.,SHALL,Server,false,,,"",""
|
|
46
|
+
hl7.fhir.us.davinci-pas_2.0.1,92,https://hl7.org/fhir/us/davinci-pas/STU2/specification.html#prior-authorization-submission,"[T]he [server] system is responsible for performing full conversion of all mapped elements, including execution of terminology translations when necessary.",SHALL,Server,false,,,"",""
|
|
47
|
+
hl7.fhir.us.davinci-pas_2.0.1,93,https://hl7.org/fhir/us/davinci-pas/STU2/specification.html#prior-authorization-submission,[T]he [server] system SHALL make the entire PAS FHIR Bundle [submitted for prior authorization] available to the intended payer.,SHALL,Server,false,,,"",""
|
|
48
|
+
hl7.fhir.us.davinci-pas_2.0.1,94,https://hl7.org/fhir/us/davinci-pas/STU2/specification.html#prior-authorization-submission,The method [of making the submitted FHIR prior authorization bundle available] may be based on the X12 275 or another method that trading partners have agreed to use.,MAY,Server,false,,,"",""
|
|
49
|
+
hl7.fhir.us.davinci-pas_2.0.1,95,https://hl7.org/fhir/us/davinci-pas/STU2/specification.html#prior-authorization-submission,"If the X12 275 is used for this purpose [of making the FHIR prior authorization bundle avilable], the 275 BDS01 Filter ID Code element SHALL be set to “B64”.",SHALL,Server,true,,,"",""
|
|
50
|
+
hl7.fhir.us.davinci-pas_2.0.1,96,https://hl7.org/fhir/us/davinci-pas/STU2/specification.html#prior-authorization-submission,"Since the 275 binary segment doesn’t contain a field for the binary data MIME type, any system reading that field [to access the FHIR prior authorization bundle avilable] will have to parse out the first few characters to determine whether the FHIR resources are encoded using XML or JSON syntax.",SHALL,Server,true,Not Tested,Details of X12 messages will not be tested by Inferno.,NA,NA
|
|
51
|
+
hl7.fhir.us.davinci-pas_2.0.1,97,https://hl7.org/fhir/us/davinci-pas/STU2/specification.html#prior-authorization-submission,"Translation/mapping systems should be aware that if the size of the attachments as part of a claims submission would exceed the size limitations of a particular recipient, the intermediary should split the attachments into separate 275s to remain within the overall limit.",SHALL,Server,true,,,"",""
|
|
52
|
+
hl7.fhir.us.davinci-pas_2.0.1,98,https://hl7.org/fhir/us/davinci-pas/STU2/specification.html#prior-authorization-submission,It is up to that black box [that processes submitted FHIR prior authorization Bundles] to ensure that any regulatory requirements are met and to perform all processing within the allowed timeframe.,SHALL,Server,false,,,"",""
|
|
53
|
+
hl7.fhir.us.davinci-pas_2.0.1,99,https://hl7.org/fhir/us/davinci-pas/STU2/specification.html#prior-authorization-response,The response to the prior authorization is processed in the reverse order as the request. The [server] system is responsible for converting the ASC X12N 278 response into a FHIR [Bundle](https://hl7.org/fhir/us/davinci-pas/STU2/StructureDefinition-profile-pas-response-bundle.html).,SHALL,Server,false,,,"",""
|
|
54
|
+
hl7.fhir.us.davinci-pas_2.0.1,100,https://hl7.org/fhir/us/davinci-pas/STU2/specification.html#prior-authorization-response,The [[PAS Response](https://hl7.org/fhir/us/davinci-pas/STU2/StructureDefinition-profile-pas-response-bundle.html)] Bundle **SHALL** start with a ClaimResponse entry that contains information mapped from the 278 response.,SHALL,Server,false,,,"2.1.1.03, 2.2.1.03, 2.3.1.03, 3.1.1.03","davinci_pas_server_suite_v201-Group02-pas_server_v201_approval_use_case-Group01-pas_server_v201_pas_response_bundle_validation_test, davinci_pas_server_suite_v201-Group02-pas_server_v201_denial_use_case-Group01-pas_server_v201_pas_response_bundle_validation_test, davinci_pas_server_suite_v201-Group02-pas_server_v201_pended_use_case-Group01-pas_server_v201_pas_response_bundle_validation_test, davinci_pas_server_suite_v201-pas_server_v201_must_support_use_case-Group01-Group01-pas_server_v201_pas_response_bundle_validation_test"
|
|
55
|
+
hl7.fhir.us.davinci-pas_2.0.1,101,https://hl7.org/fhir/us/davinci-pas/STU2/specification.html#prior-authorization-response,[A]dditional [[PAS Response](https://hl7.org/fhir/us/davinci-pas/STU2/StructureDefinition-profile-pas-response-bundle.html)] Bundle entries must be present for all resources referenced by the ClaimResponse or descendent references.,SHALL,Server,false,,,"2.1.1.03, 2.2.1.03, 2.3.1.03, 3.1.1.03","davinci_pas_server_suite_v201-Group02-pas_server_v201_approval_use_case-Group01-pas_server_v201_pas_response_bundle_validation_test, davinci_pas_server_suite_v201-Group02-pas_server_v201_denial_use_case-Group01-pas_server_v201_pas_response_bundle_validation_test, davinci_pas_server_suite_v201-Group02-pas_server_v201_pended_use_case-Group01-pas_server_v201_pas_response_bundle_validation_test, davinci_pas_server_suite_v201-pas_server_v201_must_support_use_case-Group01-Group01-pas_server_v201_pas_response_bundle_validation_test"
|
|
56
|
+
hl7.fhir.us.davinci-pas_2.0.1,102,https://hl7.org/fhir/us/davinci-pas/STU2/specification.html#prior-authorization-response,"When converting additional [[PAS Response](https://hl7.org/fhir/us/davinci-pas/STU2/StructureDefinition-profile-pas-response-bundle.html)] Bundle entries, the conversion process **SHALL** ensure that only one resource is created for a given combination of content. E.g. if the same Practitioner information is referenced in multiple places, only one Practitioner instance should be created - referenced from multiple places as appropriate.",SHALL,Server,true,,,"2.1.1.03, 2.2.1.03, 2.3.1.03, 3.1.1.03","davinci_pas_server_suite_v201-Group02-pas_server_v201_approval_use_case-Group01-pas_server_v201_pas_response_bundle_validation_test, davinci_pas_server_suite_v201-Group02-pas_server_v201_denial_use_case-Group01-pas_server_v201_pas_response_bundle_validation_test, davinci_pas_server_suite_v201-Group02-pas_server_v201_pended_use_case-Group01-pas_server_v201_pas_response_bundle_validation_test, davinci_pas_server_suite_v201-pas_server_v201_must_support_use_case-Group01-Group01-pas_server_v201_pas_response_bundle_validation_test"
|
|
57
|
+
hl7.fhir.us.davinci-pas_2.0.1,103,https://hl7.org/fhir/us/davinci-pas/STU2/specification.html#prior-authorization-response,"When echoing back resources [in the [PAS Response Bundle](https://hl7.org/fhir/us/davinci-pas/STU2/StructureDefinition-profile-pas-response-bundle.html)] that are the same as were present in the prior authorization request, the [payer] system **SHALL** ensure that the same fullUrl and resource identifiers are used in the response as appeared in the request.",SHALL,Server,true,,,"2.1.1.03, 2.2.1.03, 2.3.1.03, 3.1.1.03","davinci_pas_server_suite_v201-Group02-pas_server_v201_approval_use_case-Group01-pas_server_v201_pas_response_bundle_validation_test, davinci_pas_server_suite_v201-Group02-pas_server_v201_denial_use_case-Group01-pas_server_v201_pas_response_bundle_validation_test, davinci_pas_server_suite_v201-Group02-pas_server_v201_pended_use_case-Group01-pas_server_v201_pas_response_bundle_validation_test, davinci_pas_server_suite_v201-pas_server_v201_must_support_use_case-Group01-Group01-pas_server_v201_pas_response_bundle_validation_test"
|
|
58
|
+
hl7.fhir.us.davinci-pas_2.0.1,104,https://hl7.org/fhir/us/davinci-pas/STU2/specification.html#prior-authorization-response,"It is possible that the incoming prior authorization Bundle can not be processed due to validation errors or other non-business-errors. In these instances, the receiving system **SHALL** return OperationOutcome instances that detail why the Bundle could not be processed",SHALL,Server,true,,,4.01,davinci_pas_server_suite_v201-pas_v201_error_group-prior_auth_submission_error
|
|
59
|
+
hl7.fhir.us.davinci-pas_2.0.1,105,https://hl7.org/fhir/us/davinci-pas/STU2/specification.html#prior-authorization-response,"It is possible that the incoming prior authorization Bundle can not be processed due to validation errors or other non-business-errors. In these instances, the receiving system **SHALL** return ... no ClaimResponse",SHALL,Server,true,,,4.01,davinci_pas_server_suite_v201-pas_v201_error_group-prior_auth_submission_error
|
|
60
|
+
hl7.fhir.us.davinci-pas_2.0.1,106,https://hl7.org/fhir/us/davinci-pas/STU2/specification.html#prior-authorization-response,These errors [communicated via OperationOutcome instances] are NOT the errors that are detected by the system processing the request and that can be conveyed in a ClaimResponse via the error capability.,SHALL NOT,Server,true,,,4.01,davinci_pas_server_suite_v201-pas_v201_error_group-prior_auth_submission_error
|
|
61
|
+
hl7.fhir.us.davinci-pas_2.0.1,107,https://hl7.org/fhir/us/davinci-pas/STU2/specification.html#prior-authorization-response,The resulting [[PAS Response](https://hl7.org/fhir/us/davinci-pas/STU2/StructureDefinition-profile-pas-response-bundle.html)] Bundle is returned as the HTTP body of the POST response.,SHALL,Server,false,,,"2.1.1.03, 2.2.1.03, 2.3.1.03, 3.1.1.03","davinci_pas_server_suite_v201-Group02-pas_server_v201_approval_use_case-Group01-pas_server_v201_pas_response_bundle_validation_test, davinci_pas_server_suite_v201-Group02-pas_server_v201_denial_use_case-Group01-pas_server_v201_pas_response_bundle_validation_test, davinci_pas_server_suite_v201-Group02-pas_server_v201_pended_use_case-Group01-pas_server_v201_pas_response_bundle_validation_test, davinci_pas_server_suite_v201-pas_server_v201_must_support_use_case-Group01-Group01-pas_server_v201_pas_response_bundle_validation_test"
|
|
62
|
+
hl7.fhir.us.davinci-pas_2.0.1,108,https://hl7.org/fhir/us/davinci-pas/STU2/specification.html#prior-authorization-transaction-error-handling,Recipients of the transactions should respond as indicated,SHOULD,Server,false,Not Verifiable,The specification does not provide clear details on the indicated responses (unclear diagram),NA,NA
|
|
63
|
+
hl7.fhir.us.davinci-pas_2.0.1,110,https://hl7.org/fhir/us/davinci-pas/STU2/specification.html#prior-authorization-transaction-error-handling,"Business errors that are a part of the processing of the 278 payload, eg. in the AAA segments, are represented in the mapping to the [[PAS Response](https://hl7.org/fhir/us/davinci-pas/STU2/StructureDefinition-profile-pas-response-bundle.html)] response bundle.",SHALL,Server,false,,,3.1.3.02,davinci_pas_server_suite_v201-pas_server_v201_must_support_use_case-Group01-Group03-pas_server_submit_response_v201_claimresponse_must_support_test
|
|
64
|
+
hl7.fhir.us.davinci-pas_2.0.1,111,https://hl7.org/fhir/us/davinci-pas/STU2/specification.html#prior-authorization-transaction-error-handling,All transactions in PAS are synchronous and **SHALL** require one of the following HTTP responses: [including] … 2XX – transaction submission succeeded,SHALL,Server,true,,,"2.1.1.02, 2.2.1.02, 2.3.1.02, 2.3.2.05, 3.1.1.02, 3.2.1.02","davinci_pas_server_suite_v201-Group02-pas_server_v201_approval_use_case-Group01-pas_v201_claim_operation_test_approval, davinci_pas_server_suite_v201-Group02-pas_server_v201_denial_use_case-Group01-pas_v201_claim_operation_test_denial, davinci_pas_server_suite_v201-Group02-pas_server_v201_pended_use_case-Group01-pas_v201_claim_operation_test_pended, davinci_pas_server_suite_v201-Group02-pas_server_v201_pended_use_case-Group02-pas_v201_claim_inquiry_operation_test_pended, davinci_pas_server_suite_v201-pas_server_v201_must_support_use_case-Group01-Group01-pas_v201_claim_operation_test_must_support, davinci_pas_server_suite_v201-pas_server_v201_must_support_use_case-Group02-Group01-pas_v201_claim_inquiry_operation_test_must_support"
|
|
65
|
+
hl7.fhir.us.davinci-pas_2.0.1,112,https://hl7.org/fhir/us/davinci-pas/STU2/specification.html#prior-authorization-transaction-error-handling,All transactions in PAS are synchronous and **SHALL** require one of the following HTTP responses: [including] … 4XX – transaction failed – bad request - failures are not recoverable by resubmission of the transaction.,SHALL,Server,true,,,"4.01, 4.02","davinci_pas_server_suite_v201-pas_v201_error_group-prior_auth_submission_error, davinci_pas_server_suite_v201-pas_v201_error_group-prior_auth_inquiry_error"
|
|
66
|
+
hl7.fhir.us.davinci-pas_2.0.1,113,https://hl7.org/fhir/us/davinci-pas/STU2/specification.html#prior-authorization-transaction-error-handling,[When returning a 4XX HTTP response code t]here will be an OperationOutcome returned that can be reviewed to determine the actual failure,SHALL,Server,true,,,"4.01, 4.02","davinci_pas_server_suite_v201-pas_v201_error_group-prior_auth_submission_error, davinci_pas_server_suite_v201-pas_v201_error_group-prior_auth_inquiry_error"
|
|
67
|
+
hl7.fhir.us.davinci-pas_2.0.1,114,https://hl7.org/fhir/us/davinci-pas/STU2/specification.html#prior-authorization-transaction-error-handling,All transactions in PAS are synchronous and **SHALL** require one of the following HTTP responses: [including] … 5XX – transaction failed – service unavailable or timeout - failures that may be temporary and resubmission may result in successful processing.,SHALL,Server,true,,,"",""
|
|
68
|
+
hl7.fhir.us.davinci-pas_2.0.1,115,https://hl7.org/fhir/us/davinci-pas/STU2/specification.html#prior-authorization-transaction-error-handling,When returning a 5XX HTTP response code] no OperationOutcome will be returned in this instance,SHALL,Server,true,,,"",""
|
|
69
|
+
hl7.fhir.us.davinci-pas_2.0.1,116,https://hl7.org/fhir/us/davinci-pas/STU2/specification.html#http-responses,"If an OperationOutcome [from a server] is received, it may have information regarding errors that should be addressed in the future, but did not cause the transaction to fail.",MAY,Server,true,,,"",""
|
|
70
|
+
hl7.fhir.us.davinci-pas_2.0.1,124,https://hl7.org/fhir/us/davinci-pas/STU2/specification.html#prior-authorization-inquiries,The operation is ... a query-by-example where the incoming Claim resource provides elements that will match existing prior authorizations. Any authorizations that match the incoming resource elements will be returned by the operation. The rules for how the included data elements are matched are specified in the X12 278 inquiry TR3 specification.,SHALL,Server,false,Not Tested,The rules for determining matching claims are specified in a proprietary X12 specification.,NA,NA
|
|
71
|
+
hl7.fhir.us.davinci-pas_2.0.1,129,https://hl7.org/fhir/us/davinci-pas/STU2/specification.html#prior-authorization-inquiries,The information in the [[PAS Inquiry Request](https://hl7.org/fhir/us/davinci-pas/STU2/StructureDefinition-profile-pas-inquiry-request-bundle.html)] Bundle is mapped to a 278 Health Care Services Review Information - Inquiry transaction (278i request).,SHALL,Server,false,,,"",""
|
|
72
|
+
hl7.fhir.us.davinci-pas_2.0.1,130,https://hl7.org/fhir/us/davinci-pas/STU2/specification.html#prior-authorization-inquiries,The 278 Health Care Services Review Information - Response (278i response) is then mapped to a [PAS Inquiry Response Bundle](https://hl7.org/fhir/us/davinci-pas/STU2/StructureDefinition-profile-pas-inquiry-response-bundle.html) with the results of the inquiry contained in the Bundle.,SHALL,Server,false,,,"",""
|
|
73
|
+
hl7.fhir.us.davinci-pas_2.0.1,131,https://hl7.org/fhir/us/davinci-pas/STU2/specification.html#prior-authorization-inquiries,"the returned ClaimResponse [for an inquiry] **SHALL** include the current results for all submitted items, including any items changed or canceled since the original authoriation request.",SHALL,Server,false,,,"2.3.2.06, 3.2.1.03","davinci_pas_server_suite_v201-Group02-pas_server_v201_pended_use_case-Group02-pas_server_v201_pas_inquiry_response_bundle_validation_test, davinci_pas_server_suite_v201-pas_server_v201_must_support_use_case-Group02-Group01-pas_server_v201_pas_inquiry_response_bundle_validation_test"
|
|
74
|
+
hl7.fhir.us.davinci-pas_2.0.1,132,https://hl7.org/fhir/us/davinci-pas/STU2/specification.html#prior-authorization-inquiries,[T]he returned ClaimResponse will be a subset if the request was for a subset of information,SHALL,Server,true,Not Tested,How to request a subset of information is not detailed in the specification and lives in priopietary X12 specifications and mappings.,NA,NA
|
|
75
|
+
hl7.fhir.us.davinci-pas_2.0.1,133,https://hl7.org/fhir/us/davinci-pas/STU2/specification.html#prior-authorization-inquiries,"[I]f the authorizationresponseid submitted is not the ‘current’ authorization response identifier (because subsequent additions/changes/cancellations have been made to the prior authorization request), the returned record **SHALL** be the ‘current’ authorization response - even though it no longer has the same identifier. I.e. If a search is for a ‘replaced’ prior authorization, the search result **SHALL** include the ‘current’ prior authorization response for the most recent replacing prior authorization request.",SHALL,Server,true,,,"",""
|
|
76
|
+
hl7.fhir.us.davinci-pas_2.0.1,134,https://hl7.org/fhir/us/davinci-pas/STU2/specification.html#prior-authorization-inquiries,[Server] systems MAY withhold information about prior authorizations that are ‘open’ but are deemed to be not relevant to the provider (eg. prior authorization requests for sensitive care where the requesting provider is neither the ordering nor rendering provider) who is checking for the prior authorization status if not searching by a specific Claim.identifier.,MAY,Server,true,,,"",""
|
|
77
|
+
hl7.fhir.us.davinci-pas_2.0.1,135,https://hl7.org/fhir/us/davinci-pas/STU2/specification.html#prior-authorization-inquiries,In such situations [when a server restricts access] the response SHOULD include an OperationOutcome warning that some prior authorizations have been suppressed and provide an alternative mechanism (e.g. telephone number) to provide further information if needed.,SHOULD,Server,true,,,"",""
|
|
78
|
+
hl7.fhir.us.davinci-pas_2.0.1,136,https://hl7.org/fhir/us/davinci-pas/STU2/specification.html#pended-authorization-responses,"When the ClaimResponse.reviewaction.code is the X12 code for ‘pended’, it means that the payer requires additional time to make a final determination on all items within the prior authorization request.",SHALL,Server,true,,,"2.1.1.02, 2.2.1.02, 2.3.1.02, 3.1.1.02","davinci_pas_server_suite_v201-Group02-pas_server_v201_approval_use_case-Group01-pas_v201_claim_operation_test_approval, davinci_pas_server_suite_v201-Group02-pas_server_v201_denial_use_case-Group01-pas_v201_claim_operation_test_denial, davinci_pas_server_suite_v201-Group02-pas_server_v201_pended_use_case-Group01-pas_v201_claim_operation_test_pended, davinci_pas_server_suite_v201-pas_server_v201_must_support_use_case-Group01-Group01-pas_v201_claim_operation_test_must_support"
|
|
79
|
+
hl7.fhir.us.davinci-pas_2.0.1,138,https://hl7.org/fhir/us/davinci-pas/STU2/specification.html#pended-authorization-responses,Servers **SHALL** permit access to the prior authorization response to systems other than the original submitter.,SHALL,Server,false,,,"",""
|
|
80
|
+
hl7.fhir.us.davinci-pas_2.0.1,139,https://hl7.org/fhir/us/davinci-pas/STU2/specification.html#pended-authorization-responses,"[Servers] **SHALL** require a match on the patient member or subscriber id (identifier on the Claim.patient) plus the ordering and/or rendering provider identifier, i.e. the provider’s NPI [before responding with prior authorzation details requested by non-submitters].",SHALL,Server,true,,,"",""
|
|
81
|
+
hl7.fhir.us.davinci-pas_2.0.1,141,https://hl7.org/fhir/us/davinci-pas/STU2/specification.html#subscription,[Servers] SHALL support the R4 Subscriptions referenced in the [Subscriptions for R5 Backport Implementation Guide](http://hl7.org/fhir/uv/subscriptions-backport/).,SHALL,Server,false,,,"1, 2.3.2.01","davinci_pas_server_suite_v201-pas_server_v201_subscription_setup, davinci_pas_server_suite_v201-Group02-pas_server_v201_pended_use_case-Group02-prior_auth_claim_response_update_notification_validation"
|
|
82
|
+
hl7.fhir.us.davinci-pas_2.0.1,145,https://hl7.org/fhir/us/davinci-pas/STU2/specification.html#subscription,PAS ... [Server] Intermediaries SHALL support subscriptions with content=’id-only’,SHALL,Server,false,,,2.3.2.02,davinci_pas_server_suite_v201-Group02-pas_server_v201_pended_use_case-Group02-subscriptions_r4_server_notification_conformance
|
|
83
|
+
hl7.fhir.us.davinci-pas_2.0.1,147,https://hl7.org/fhir/us/davinci-pas/STU2/specification.html#subscription,PAS ... [Server] Intermediaries … **MAY** by mutual agreement [with client partners] and with appropriate security arrangements in place for push notifications containing PHI also support content=’full-resource’.,MAY,Server,false,,,"",""
|
|
84
|
+
hl7.fhir.us.davinci-pas_2.0.1,148,https://hl7.org/fhir/us/davinci-pas/STU2/specification.html#subscription,[Server i]ntermediaries **SHALL** ensure that subscriptions to monitor a particular organization’s prior authorizations are only created or modified by that organization.,SHALL,Server,false,,,"",""
|
|
85
|
+
hl7.fhir.us.davinci-pas_2.0.1,149,https://hl7.org/fhir/us/davinci-pas/STU2/specification.html#subscription,Servers supporting subscriptions **SHALL** expose this as part of the Server’s CapabilityStatement,SHALL,Server,false,,,"",""
|
|
86
|
+
hl7.fhir.us.davinci-pas_2.0.1,150,https://hl7.org/fhir/us/davinci-pas/STU2/specification.html#subscription,Servers **SHOULD** support rest-hook … channels,SHOULD,Server,false,,,"",""
|
|
87
|
+
hl7.fhir.us.davinci-pas_2.0.1,151,https://hl7.org/fhir/us/davinci-pas/STU2/specification.html#subscription,Servers … **MAY** support websocket channels,MAY,Server,false,,,"",""
|
|
88
|
+
hl7.fhir.us.davinci-pas_2.0.1,152,https://hl7.org/fhir/us/davinci-pas/STU2/specification.html#subscription,"Once the subscription has been created, the Server **SHALL** send a notification over the requested channel indicating that a prior authorization response submitted by the requesting provider organization has changed. This may happen when the response is complete, but may also occur when information on one or more of the items has been adjusted but the overall response remains as ‘pended’.",SHALL,Server,false,,,"",""
|
|
89
|
+
hl7.fhir.us.davinci-pas_2.0.1,155,https://hl7.org/fhir/us/davinci-pas/STU2/specification.html#checking-status,There are no retry limits for user-initiated status checks.,SHALL,Server,false,,,"",""
|
|
90
|
+
hl7.fhir.us.davinci-pas_2.0.1,176,https://hl7.org/fhir/us/davinci-pas/STU2/specification.html#updating-authorization-requests,The intermediary will create 278 and/or 275 submissions that instantiate the changes (by looking for those items and supportingInfo elements),SHALL,Server,true,,,"",""
|
|
91
|
+
hl7.fhir.us.davinci-pas_2.0.1,177,https://hl7.org/fhir/us/davinci-pas/STU2/specification.html#updating-authorization-requests,The intermediary will create 278 and/or 275 submissions that... will ignore the unchanged items.,SHALL,Server,true,,,"",""
|
|
92
|
+
hl7.fhir.us.davinci-pas_2.0.1,178,https://hl7.org/fhir/us/davinci-pas/STU2/specification.html#responses-to-changed-prior-authorization-requests,"[In response to an update to a previously-submitted prior authorization request,] payers may include responses for all items in the authorization.",MAY,Server,true,,,"",""
|
|
93
|
+
hl7.fhir.us.davinci-pas_2.0.1,179,https://hl7.org/fhir/us/davinci-pas/STU2/specification.html#responses-to-changed-prior-authorization-requests,"In response to an update to a previously-submitted prior authorization request, payers] might only include responses for those items that were specifically changed.",MAY,Server,true,,,"",""
|
|
94
|
+
hl7.fhir.us.davinci-pas_2.0.1,180,https://hl7.org/fhir/us/davinci-pas/STU2/specification.html#responses-to-changed-prior-authorization-requests,"[I]f a ClaimResponse does not contain items corresponding to all that are part of the revised prior authorization (including those canceled or unmodified), it **SHALL** declare a [security tag](http://hl7.org/fhir/R4/resource-definitions.html#Meta.security) with a value of [SUBSETTED](http://hl7.org/fhir/R4/v3/ObservationValue/cs.html#v3-ObservationValue-SUBSETTED) to make clear that the resource is incomplete.",SHALL,Server,true,,,"",""
|
|
95
|
+
hl7.fhir.us.davinci-pas_2.0.1,181,https://hl7.org/fhir/us/davinci-pas/STU2/specification.html#responses-to-changed-prior-authorization-requests,The [server] intermediary would populate the ClaimResponse Bundle based on the approach the payer had chosen in their 278 response.,SHALL,Server,true,,,"",""
|
|
96
|
+
hl7.fhir.us.davinci-pas_2.0.1,182,https://hl7.org/fhir/us/davinci-pas/STU2/specification.html#responses-to-changed-prior-authorization-requests,"When querying for the current status of a prior authorization, the prior authorization response **SHALL** include all items, even if the identifier queried against corresponds to a prior authorization response whose synchronous response was a differential.",SHALL,Server,true,,,"",""
|
|
97
|
+
hl7.fhir.us.davinci-pas_2.0.1,183,https://hl7.org/fhir/us/davinci-pas/STU2/specification.html#responses-to-changed-prior-authorization-requests,PAS systems **SHALL** ensure that prior authorizations that were initially pended remain available for query for at least 6 months after the anticipated completion of the services whose authorization was requested.,SHALL,Server,true,,,"",""
|
|
98
|
+
hl7.fhir.us.davinci-pas_2.0.1,185,https://hl7.org/fhir/us/davinci-pas/STU2/specification.html#responses-to-changed-prior-authorization-requests,"Note that data submitted by client systems will comply with US Core profiles, meaning that codes for medications, conditions, etc. will be those used for clinical purposes, not billing. The intermediary will be responsible for performing any necessary mappings (e.g. SNOMED diagnosis codes to ICD10).",SHALL,Server,false,,,"",""
|
|
99
|
+
hl7.fhir.us.davinci-pas_2.0.1,189,https://hl7.org/fhir/us/davinci-pas/STU2/privacy.html,Payers are responsible for ensuring that only information necessary to make the prior authorization decision is solicited [under HIPAA’s “minimum necessary” regulations],SHALL,Server,false,,,"",""
|
|
100
|
+
hl7.fhir.us.davinci-pas_2.0.1,191,https://hl7.org/fhir/us/davinci-pas/STU2/privacy.html,"Some of the data shared as part of the prior authorization process may have associated constraints on the use of that information for other purposes, including subsequent disclosure to other payers, practitioners, policy-holders, etc. While HL7 FHIR supports conveying this information via security labels on transmitted resources, this information is not currently mappable (and thus findable) in the X12 275 and 278 transactions. Payers who do not view the FHIR version of the transmitted information should be aware of the possibility of these limitations and ensure they have policies that enforce appropriate sharing constraints on data.",SHOULD,Server,true,Not Tested,Details of payer business rules will not be tested by Inferno.,NA,NA
|
|
101
|
+
hl7.fhir.us.davinci-pas_2.0.1,192,https://hl7.org/fhir/us/davinci-pas/STU2/privacy.html,PAS Servers **SHOULD** support server-server Oauth,SHOULD,Server,false,,,"",""
|
|
102
|
+
hl7.fhir.us.davinci-pas_2.0.1,193,https://hl7.org/fhir/us/davinci-pas/STU2/privacy.html,PAS Servers ... **MAY** support mutually authenticated TLS.,MAY,Server,false,,,"",""
|
|
103
|
+
hl7.fhir.us.davinci-pas_2.0.1,194,https://hl7.org/fhir/us/davinci-pas/STU2/privacy.html,Every [server] system implementing the Prior Authorization guide will need to be aware of and follow the guidance in the FHIR Core Specification on [Clinical Safety](http://hl7.org/fhir/safety.html),SHALL,Server,false,,,"",""
|
|
104
|
+
hl7.fhir.us.davinci-pas_2.0.1,196,https://hl7.org/fhir/us/davinci-pas/STU2/privacy.html,Every [server] system implementing the Prior Authorization guide will need to be aware of and follow the guidance in ... the [Security and Privacy page in the Da Vinci HRex guide](http://hl7.org/fhir/us/davinci-hrex/security.html).,SHALL,Server,false,,,"",""
|
|
105
|
+
hl7.fhir.us.davinci-pas_2.0.1,198,https://hl7.org/fhir/us/davinci-pas/STU2/privacy.html,"Once the system authentication has occurred, the payer will perform any authorization required for the provider to see the current state of the prior authorization.",SHALL,Server,false,,,"",""
|
|
106
|
+
hl7.fhir.us.davinci-pas_2.0.1,199,https://hl7.org/fhir/us/davinci-pas/STU2/epaWorkflow.html#pas-epa-coordinator-information,[T]he exchanges between the provider HIT (including any ePA) and the payer HIT (including any ePA) SHALL replicate all of the defined exchanges between provider and intermediary or the intermediary and payer,SHALL,Server,false,,,"",""
|
|
107
|
+
hl7.fhir.us.davinci-pas_2.0.1,201,https://hl7.org/fhir/us/davinci-pas/STU2/metrics.html#metric-data-model,PAS implementers **SHOULD** store [Metric] information for each PAS call in a manner that would allow them to respond to measures based on this logical model.,SHOULD,"Client,Server",false,,,"",""
|
|
108
|
+
hl7.fhir.us.davinci-pas_2.0.1,207,https://hl7.org/fhir/us/davinci-pas/STU2/CapabilityStatement-IntermediaryCapabilities.html,[Servers **SHALL** support the Claim Submit Operation],SHALL,Server,false,,,"2.1.1.02, 2.2.1.02, 2.3.1.02, 3.1.1.02","davinci_pas_server_suite_v201-Group02-pas_server_v201_approval_use_case-Group01-pas_v201_claim_operation_test_approval, davinci_pas_server_suite_v201-Group02-pas_server_v201_denial_use_case-Group01-pas_v201_claim_operation_test_denial, davinci_pas_server_suite_v201-Group02-pas_server_v201_pended_use_case-Group01-pas_v201_claim_operation_test_pended, davinci_pas_server_suite_v201-pas_server_v201_must_support_use_case-Group01-Group01-pas_v201_claim_operation_test_must_support"
|
|
109
|
+
hl7.fhir.us.davinci-pas_2.0.1,208,https://hl7.org/fhir/us/davinci-pas/STU2/CapabilityStatement-IntermediaryCapabilities.html,[Servers **SHALL** support the Claim Inquiry Operation],SHALL,Server,false,,,"2.3.2.05, 3.2.1.02","davinci_pas_server_suite_v201-Group02-pas_server_v201_pended_use_case-Group02-pas_v201_claim_inquiry_operation_test_pended, davinci_pas_server_suite_v201-pas_server_v201_must_support_use_case-Group02-Group01-pas_v201_claim_inquiry_operation_test_must_support"
|
|
110
|
+
hl7.fhir.us.davinci-pas_2.0.1,209,https://hl7.org/fhir/us/davinci-pas/STU2/CapabilityStatement-IntermediaryCapabilities.html,[Servers **SHALL** support the Subscription Create interaction],SHALL,Server,false,,,"",""
|
|
111
|
+
hl7.fhir.us.davinci-pas_2.0.1,210,https://hl7.org/fhir/us/davinci-pas/STU2/CapabilityStatement-IntermediaryCapabilities.html,[Servers **SHALL** support the Subscription Update interaction],SHALL,Server,false,,,"",""
|
|
112
|
+
hl7.fhir.us.davinci-pas_2.0.1,211,https://hl7.org/fhir/us/davinci-pas/STU2/CapabilityStatement-IntermediaryCapabilities.html,[Servers **SHALL** support the Subscription Delete interaction],SHALL,Server,false,,,"",""
|
|
113
|
+
hl7.fhir.us.davinci-pas_2.0.1,212,https://hl7.org/fhir/us/davinci-hrex/STU1/conformance.html,"In the context of an HRex compliant IG, mustSupport on any data element **SHALL** be interpreted [to mean that] … Data Sources **SHALL** be capable of populating the data element when sharing resources compliant with the profile. I.e. the system must be able to demonstrate the population and sharing of the element",SHALL,Server,false,,,"",""
|
|
114
|
+
hl7.fhir.us.davinci-pas_2.0.1,213,https://hl7.org/fhir/us/davinci-hrex/STU1/conformance.html,"In the context of an HRex compliant IG, mustSupport on any data element **SHALL** be interpreted [to mean that] … it is acceptable to omit the [must support] element if the [data source] system doesn't have values in a particular instance.",MAY,Server,true,,,"",""
|
|
115
|
+
hl7.fhir.us.davinci-pas_2.0.1,215,https://hl7.org/fhir/us/davinci-hrex/STU1/conformance.html,"In the context of an HRex compliant IG, mustSupport on any data element **SHALL** be interpreted [to mean that] … [i]f the minimum cardinality of an element is greater than 0 – i.e. the element is ‘required’, then the element **SHALL** be present in the instance",SHALL,Server,true,,,"",""
|
|
116
|
+
hl7.fhir.us.davinci-pas_2.0.1,216,https://hl7.org/fhir/us/davinci-hrex/STU1/conformance.html,"In the context of an HRex compliant IG, mustSupport on any data element **SHALL** be interpreted [to mean that] … [i]f the minimum cardinality of an element is greater than 0 – i.e. the element is ‘required’, then the element ... **SHALL** have a value unless:
|
|
117
|
+
|
|
118
|
+
- The profile explicitly declares the dataAbsentReason extension or other extension for the element, in which case an extension can be present in place of the value. [or]
|
|
119
|
+
- The profile is inherited from U.S. Core, in which case a dataAbsentReason extension may be sent in place of the value even where dataAbsentReason is not explicitly declared in the profile.",SHALL,Server,true,,,"",""
|
|
120
|
+
hl7.fhir.us.davinci-pas_2.0.1,218,https://hl7.org/fhir/us/davinci-hrex/STU1/conformance.html,"In the context of an HRex compliant IG, mustSupport on any data element **SHALL** be interpreted [to mean that] … [w]here the value set for an element includes concepts such as “unknown”, “refused to answer”, “not available” or where dataAbsentReason is explicitly referenced in a profile, then Data Sources **SHALL** use these values/that extension to communicate the reason for missing data.",SHALL,Server,true,,,"",""
|
|
121
|
+
hl7.fhir.us.davinci-pas_2.0.1,220,https://hl7.org/fhir/us/davinci-hrex/STU1/conformance.html,[Data sources] are free to include additional data [beyond the must support elements],MAY,Server,false,,,"",""
|
|
122
|
+
hl7.fhir.us.davinci-pas_2.0.1,222,https://hl7.org/fhir/us/davinci-hrex/STU1/conformance.html,"[Data Sources] should be aware that they can't count on receivers storing, processing or doing anything other than ignoring data that is not marked as mustSupport.",SHOULD,Server,true,Not Verifiable,Can only be tested in the context of a specific trading partner,NA,NA
|
|
123
|
+
hl7.fhir.us.davinci-pas_2.0.1,223,https://hl7.org/fhir/us/davinci-hrex/STU1/conformance.html,"Many of the profiles in this guide reference other FHIR resources that are US Core profiles. This is defined in the formal profile definitions. For example, US Core Patient. For any other references not formally defined in a US Core profiles, the referenced resource **SHOULD** be a US Core profile if a US Core profile exists for the resource type.",SHOULD,Server,true,,,"",""
|
|
124
|
+
hl7.fhir.uv.subscriptions_1.1.0,2,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/components.html#subscription-topics-in-r4,"In order to allow for discovery of supported subscription topics, this guide defines the CapabilityStatement SubscriptionTopic Canonical extension. The extension allows server implementers to advertise the canonical URLs of topics available to clients and allows clients to see the list of supported topics on a server. The extension is expected to appear, if supported, on the Subscription resource entry. Note that servers are NOT required to advertise supported topics via this extension.",MAY,Server,,,,"",""
|
|
125
|
+
hl7.fhir.uv.subscriptions_1.1.0,3,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/components.html#subscription-topics-in-r4,"Supported topics can also be advertised, for example, by the CapabilityStatement.instantiates or CapabilityStatement.implementationGuide elements of a CapabilityStatement, as defined by another Implementation Guide.",MAY,Server,,Not Verifiable,Not precise enough to be consistently verified,NA,NA
|
|
126
|
+
hl7.fhir.uv.subscriptions_1.1.0,4,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/components.html#subscription-topics-in-r4,"FHIR R4 servers MAY choose to leave topic discovery completely out-of-band and part of other steps, such as registration or integration.",MAY,Server,,Not Tested,"MAY requirement, support for which doesn't imply other requirements. Additionally, meeting this requirement is simply the absence of other features.",NA,NA
|
|
127
|
+
hl7.fhir.uv.subscriptions_1.1.0,7,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/components.html#accepting-subscription-requests,"When a FHIR Server accepts a request to create a Subscription, the server is indicating to the client that the server:
|
|
128
|
+
- is capable of detecting when events covered by the requested SubscriptionTopic occur, and
|
|
129
|
+
- is willing to make a simple best effort attempt at delivering a notification for each occurrence of a matching event.",SHALL,Server,,,,1.04,davinci_pas_server_suite_v201-pas_server_v201_subscription_setup-subscriptions_r4_server_creation_response_conformance
|
|
130
|
+
hl7.fhir.uv.subscriptions_1.1.0,8,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/components.html#accepting-subscription-requests,When processing a request for a Subscription...a server SHOULD validate…that the SubscriptionTopic is valid and implemented by the server,SHOULD,Server,,,,"",""
|
|
131
|
+
hl7.fhir.uv.subscriptions_1.1.0,9,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/components.html#accepting-subscription-requests,When processing a request for a Subscription...a server SHOULD validate…that all requested filters are defined in the requested topic and are implemented in the server,SHOULD,Server,,,,"",""
|
|
132
|
+
hl7.fhir.uv.subscriptions_1.1.0,10,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/components.html#accepting-subscription-requests,When processing a request for a Subscription...a server SHOULD validate…that the channel type is known and implemented by the server,SHOULD,Server,,,,"",""
|
|
133
|
+
hl7.fhir.uv.subscriptions_1.1.0,11,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/components.html#accepting-subscription-requests,"When processing a request for a Subscription...a server SHOULD validate…that the channel endpoint is valid for the channel provided (e.g., is it a valid URL of the expected type)",SHOULD,Server,,,,"",""
|
|
134
|
+
hl7.fhir.uv.subscriptions_1.1.0,12,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/components.html#accepting-subscription-requests,When processing a request for a Subscription...a server SHOULD validate…that the payload configuration is known and implemented by the server,SHOULD,Server,,,,"",""
|
|
135
|
+
hl7.fhir.uv.subscriptions_1.1.0,13,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/components.html#accepting-subscription-requests,"When processing a request for a Subscription...a server SHOULD validate…that the payload configuration is valid for the channel type requested (e.g., complies with the server’s security policy)",SHOULD,Server,,,,"",""
|
|
136
|
+
hl7.fhir.uv.subscriptions_1.1.0,14,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/components.html#subscription-notifications,"In ... FHIR R4 ... notifications are based on a history Bundle. The first entry always contains SubscriptionStatus information, encoded as ... a Parameters resource using the Backport SubscriptionStatus Profile in FHIR R4",SHALL,Server,,,,"1.05, 2.3.2.03","davinci_pas_server_suite_v201-pas_server_v201_subscription_setup-subscriptions_r4_server_handshake_conformance, davinci_pas_server_suite_v201-Group02-pas_server_v201_pended_use_case-Group02-subscriptions_r4_server_id_only_conformance"
|
|
137
|
+
hl7.fhir.uv.subscriptions_1.1.0,15,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/components.html#subscription-notifications,"Note that since notifications use history type Bundles, all notifications need to comply with the requirements for that bundle type. Specifically, there are two invariants on Bundle (bdl-3 and bdl-4) that require a Bundle.entry.request element for every Bundle.entry.
|
|
138
|
+
- For the status resource (entry[0]) the request SHALL be filled out to match a request to the $status operation.
|
|
139
|
+
- for additional entries the request SHOULD be filled out in a way that makes sense given the subscription (e.g., a POST or PUT operation on the resource, etc.). However, a server MAY choose to simply include a GET to the relevant resource instead.",SHALL,Server,,,,"1.05, 2.3.2.03","davinci_pas_server_suite_v201-pas_server_v201_subscription_setup-subscriptions_r4_server_handshake_conformance, davinci_pas_server_suite_v201-Group02-pas_server_v201_pended_use_case-Group02-subscriptions_r4_server_id_only_conformance"
|
|
140
|
+
hl7.fhir.uv.subscriptions_1.1.0,16,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/components.html#scoping-responsibilities,"Unless otherwise specified by a server implementation and channel, the Subscriptions Framework does not involve guaranteed delivery of notifications. While the Subscriptions Framework is able to support such mechanisms, defining them are beyond the scope of the standard or this guide. - Servers SHOULD detect errors and take appropriate action where possible. In general, this boundary is when the notification is delivered.",SHOULD,Server,,,,"",""
|
|
141
|
+
hl7.fhir.uv.subscriptions_1.1.0,18,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/workflow.html#workflow-fhir-r4,"[When a client requests a Subscription, the] Server MAY accept the Subscription request and mark it active (e.g., supported channel and payload, no handshake required).",MAY,Server,,Not Tested,"MAY requirement, support for which doesn't imply other requirements.",NA,NA
|
|
142
|
+
hl7.fhir.uv.subscriptions_1.1.0,19,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/workflow.html#workflow-fhir-r4,"[When a client requests a Subscription, the] Server MAY accept the Subscription request and mark it requested (e.g., supported channel and payload, handshake required).",MAY,Server,,Not Tested,"MAY requirement, support for which doesn't imply other requirements.",NA,NA
|
|
143
|
+
hl7.fhir.uv.subscriptions_1.1.0,20,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/workflow.html#workflow-fhir-r4,"[When a server sends a handshake bundle to a Subscription endpoint] If the Endpoint responds appropriately, per the channel requirements (e.g., in REST an HTTP Success code such as 200), the Server updates the subscription to active.",SHALL,Server,,,,"",""
|
|
144
|
+
hl7.fhir.uv.subscriptions_1.1.0,21,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/workflow.html#workflow-fhir-r4,"[When a server sends a handshake bundle to a Subscription endpoint] If the handshake fails (e.g., connection failure, bad response, etc.), the Server updates the subscription to error.",SHALL,Server,,,,"",""
|
|
145
|
+
hl7.fhir.uv.subscriptions_1.1.0,22,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/workflow.html#workflow-fhir-r4,"[When a client requests a Subscription, the] Server MAY reject the Subscription request (e.g., unsupported channel type).",MAY,Server,,Not Tested,"MAY requirement, support for which doesn't imply other requirements.",NA,NA
|
|
146
|
+
hl7.fhir.uv.subscriptions_1.1.0,25,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/channels.html#rest-hook-1,"To convey an event notification, the server POSTs a Bundle to the client’s nominated endpoint URL",SHALL,Server,,,,"1.04, 1.05","davinci_pas_server_suite_v201-pas_server_v201_subscription_setup-subscriptions_r4_server_creation_response_conformance, davinci_pas_server_suite_v201-pas_server_v201_subscription_setup-subscriptions_r4_server_handshake_conformance"
|
|
147
|
+
hl7.fhir.uv.subscriptions_1.1.0,26,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/channels.html#rest-hook-1,The content-type of the [server's event notification] POST SHALL match the MIME type on the Subscription ([Subscription.channel.payload](http://hl7.org/fhir/subscription-definitions.html#Subscription.channel.payload)).,SHALL,Server,,,,"",""
|
|
148
|
+
hl7.fhir.uv.subscriptions_1.1.0,27,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/channels.html#rest-hook-1,Each [Subscription.channel.header](http://hl7.org/fhir/subscription-definitions.html#Subscription.channel.header) value SHALL be conveyed as an HTTP request header [in the server's event notification POST].,SHALL,Server,,,,"",""
|
|
149
|
+
hl7.fhir.uv.subscriptions_1.1.0,28,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/channels.html#rest-hook-1,The [server's event notification] bundle SHALL comply with the [Backported R5 Notification Bundle Profile](https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/StructureDefinition-backport-subscription-notification.html).,SHALL,Server,,,,"1.05, 2.3.2.03","davinci_pas_server_suite_v201-pas_server_v201_subscription_setup-subscriptions_r4_server_handshake_conformance, davinci_pas_server_suite_v201-Group02-pas_server_v201_pended_use_case-Group02-subscriptions_r4_server_id_only_conformance"
|
|
150
|
+
hl7.fhir.uv.subscriptions_1.1.0,29,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/channels.html#rest-hook-1,"When a Subscription is created for a REST Hook channel type, the server SHALL set initial status to requested, pending verification of the nominated endpoint URL.",SHALL,Server,,,,1.04,davinci_pas_server_suite_v201-pas_server_v201_subscription_setup-subscriptions_r4_server_creation_response_conformance
|
|
151
|
+
hl7.fhir.uv.subscriptions_1.1.0,30,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/channels.html#rest-hook-1,"After a successful handshake notification has been sent and accepted [for a REST Hook channel type], the server SHALL update the status to active.",SHALL,Server,,,,"",""
|
|
152
|
+
hl7.fhir.uv.subscriptions_1.1.0,31,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/channels.html#rest-hook-1,Any errors in the initial handshake [for a REST Hook channel type] SHALL result in the status being changed to error.,SHALL,Server,,,,"",""
|
|
153
|
+
hl7.fhir.uv.subscriptions_1.1.0,32,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/channels.html#security-notes,"HTTP is neither a secure nor an encrypted channel, nor does it provide endpoint verification. It is strongly recommended that implementations refuse requests to send notifications to URLs using the HTTP protocol (use HTTPS instead).",SHOULD,Server,,,,"",""
|
|
154
|
+
hl7.fhir.uv.subscriptions_1.1.0,33,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/notifications.html#event-notifications-and-what-to-include,"In addition to the Subscription Status information, each notification MAY include additional resources or references to resources (URLs or ids).",MAY,Server,,Not Tested,"MAY requirement, support for which doesn't imply other requirements.",NA,NA
|
|
155
|
+
hl7.fhir.uv.subscriptions_1.1.0,34,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/notifications.html#additional-resources,Servers MAY choose to include additional resources [other than the focus] with notifications that may be of interest to clients.,MAY,Server,,Not Tested,"MAY requirement, support for which doesn't imply other requirements.",NA,NA
|
|
156
|
+
hl7.fhir.uv.subscriptions_1.1.0,35,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/notifications.html#additional-resources,"Servers SHALL conform to the payload configuration of the subscription when adding additional resources (e.g., if the subscription is id-only, then only ids of additional resources may be provided; if the subscription is full-resource, then full resources should be provided).",SHALL,Server,,,,2.3.2.03,davinci_pas_server_suite_v201-Group02-pas_server_v201_pended_use_case-Group02-subscriptions_r4_server_id_only_conformance
|
|
157
|
+
hl7.fhir.uv.subscriptions_1.1.0,36,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/payloads.html#payload-types,"If a server will not honor a payload type (e.g., will not send full-resource over HTTP), it SHOULD reject the Subscription request",SHOULD,Server,,,,"",""
|
|
158
|
+
hl7.fhir.uv.subscriptions_1.1.0,37,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/payloads.html#payload-types,"If a server will not honor a payload type (e.g., will not send full-resource over HTTP), it ... MAY accept the subscription with modifications.",MAY,Server,,Not Tested,"MAY requirement, support for which doesn't imply other requirements.",NA,NA
|
|
159
|
+
hl7.fhir.uv.subscriptions_1.1.0,38,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/payloads.html#empty,"When populating the SubscriptionStatus.notificationEvent structure for a notification with an empty payload, a server SHALL NOT include references to resources (e.g., SubscriptionStatus.notificationEvent.focus and SubscriptionStatus.notificationEvent.additionalContext SHALL NOT be present).",SHALL NOT,Server,,,,"",""
|
|
160
|
+
hl7.fhir.uv.subscriptions_1.1.0,39,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/payloads.html#empty,"When the content type is empty, notification bundles SHALL not contain Bundle.entry elements other than the SubscriptionStatus for the notification.",SHALL NOT,Server,,,,"",""
|
|
161
|
+
hl7.fhir.uv.subscriptions_1.1.0,40,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/payloads.html#id-only,"When the content type is id-only, notification bundles SHALL include references to the appropriate focus resources in the SubscriptionStatus.notificationEvent.focus element.",SHALL,Server,,,,2.3.2.03,davinci_pas_server_suite_v201-Group02-pas_server_v201_pended_use_case-Group02-subscriptions_r4_server_id_only_conformance
|
|
162
|
+
hl7.fhir.uv.subscriptions_1.1.0,41,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/payloads.html#id-only,"Additionally, [id-only] notification bundles MAY contain, in addition to the SubscriptionStatus used to convey status information, at least one Bundle.entry for each resource relevant to the notification. For example, a notification for a topic based on Encounter MAY include a reference to the Encounter and MAY also include additional resources deemed relevant (e.g., the linked Patient).",MAY,Server,,Not Tested,"MAY requirement, support for which doesn't imply other requirements.",NA,NA
|
|
163
|
+
hl7.fhir.uv.subscriptions_1.1.0,42,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/payloads.html#id-only,"Each Bundle.entry for id-only notification SHALL contain a relevant resource URL in the fullUrl and request elements, as is required for history bundles.",SHALL,Server,,,,2.3.2.03,davinci_pas_server_suite_v201-Group02-pas_server_v201_pended_use_case-Group02-subscriptions_r4_server_id_only_conformance
|
|
164
|
+
hl7.fhir.uv.subscriptions_1.1.0,43,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/payloads.html#full-resource,"When the content type is full-resource, notification bundles SHALL include references to the appropriate focus resources in the SubscriptionStatus.notificationEvent.focus element.",SHALL,Server,,,,"",""
|
|
165
|
+
hl7.fhir.uv.subscriptions_1.1.0,44,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/payloads.html#full-resource,"Notification bundles for full-resource subscriptions SHALL contain, in addition to the SubscriptionStatus, at least one Bundle.entry for each resource relevant to the notification. For example, a notification for a topic based on the Encounter resource SHALL include an Encounter and MAY include additional resources deemed relevant (e.g., the referenced Patient).",SHALL,Server,,,,"",""
|
|
166
|
+
hl7.fhir.uv.subscriptions_1.1.0,45,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/payloads.html#full-resource,"Each Bundle.entry for a full-resource notification SHALL contain a relevant resource in the entry.resource element. If a server cannot include the resource contents due to an issue with a specific notification, the server SHALL populate the entry.request and/or entry.response elements.",SHALL,Server,,,,"",""
|
|
167
|
+
hl7.fhir.uv.subscriptions_1.1.0,47,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/conformance.html#conformance-in-fhir-r4,"In order to claim conformance with this guide, a server…SHALL support the $status operation on the Subscription resource.",SHALL,Server,,,,"",""
|
|
168
|
+
hl7.fhir.uv.subscriptions_1.1.0,48,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/conformance.html#conformance-in-fhir-r4,"In order to claim conformance with this guide, a server…SHOULD support topic discovery via the CapabilityStatement SubscriptionTopic Canonical extension",SHOULD,Server,,,,"",""
|
|
169
|
+
hl7.fhir.uv.subscriptions_1.1.0,49,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/conformance.html#conformance-in-fhir-r4,"In order to claim conformance with this guide, a server…SHALL support at least one channel type",SHALL,Server,,,,1.04,davinci_pas_server_suite_v201-pas_server_v201_subscription_setup-subscriptions_r4_server_creation_response_conformance
|
|
170
|
+
hl7.fhir.uv.subscriptions_1.1.0,50,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/conformance.html#conformance-in-fhir-r4,"In order to claim conformance with this guide, a server…SHOULD include one [channel type] from this guide",SHOULD,Server,,,,"",""
|
|
171
|
+
hl7.fhir.uv.subscriptions_1.1.0,51,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/conformance.html#conformance-in-fhir-r4,"In order to claim conformance with this guide, a server…SHALL support at least one Payload Type",SHALL,Server,,,,2.3.2.03,davinci_pas_server_suite_v201-Group02-pas_server_v201_pended_use_case-Group02-subscriptions_r4_server_id_only_conformance
|
|
172
|
+
hl7.fhir.uv.subscriptions_1.1.0,52,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/conformance.html#conformance-artifacts-1,"FHIR Servers claiming conformance to this Implementation Guide must conform to the expectations described in the Capability Statement appropriate to the implemented FHIR version. For FHIR R4 servers, this guide defines the R4 Server CapabilityStatement (https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/CapabilityStatement-backport-subscription-server-r4.html).",SHALL,Server,,,,"",""
|
|
173
|
+
hl7.fhir.uv.subscriptions_1.1.0,53,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/conformance.html#conformance-artifacts-1,"In addition to the basic support in the CapabilityStatement (e.g., resources, interactions, and operations), a conformant server SHALL support at least one Payload Type … listed in this IG.",SHALL,Server,,,,2.3.2.03,davinci_pas_server_suite_v201-Group02-pas_server_v201_pended_use_case-Group02-subscriptions_r4_server_id_only_conformance
|
|
174
|
+
hl7.fhir.uv.subscriptions_1.1.0,54,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/conformance.html#conformance-artifacts-1,"In addition to the basic support in the CapabilityStatement (e.g., resources, interactions, and operations), a conformant server ... SHOULD support one Channel Type listed in this IG.",SHOULD,Server,,,,"",""
|
|
175
|
+
hl7.fhir.uv.subscriptions_1.1.0,57,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/conformance.html#profile-support-1,a conformant server…SHOULD declare conformance with the Backport Subscription Server Capability Statement by including its official URL in the server’s CapabilityStatement.instantiates element: http://hl7.org/fhir/uv/subscriptions-backport/CapabilityStatement/backport-subscription-server-r4.,SHOULD,Server,,,,"",""
|
|
176
|
+
hl7.fhir.uv.subscriptions_1.1.0,58,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/conformance.html#profile-support-1,"a conformant server…SHALL specify the full capability details from the CapabilityStatement it claims to implement, including declaring support for the Backport Subscription Profile by including its official URL in the server’s CapabilityStatement.rest.resource.supportedProfile element: http://hl7.org/fhir/uv/subscriptions-backport/StructureDefinition/backport-subscription",SHALL,Server,,Not Tested,Conflicts with requirement 120 and is removed in future versions of the spec.,NA,NA
|
|
177
|
+
hl7.fhir.uv.subscriptions_1.1.0,59,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/conformance.html#backport-channel-type-1,Servers supporting this guide SHALL be able to read values present in this [backport-channel-type extension - https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/StructureDefinition-backport-channel-type.html] element.,SHALL,Server,,,,"",""
|
|
178
|
+
hl7.fhir.uv.subscriptions_1.1.0,60,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/conformance.html#backport-channel-type-1,A server SHALL reject the subscription request if a client requests an unsupported channel via this [backport-channel-type extension - https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/StructureDefinition-backport-channel-type.html] element.,SHALL,Server,,,,"",""
|
|
179
|
+
hl7.fhir.uv.subscriptions_1.1.0,63,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/conformance.html#backport-filter-criteria-1,"If a server is capable of supporting filter criteria in general but unable to support criteria requested in a subscription [via the extension backport-filter-criteria - https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/StructureDefinition-backport-filter-criteria.html], the server SHALL reject the subscription.",SHALL,Server,,,,"",""
|
|
180
|
+
hl7.fhir.uv.subscriptions_1.1.0,65,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/conformance.html#backport-payload-content-1,Servers supporting this guide SHALL be able to read values from this [backport-payload-content - https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/StructureDefinition-backport-payload-content.html] extension.,SHALL,Server,,,,2.3.2.03,davinci_pas_server_suite_v201-Group02-pas_server_v201_pended_use_case-Group02-subscriptions_r4_server_id_only_conformance
|
|
181
|
+
hl7.fhir.uv.subscriptions_1.1.0,66,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/conformance.html#backport-payload-content-1,"A server SHALL reject the subscription request if a client asks for a content level the server does not intend to support (e.g., does not meet security requirements) [using the extension backport-payload-content - https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/StructureDefinition-backport-payload-content.html].",SHALL,Server,,,,"",""
|
|
182
|
+
hl7.fhir.uv.subscriptions_1.1.0,67,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/conformance.html#backport-payload-content-1,Servers SHALL include information in notifications as described in this guide based on this value [in the extension backport-payload-content - https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/StructureDefinition-backport-payload-content.html].,SHALL,Server,,,,2.3.2.03,davinci_pas_server_suite_v201-Group02-pas_server_v201_pended_use_case-Group02-subscriptions_r4_server_id_only_conformance
|
|
183
|
+
hl7.fhir.uv.subscriptions_1.1.0,69,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/conformance.html#notification-entry-subscriptionstatus-1,Servers supporting this guide SHALL be able to generate a valid and correct R4 Backported R5 SubscriptionStatus resource for each notification.,SHALL,Server,,,,"1.05, 2.3.2.03","davinci_pas_server_suite_v201-pas_server_v201_subscription_setup-subscriptions_r4_server_handshake_conformance, davinci_pas_server_suite_v201-Group02-pas_server_v201_pended_use_case-Group02-subscriptions_r4_server_id_only_conformance"
|
|
184
|
+
hl7.fhir.uv.subscriptions_1.1.0,70,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/conformance.html#notification-entry-subscriptionstatus-1,The status entry SHALL be the first entry of each notification bundle.,SHALL,Server,,,,"1.05, 2.3.2.03","davinci_pas_server_suite_v201-pas_server_v201_subscription_setup-subscriptions_r4_server_handshake_conformance, davinci_pas_server_suite_v201-Group02-pas_server_v201_pended_use_case-Group02-subscriptions_r4_server_id_only_conformance"
|
|
185
|
+
hl7.fhir.uv.subscriptions_1.1.0,72,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/conformance.html#subscriptioncriteria-1,"The Subscription.criteria element is required (cardinality of 1..1), so any compatible implementation SHALL be able to read and/or write as necessary.",SHALL,Server,,,,1.01,davinci_pas_server_suite_v201-pas_server_v201_subscription_setup-subscriptions_r4_server_subscription_conformance
|
|
186
|
+
hl7.fhir.uv.subscriptions_1.1.0,73,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/conformance.html#subscriptioncriteria-1,"Compared with the core specification, this guide specifies that the [Subscription.criteria] element SHALL contain the canonical URL for the Subscription Topic.",SHALL,Server,,,,1.01,davinci_pas_server_suite_v201-pas_server_v201_subscription_setup-subscriptions_r4_server_subscription_conformance
|
|
187
|
+
hl7.fhir.uv.subscriptions_1.1.0,74,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/conformance.html#subscriptioncriteria-1,Servers supporting this guide SHALL be able to read values in this [Subscription.criteria] element and process requests for subscription topics referenced by it.,SHALL,Server,,,,"",""
|
|
188
|
+
hl7.fhir.uv.subscriptions_1.1.0,75,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/conformance.html#subscriptioncriteria-1,"If a server does not support a requested topic [in the Subscription.criteria element] or will not honor the subscription otherwise, a server SHALL reject the subscription request.",SHALL,Server,,,,"",""
|
|
189
|
+
hl7.fhir.uv.subscriptions_1.1.0,77,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/errors.html#handling-errors-as-a-server,A server SHALL…Increment the eventsSinceSubscriptionStart counter internally.,SHALL,Server,,,,"",""
|
|
190
|
+
hl7.fhir.uv.subscriptions_1.1.0,78,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/errors.html#handling-errors-as-a-server,A server SHALL…Update the status of the subscription internally.,SHALL,Server,,,,"",""
|
|
191
|
+
hl7.fhir.uv.subscriptions_1.1.0,79,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/errors.html#handling-errors-as-a-server,A server SHALL…Continue to respond to $status requests.,SHALL,Server,,,,"",""
|
|
192
|
+
hl7.fhir.uv.subscriptions_1.1.0,80,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/errors.html#handling-errors-as-a-server,A server MAY Continue to send heartbeat messages (with an error status set).,MAY,Server,,Not Tested,"MAY requirement, support for which doesn't imply other requirements.",NA,NA
|
|
193
|
+
hl7.fhir.uv.subscriptions_1.1.0,83,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/errors.html#using-the-events-operation,"Servers MAY choose to support the $events operation, as defined in this IG.",MAY,Server,,,,"",""
|
|
194
|
+
hl7.fhir.uv.subscriptions_1.1.0,84,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/errors.html#using-the-events-operation,"Servers which implement the operation MAY use implementation-specific criteria to restrict availability of events (e.g., most recent 10 events, events within the past 30 days, etc.).",MAY,Server,,Not Tested,"MAY requirement, support for which doesn't imply other requirements.",NA,NA
|
|
195
|
+
hl7.fhir.uv.subscriptions_1.1.0,90,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/components.html#subscriptions-and-fhir-versions,"Servers SHALL look for this [Subscription.channel.payload element] parameter during subscription negotiation and SHALL not accept requests for notification FHIR versions it cannot support (servers MAY reject or coerce, according to their policies)",SHALL,Server,,,,"",""
|
|
196
|
+
hl7.fhir.uv.subscriptions_1.1.0,92,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/channels.html#rest-hook-1,Server may send notifications of type heartbeat at any time.,MAY,Server,,Not Tested,"MAY requirement, support for which doesn't imply other requirements.",NA,NA
|
|
197
|
+
hl7.fhir.uv.subscriptions_1.1.0,93,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/StructureDefinition-backport-subscription-definitions.html#root,"Subscription.channel.extension:heartbeatPeriod: If present, a 'hearbeat' notification (keepalive) is sent via this channel with an the interval period equal to this elements integer value in seconds.",SHALL,Server,,,,"",""
|
|
198
|
+
hl7.fhir.uv.subscriptions_1.1.0,94,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/StructureDefinition-backport-subscription-definitions.html#root,"Subscription.channel.extension:heartbeatPeriod: If not present, a heartbeat notification is not sent.",SHALL,Server,,,,"",""
|
|
199
|
+
hl7.fhir.uv.subscriptions_1.1.0,95,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/StructureDefinition-backport-subscription-definitions.html#root,"Subscription.criteria.extension:filterCriteria: When multiple filters are applied, evaluates to true if all the conditions are met; otherwise it returns false. (i.e., logical AND).",SHALL,Server,,,,"",""
|
|
200
|
+
hl7.fhir.uv.subscriptions_1.1.0,97,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/StructureDefinition-backport-subscription-definitions.html#root,"Subscription.channel.extension:timeout: If present, the maximum amount of time a server will allow before failing a notification attempt.",SHALL,Server,,,,"",""
|
|
201
|
+
hl7.fhir.uv.subscriptions_1.1.0,98,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/StructureDefinition-backport-subscription-definitions.html#root,"Subscription.channel.extension:maxCount: If present, the maximum number of triggering resources that will be included in a notification bundle (e.g., a server will not include more than this number of trigger resources in a single notification). Note that this is not a strict limit on the number of entries in a bundle, as dependent resources can be included.",SHALL,Server,,,,"",""
|
|
202
|
+
hl7.fhir.uv.subscriptions_1.1.0,99,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/StructureDefinition-backport-subscription-status-r4-definitions.html,Parameters.parameter:topic.value[x]: This value SHOULD NOT be present when using empty payloads,SHOULD NOT,Server,,,,"",""
|
|
203
|
+
hl7.fhir.uv.subscriptions_1.1.0,100,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/StructureDefinition-backport-subscription-status-r4-definitions.html,Parameters.parameter:topic.value[x]: This value … MAY be present when using id-only payloads,MAY,Server,,Not Tested,"MAY requirement, support for which doesn't imply other requirements.",NA,NA
|
|
204
|
+
hl7.fhir.uv.subscriptions_1.1.0,101,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/StructureDefinition-backport-subscription-status-r4-definitions.html,Parameters.parameter:topic.value[x]: This value … SHOULD be present when using full-resource payloads.,SHOULD,Server,,,,"",""
|
|
205
|
+
hl7.fhir.uv.subscriptions_1.1.0,102,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/StructureDefinition-backport-subscription-status-r4-definitions.html,Parameters.parameter:eventsSinceSubscriptionStart.value[x]: The total number of actual events which have been generated since the Subscription was created (inclusive of this notification) - regardless of how many have been successfully communicated. This number is NOT incremented for handshake and heartbeat notifications.,SHALL,Server,,,,"",""
|
|
206
|
+
hl7.fhir.uv.subscriptions_1.1.0,103,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/StructureDefinition-backport-subscription-status-r4-definitions.html,Parameters.parameter:notificationEvent.part:eventNumber.value[x]: The sequential number of this event in this subscription context.,SHALL,Server,,,,"",""
|
|
207
|
+
hl7.fhir.uv.subscriptions_1.1.0,104,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/StructureDefinition-backport-subscription-status-r4-definitions.html,Parameters.parameter:notificationEvent.part:eventFocus.value[x]: MAY contain a reference to a non-FHIR object.,MAY,Server,,Not Tested,"MAY requirement, support for which doesn't imply other requirements.",NA,NA
|
|
208
|
+
hl7.fhir.uv.subscriptions_1.1.0,105,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/StructureDefinition-backport-subscription-status-r4-definitions.html,Parameters.parameter:notificationEvent.part:eventAdditionalContext.value[x]: MAY refer to non-FHIR objects.,MAY,Server,,Not Tested,"MAY requirement, support for which doesn't imply other requirements.",NA,NA
|
|
209
|
+
hl7.fhir.uv.subscriptions_1.1.0,106,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/OperationDefinition-backport-subscription-status.html,"id Parameter: At the Instance level, this parameter is ignored.",SHALL,Server,,,,"",""
|
|
210
|
+
hl7.fhir.uv.subscriptions_1.1.0,107,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/OperationDefinition-backport-subscription-status.html,"id Parameter: At the Resource level … multiple values are joined via OR (e.g., ""id1"" OR ""id2"").",SHALL,Server,,,,"",""
|
|
211
|
+
hl7.fhir.uv.subscriptions_1.1.0,108,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/OperationDefinition-backport-subscription-status.html,"id Parameter: At the Resource level … In the absence of any specified ids, the server returns the status for all Subscriptions available to the caller.",SHALL,Server,,,,"",""
|
|
212
|
+
hl7.fhir.uv.subscriptions_1.1.0,109,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/OperationDefinition-backport-subscription-status.html,"status Parameter: At the Instance level, this parameter is ignored.",SHALL,Server,,,,"",""
|
|
213
|
+
hl7.fhir.uv.subscriptions_1.1.0,110,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/OperationDefinition-backport-subscription-status.html,"status Parameter: At the resource level, … Multiple values are joined via OR (e.g., ""error"" OR ""off"").",SHALL,Server,,,,"",""
|
|
214
|
+
hl7.fhir.uv.subscriptions_1.1.0,111,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/OperationDefinition-backport-subscription-status.html,"status Parameter: At the resource level, … In the absence of any specified status values, the server does not filter contents based on the status.",SHALL,Server,,,,"",""
|
|
215
|
+
hl7.fhir.uv.subscriptions_1.1.0,112,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/OperationDefinition-backport-subscription-status.html,"return Parameter: The operation returns a bundle containing one or more subscription status resources, one per Subscription being queried. The Bundle type is ""searchset"".",SHALL,Server,,,,"",""
|
|
216
|
+
hl7.fhir.uv.subscriptions_1.1.0,113,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/channels.html#rest-hook-1,Server may send notifications of type event-notification at any time.,MAY,Server,,,,"",""
|
|
217
|
+
hl7.fhir.uv.subscriptions_1.1.0,114,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/CapabilityStatement-backport-subscription-server-r4.html#subscription,[Subscription Resource] Conformance Expectation: SHALL,SHALL,Server,,,,"",""
|
|
218
|
+
hl7.fhir.uv.subscriptions_1.1.0,115,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/OperationDefinition-backport-subscription-events.html,"The [$events] operation returns a valid notification bundle, with the first entry being the subscription status information resource. The bundle type is ""history"".",SHALL,Server,,,,"",""
|
|
219
|
+
hl7.fhir.uv.subscriptions_1.1.0,117,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/OperationDefinition-backport-subscription-events.html,"[the content input indicates the] Requested content style of returned data [from the $events operation]…. This is a hint to the server what a client would prefer, and MAY be ignored.",MAY,Server,,Not Tested,"MAY requirement, support for which doesn't imply other requirements.",NA,NA
|
|
220
|
+
hl7.fhir.uv.subscriptions_1.1.0,118,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/OperationDefinition-backport-subscription-events.html,"[The eventsSinceNumber input indicates] The starting event number, inclusive of this event (lower bound).",SHALL,Server,,,,"",""
|
|
221
|
+
hl7.fhir.uv.subscriptions_1.1.0,119,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/OperationDefinition-backport-subscription-events.html,"[The eventsUntilNumber input indicates] The ending event number, inclusive of this event (upper bound).",SHALL,Server,,,,"",""
|
|
222
|
+
hl7.fhir.uv.subscriptions_1.1.0,120,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/CapabilityStatement-backport-subscription-server-r4.html#summary,"[servers] SHOULD support [profile]: Backported R5 Subscription [NOTE: narrative says SHALL, resource says SHOULD, future versions correct the narrative to SHOULD]",SHOULD,Server,,,,"",""
|
|
223
|
+
hl7.fhir.uv.subscriptions_1.1.0,121,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/CapabilityStatement-backport-subscription-server-r4.html#summary,SHALL support the $status operation,SHALL,Server,,,,"",""
|
|
224
|
+
hl7.fhir.uv.subscriptions_1.1.0,122,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/CapabilityStatement-backport-subscription-server-r4.html#summary,MAY support the $events operation,MAY,Server,,,,"",""
|
|
225
|
+
hl7.fhir.uv.subscriptions_1.1.0,123,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/CapabilityStatement-backport-subscription-server-r4.html#summary,MAY support the $get-ws-binding-token operation,MAY,Server,,Not Tested,Used for Websocket channels that Inferno does not currently support,NA,NA
|
|
226
|
+
hl7.fhir.uv.subscriptions_1.1.0,124,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/CapabilityStatement-backport-subscription-server-r4.html#summary,A Server SHALL be capable of returning a Subscription resource using: GET [base]/Subscription/[id],SHALL,Server,,,,"",""
|
|
227
|
+
hl7.fhir.uv.subscriptions_1.1.0,125,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/CapabilityStatement-backport-subscription-server-r4.html#summary,A Server SHOULD be capable of creating a Subscription resource using either: POST [base]/Subscription or PUT [base]/Subscription/[id],SHOULD,Server,,,,"",""
|
|
228
|
+
hl7.fhir.uv.subscriptions_1.1.0,126,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/CapabilityStatement-backport-subscription-server-r4.html#summary,A Server SHOULD be capable of modifying a Subscription resource using either: PUT [base]/Subscription/[id] or PATCH [base]/Subscription/[id],SHOULD,Server,,,,"",""
|
|
229
|
+
hl7.fhir.uv.subscriptions_1.1.0,127,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/CapabilityStatement-backport-subscription-server-r4.html#summary,A Server SHOULD be capable of deleting a Subscription resource using: DELETE [base]/Subscription/[id],SHOULD,Server,,,,"",""
|
|
230
|
+
hl7.fhir.uv.subscriptions_1.1.0,128,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/CapabilityStatement-backport-subscription-server-r4.html#summary,A Server [MAY] be capable of searching for Subscription resources using: GET [base]/Subscription/?[parameters],MAY,Server,,,,"",""
|
|
231
|
+
hl7.fhir.uv.subscriptions_1.1.0,129,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/CapabilityStatement-backport-subscription-server-r4.html#summary,Search Parameter Summary: SHALL [support] url,SHALL,Server,,,,"",""
|
|
232
|
+
hl7.fhir.uv.subscriptions_1.1.0,130,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/CapabilityStatement-backport-subscription-server-r4.html#summary,Search Parameter Summary: SHOULD [support] status,SHOULD,Server,,,,"",""
|
|
233
|
+
hl7.fhir.uv.subscriptions_1.1.0,131,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/StructureDefinition-backport-subscription-status-r4.html,[several SubscriptionStatus profile elements are flagged as must support],MAY,Server,,Not Verifiable,IG doesn't indicate what must support requirements are for the SubscriptionStatus profile (in contrast to the Subscription profile where they are provided),NA,NA
|
|
234
|
+
hl7.fhir.uv.subscriptions_1.1.0,133,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/conformance.html#conformance-in-fhir-r4,"In order to claim conformance with this guide, a server…SHALL support the Subscription resource (...write).",SHALL,Server,,,,1.03,davinci_pas_server_suite_v201-pas_server_v201_subscription_setup-subscriptions_r4_server_notification_delivery
|
|
235
|
+
hl7.fhir.uv.subscriptions_1.1.0,134,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/conformance.html#conformance-in-fhir-r4,"In order to claim conformance with this guide, a server…SHALL support the Subscription resource (read...).",SHALL,Server,,,,"",""
|
|
236
|
+
hl7.fhir.uv.subscriptions_1.1.0,135,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/conformance.html#backport-filter-criteria-1,Servers supporting this guide SHALL be able to read values in this [backport-filter-criteria - https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/StructureDefinition-backport-filter-criteria.html] extension.,SHALL,Server,,,,"",""
|
|
237
|
+
hl7.fhir.uv.subscriptions_1.1.0,136,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/conformance.html#backport-filter-criteria-1,Servers supporting this guide...SHALL be able to apply filters [from the backport-filter-criteria - https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/StructureDefinition-backport-filter-criteria.html extension] as described by any Subscription Topics the server advertises support for.,SHALL,Server,,,,"",""
|
|
238
|
+
hl7.fhir.uv.subscriptions_1.1.0,137,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/conformance.html#profile-support-1,a conformant server…SHALL communicate all profile data elements that are mandatory by that profile’s StructureDefinition [for the R4/B Topic-Based Subscription profile],SHALL,Server,,,,"",""
|
|
239
|
+
hl7.fhir.uv.subscriptions_1.1.0,138,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/conformance.html#profile-support-1,a conformant server…SHALL communicate all profile data elements that are mandatory by that profile’s StructureDefinition [for the R4 Topic-Based Subscription Notification Bundle],SHALL,Server,,,,"1.05, 2.3.2.03","davinci_pas_server_suite_v201-pas_server_v201_subscription_setup-subscriptions_r4_server_handshake_conformance, davinci_pas_server_suite_v201-Group02-pas_server_v201_pended_use_case-Group02-subscriptions_r4_server_id_only_conformance"
|
|
240
|
+
hl7.fhir.uv.subscriptions_1.1.0,139,https://hl7.org/fhir/uv/subscriptions-backport/STU1.1/conformance.html#profile-support-1,a conformant server…SHALL communicate all profile data elements that are mandatory by that profile’s StructureDefinition [for the R4 Backported R5 SubscriptionStatus],SHALL,Server,,,,"1.05, 2.3.2.03","davinci_pas_server_suite_v201-pas_server_v201_subscription_setup-subscriptions_r4_server_handshake_conformance, davinci_pas_server_suite_v201-Group02-pas_server_v201_pended_use_case-Group02-subscriptions_r4_server_id_only_conformance"
|
|
Binary file
|
data/lib/davinci_pas_test_kit.rb
CHANGED
metadata
CHANGED
|
@@ -1,14 +1,14 @@
|
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
|
2
2
|
name: davinci_pas_test_kit
|
|
3
3
|
version: !ruby/object:Gem::Version
|
|
4
|
-
version: 0.13.
|
|
4
|
+
version: 0.13.3
|
|
5
5
|
platform: ruby
|
|
6
6
|
authors:
|
|
7
7
|
- Inferno Team
|
|
8
8
|
autorequire:
|
|
9
9
|
bindir: bin
|
|
10
10
|
cert_chain: []
|
|
11
|
-
date: 2025-
|
|
11
|
+
date: 2025-07-02 00:00:00.000000000 Z
|
|
12
12
|
dependencies:
|
|
13
13
|
- !ruby/object:Gem::Dependency
|
|
14
14
|
name: inferno_core
|
|
@@ -16,56 +16,56 @@ dependencies:
|
|
|
16
16
|
requirements:
|
|
17
17
|
- - "~>"
|
|
18
18
|
- !ruby/object:Gem::Version
|
|
19
|
-
version: 0.6.
|
|
19
|
+
version: 0.6.16
|
|
20
20
|
type: :runtime
|
|
21
21
|
prerelease: false
|
|
22
22
|
version_requirements: !ruby/object:Gem::Requirement
|
|
23
23
|
requirements:
|
|
24
24
|
- - "~>"
|
|
25
25
|
- !ruby/object:Gem::Version
|
|
26
|
-
version: 0.6.
|
|
26
|
+
version: 0.6.16
|
|
27
27
|
- !ruby/object:Gem::Dependency
|
|
28
28
|
name: smart_app_launch_test_kit
|
|
29
29
|
requirement: !ruby/object:Gem::Requirement
|
|
30
30
|
requirements:
|
|
31
31
|
- - "~>"
|
|
32
32
|
- !ruby/object:Gem::Version
|
|
33
|
-
version: 0.6.
|
|
33
|
+
version: 0.6.4
|
|
34
34
|
type: :runtime
|
|
35
35
|
prerelease: false
|
|
36
36
|
version_requirements: !ruby/object:Gem::Requirement
|
|
37
37
|
requirements:
|
|
38
38
|
- - "~>"
|
|
39
39
|
- !ruby/object:Gem::Version
|
|
40
|
-
version: 0.6.
|
|
40
|
+
version: 0.6.4
|
|
41
41
|
- !ruby/object:Gem::Dependency
|
|
42
42
|
name: subscriptions_test_kit
|
|
43
43
|
requirement: !ruby/object:Gem::Requirement
|
|
44
44
|
requirements:
|
|
45
45
|
- - "~>"
|
|
46
46
|
- !ruby/object:Gem::Version
|
|
47
|
-
version: 0.11.
|
|
47
|
+
version: 0.11.3
|
|
48
48
|
type: :runtime
|
|
49
49
|
prerelease: false
|
|
50
50
|
version_requirements: !ruby/object:Gem::Requirement
|
|
51
51
|
requirements:
|
|
52
52
|
- - "~>"
|
|
53
53
|
- !ruby/object:Gem::Version
|
|
54
|
-
version: 0.11.
|
|
54
|
+
version: 0.11.3
|
|
55
55
|
- !ruby/object:Gem::Dependency
|
|
56
56
|
name: udap_security_test_kit
|
|
57
57
|
requirement: !ruby/object:Gem::Requirement
|
|
58
58
|
requirements:
|
|
59
59
|
- - "~>"
|
|
60
60
|
- !ruby/object:Gem::Version
|
|
61
|
-
version: 0.11.
|
|
61
|
+
version: 0.11.6
|
|
62
62
|
type: :runtime
|
|
63
63
|
prerelease: false
|
|
64
64
|
version_requirements: !ruby/object:Gem::Requirement
|
|
65
65
|
requirements:
|
|
66
66
|
- - "~>"
|
|
67
67
|
- !ruby/object:Gem::Version
|
|
68
|
-
version: 0.11.
|
|
68
|
+
version: 0.11.6
|
|
69
69
|
- !ruby/object:Gem::Dependency
|
|
70
70
|
name: database_cleaner-sequel
|
|
71
71
|
requirement: !ruby/object:Gem::Requirement
|
|
@@ -319,9 +319,10 @@ files:
|
|
|
319
319
|
- lib/davinci_pas_test_kit/must_support_test.rb
|
|
320
320
|
- lib/davinci_pas_test_kit/pas_bundle_validation.rb
|
|
321
321
|
- lib/davinci_pas_test_kit/pas_subscription_verification.rb
|
|
322
|
-
- lib/davinci_pas_test_kit/requirements/
|
|
323
|
-
- lib/davinci_pas_test_kit/requirements/
|
|
324
|
-
- lib/davinci_pas_test_kit/requirements/generated/
|
|
322
|
+
- lib/davinci_pas_test_kit/requirements/davinci_pas_test_kit_requirements.csv
|
|
323
|
+
- lib/davinci_pas_test_kit/requirements/generated/davinci_pas_client_suite_v201_requirements_coverage.csv
|
|
324
|
+
- lib/davinci_pas_test_kit/requirements/generated/davinci_pas_server_suite_v201_requirements_coverage.csv
|
|
325
|
+
- lib/davinci_pas_test_kit/requirements/hl7.fhir.us.davinci-pas_2.0.1_requirements.xlsx
|
|
325
326
|
- lib/davinci_pas_test_kit/response_generator.rb
|
|
326
327
|
- lib/davinci_pas_test_kit/session_identification.rb
|
|
327
328
|
- lib/davinci_pas_test_kit/tags.rb
|
|
@@ -330,9 +331,6 @@ files:
|
|
|
330
331
|
- lib/davinci_pas_test_kit/validation_test.rb
|
|
331
332
|
- lib/davinci_pas_test_kit/validator_suppressions.rb
|
|
332
333
|
- lib/davinci_pas_test_kit/version.rb
|
|
333
|
-
- lib/inferno_requirements_tools/ext/inferno_core/runnable.rb
|
|
334
|
-
- lib/inferno_requirements_tools/tasks/requirements_coverage.rb
|
|
335
|
-
- lib/requirements_config.yaml
|
|
336
334
|
homepage: https://github.com/inferno-framework/davinci-pas-test-kit
|
|
337
335
|
licenses:
|
|
338
336
|
- Apache-2.0
|
data/lib/davinci_pas_test_kit/requirements/davinci-pas-test-kit_out_of_scope_requirements.csv
DELETED
|
@@ -1,11 +0,0 @@
|
|
|
1
|
-
Req Set,ID,Reason,Details
|
|
2
|
-
hl7.fhir.us.davinci-pas_2.0.1,12,Not Tested,Details of X12 messages will not be tested by Inferno.
|
|
3
|
-
hl7.fhir.us.davinci-pas_2.0.1,13,Not Tested,Details of X12 messages will not be tested by Inferno.
|
|
4
|
-
hl7.fhir.us.davinci-pas_2.0.1,14,Not Tested,Details of X12 messages will not be tested by Inferno.
|
|
5
|
-
hl7.fhir.us.davinci-pas_2.0.1,15,Not Tested,Details of X12 messages will not be tested by Inferno.
|
|
6
|
-
hl7.fhir.us.davinci-pas_2.0.1,96,Not Tested,Details of X12 messages will not be tested by Inferno.
|
|
7
|
-
hl7.fhir.us.davinci-pas_2.0.1,108,Not Verifiable,The specification does not provide clear details on the indicated responses (unclear diagram)
|
|
8
|
-
hl7.fhir.us.davinci-pas_2.0.1,109,Not Verifiable,The specification does not provide clear details on the indicated responses (unclear diagram)
|
|
9
|
-
hl7.fhir.us.davinci-pas_2.0.1,124,Not Tested,The rules for determining matching claims are specified in a proprietary X12 specification.
|
|
10
|
-
hl7.fhir.us.davinci-pas_2.0.1,132,Not Tested,How to request a subset of information is not detailed in the specification and lives in priopietary X12 specifications and mappings.
|
|
11
|
-
hl7.fhir.us.davinci-pas_2.0.1,191,Not Tested,Details of payer business rules will not be tested by Inferno.
|