davinci_pas_test_kit 0.14.0 → 0.15.0

data/lib/davinci_pas_test_kit/requirements/generated/davinci_pas_server_suite_v221_requirements_coverage.csv

@@ -0,0 +1,212 @@
+Req Set,ID,URL,Requirement,Conformance,Actors,Conditionality,Not Tested Reason,Not Tested Details,Da Vinci PAS Server Suite v2.2.1 Short ID(s),Da Vinci PAS Server Suite v2.2.1 Full ID(s)
+hl7.fhir.us.davinci-pas_2.2.1,ainfo-1,https://hl7.org/fhir/us/davinci-pas/2.2.1/en/additionalinfo.html#ci-c-ainfo-1,"Payers **SHOULD** attempt to use the initial DTR invocation to gather all relevant information relevant to the prior authorization request and only use the ""additional information"" approach when human review or other circumstances not known at the time of the initial DTR call require additional information to be collected.",SHOULD,PAS Payer,false,,,"",""
+hl7.fhir.us.davinci-pas_2.2.1,ainfo-2,https://hl7.org/fhir/us/davinci-pas/2.2.1/en/additionalinfo.html#ci-c-ainfo-2,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,MAY,PAS Payer,false,,,"",""
+hl7.fhir.us.davinci-pas_2.2.1,ainfo-3,https://hl7.org/fhir/us/davinci-pas/2.2.1/en/additionalinfo.html#ci-c-ainfo-3,"When a single LOINC code is used, 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,PAS Payer,false,,,"",""
+hl7.fhir.us.davinci-pas_2.2.1,conf-1,https://hl7.org/fhir/us/davinci-pas/2.2.1/en/conformance.html#ci-c-conf-1,Payers **SHALL** have a distinct endpoint for each different supported version (which are not inter-version compatible) of the PAS specification.,SHALL,PAS Payer,false,,,"",""
+hl7.fhir.us.davinci-pas_2.2.1,conf-2,https://hl7.org/fhir/us/davinci-pas/2.2.1/en/conformance.html#ci-c-conf-2,"If a payer supports endpoint discovery, they **SHALL** have at most a single endpoint for each combination of version of the specification and coverage (e.g., Medicare, Medicaid, or commercial) they provide coverage under.",SHALL,PAS Payer,false,,,"",""
+hl7.fhir.us.davinci-pas_2.2.1,conf-3,https://hl7.org/fhir/us/davinci-pas/2.2.1/en/conformance.html#ci-c-conf-3,"If a payer does not support endpoint discovery, they **SHALL** expose only one PAS endpoint of each supported version capable of handling all coverages.",SHALL,PAS Payer,false,,,"",""
+hl7.fhir.us.davinci-pas_2.2.1,conf-4,https://hl7.org/fhir/us/davinci-pas/2.2.1/en/conformance.html#ci-c-conf-4,PA Intermediary Systems **SHALL** be capable of processing all data elements that are marked as Must Support on the Claim Request and Claim Inquiry.,SHALL,PAS Payer,false,,,"",""
+hl7.fhir.us.davinci-pas_2.2.1,conf-5,https://hl7.org/fhir/us/davinci-pas/2.2.1/en/conformance.html#ci-c-conf-5,They **SHALL NOT** generate an error or cause the application to fail due the presence of any data element marked as Must Support.,SHALL NOT,PAS Payer,false,,,"",""
+hl7.fhir.us.davinci-pas_2.2.1,conf-6,https://hl7.org/fhir/us/davinci-pas/2.2.1/en/conformance.html#ci-c-conf-6,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 and the Claim Inquiry Response.,SHALL,PAS Payer,false,,,"",""
+hl7.fhir.us.davinci-pas_2.2.1,conf-10,https://hl7.org/fhir/us/davinci-pas/2.2.1/en/conformance.html#ci-c-conf-10,"If these data elements are included in a Claim Request or Claim Inquiry, the receiving PA Intermediary System **MAY** ignore those elements.",MAY,PAS Payer,false,,,"",""
+hl7.fhir.us.davinci-pas_2.2.1,conf-11,https://hl7.org/fhir/us/davinci-pas/2.2.1/en/conformance.html#ci-c-conf-11,"When processing prior auth requests and additional data submissions, PAS services **SHALL NOT** depend on or set expectations for the inclusion of resource instances not compliant with profiles defined in this guide, CRD, DTR, HRex, or US Core.",SHALL NOT,PAS Payer,false,,,"",""
+hl7.fhir.us.davinci-pas_2.2.1,conf-12,https://hl7.org/fhir/us/davinci-pas/2.2.1/en/conformance.html#ci-c-conf-12,"Similarly, they **SHALL NOT** depend on or set expectations for the inclusion of any data elements not marked as mandatory (min cardinality >= 1) or mustSupport in those profiles.",SHALL NOT,PAS Payer,false,,,"",""
+hl7.fhir.us.davinci-pas_2.2.1,conf-13,https://hl7.org/fhir/us/davinci-pas/2.2.1/en/conformance.html#ci-c-conf-13,"If the proposed change is adopted and published in the PAS continuous integration build or the CI build of one of its dependencies (e.g. US Core), implementations **MAY**, by mutual agreement, pre-adopt the use of those additional profiles and/or mustSupport data elements and not be considered in violation of #1 above.",MAY,"PAS Client,PAS Payer",false,,,"",""
+hl7.fhir.us.davinci-pas_2.2.1,conf-14,https://hl7.org/fhir/us/davinci-pas/2.2.1/en/conformance.html#ci-c-conf-14,"Where cardinality and other constraints present in profiles allow data elements to be omitted, PAS compliant systems **SHALL NOT** treat the omission of those elements as a conformance error.",SHALL NOT,"PAS Client,PAS Payer",false,,,"",""
+hl7.fhir.us.davinci-pas_2.2.1,conf-15,https://hl7.org/fhir/us/davinci-pas/2.2.1/en/conformance.html#ci-c-conf-15,PAS clients and services **SHALL** use standard PAS data elements (i.e. elements found within PAS-defined or inherited profiles and marked as mandatory or mustSupport) to communicate needed data if such elements are intended to convey such information.,SHALL,"PAS Client,PAS Payer",false,,,"",""
+hl7.fhir.us.davinci-pas_2.2.1,conf-16,https://hl7.org/fhir/us/davinci-pas/2.2.1/en/conformance.html#ci-c-conf-16,"PAS implementing organizations **SHALL NOT** publish guidance setting expectations for where certain data elements are conveyed within PAS and inherited data structures, but **MAY** submit change requests to PAS, HRex, or US Core requesting that additional guidance be provided to implementers on data structure usage to increase consistency across implementations.",SHALL NOT / MAY,"PAS Client,PAS Payer",false,,,"",""
+hl7.fhir.us.davinci-pas_2.2.1,metric-1,https://hl7.org/fhir/us/davinci-pas/2.2.1/en/metrics.html#ci-c-metric-1,"Each of these IGs recommends a set of metrics that **SHOULD** or **MAY** be collected by their respective implementations to facilitate the evaluation of adoption, functionality, processes, and improved outcomes.",SHOULD / MAY,"PAS Client,PAS Payer",false,,,"",""
+hl7.fhir.us.davinci-pas_2.2.1,metric-2,https://hl7.org/fhir/us/davinci-pas/2.2.1/en/metrics.html#ci-c-metric-2,PAS implementers **SHOULD** store information for each PAS call in a manner that would allow them to respond to measures based on this logical model.,SHOULD,"PAS Client,PAS Payer",false,,,"",""
+hl7.fhir.us.davinci-pas_2.2.1,priv-2,https://hl7.org/fhir/us/davinci-pas/2.2.1/en/privacy.html#ci-c-priv-2,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,PAS Payer,false,,,"",""
+hl7.fhir.us.davinci-pas_2.2.1,priv-3,https://hl7.org/fhir/us/davinci-pas/2.2.1/en/privacy.html#ci-c-priv-3,PAS Servers **SHOULD** support server-server OAuth and **MAY** support mutually authenticated TLS.,SHOULD / MAY,PAS Payer,false,,,"",""
+hl7.fhir.us.davinci-pas_2.2.1,prof-2,https://hl7.org/fhir/us/davinci-pas/2.2.1/en/StructureDefinition-profile-quantity.html#ci-c-prof-2,Quantities **SHALL** have a value and either a unit or a code,SHALL,"PAS Client,PAS Payer",false,,,"",""
+hl7.fhir.us.davinci-pas_2.2.1,prof-3,https://hl7.org/fhir/us/davinci-pas/2.2.1/en/StructureDefinition-profile-quantity.html#ci-c-prof-3,"If a quantity code is present, it **SHALL** use the X12 quantity units.",SHALL,"PAS Client,PAS Payer",false,,,"",""
+hl7.fhir.us.davinci-pas_2.2.1,prof-ben-1,https://hl7.org/fhir/us/davinci-pas/2.2.1/en/StructureDefinition-profile-beneficiary.html#ci-c-prof-ben-1,"X12 standard requires no dash for ZIP+4 codes and that intermediaries **SHALL** expect the dash to be present and **SHALL** remove the dash, if present, when converting the zip code to meet the X12 standard.",SHALL,PAS Payer,false,,,"",""
+hl7.fhir.us.davinci-pas_2.2.1,prof-sub-1,https://hl7.org/fhir/us/davinci-pas/2.2.1/en/StructureDefinition-profile-subscriber.html#ci-c-prof-sub-1,"X12 standard requires no dash for ZIP+4 codes and that intermediaries **SHALL** expect the dash to be present and **SHALL** remove the dash, if present, when converting the zip code to meet the X12 standard.",SHALL,PAS Payer,false,,,"",""
+hl7.fhir.us.davinci-pas_2.2.1,spec-1,https://hl7.org/fhir/us/davinci-pas/2.2.1/en/specification.html#ci-c-spec-1,"Along with the profiles defined in the PAS implementation guide, implementations **SHALL** also support the relevant US Core profiles for supplementary information.",SHALL,"PAS Client,PAS Payer",true,,,"",""
+hl7.fhir.us.davinci-pas_2.2.1,spec-2,https://hl7.org/fhir/us/davinci-pas/2.2.1/en/specification.html#ci-c-spec-2,They **SHOULD** support any other profiles relevant to the types of prior authorizations they process.,SHOULD,"PAS Client,PAS Payer",true,,,"",""
+hl7.fhir.us.davinci-pas_2.2.1,spec-3,https://hl7.org/fhir/us/davinci-pas/2.2.1/en/specification.html#ci-c-spec-3,Clients and Servers supporting this implementation guide **SHOULD** also comply with the Da Vinci [Coverage Requirements Discovery (CRD)](http://www.hl7.org/fhir/us/davinci-crd) and [Documentation Templates and Rules (DTR)](http://www.hl7.org/fhir/us/davinci-dtr) implementation guides.,SHOULD,"PAS Client,PAS Payer",true,,,"",""
+hl7.fhir.us.davinci-pas_2.2.1,spec-4,https://hl7.org/fhir/us/davinci-pas/2.2.1/en/specification.html#ci-c-spec-4,Every system 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,"PAS Client,PAS Payer",true,,,"",""
+hl7.fhir.us.davinci-pas_2.2.1,spec-5,https://hl7.org/fhir/us/davinci-pas/2.2.1/en/specification.html#ci-c-spec-5,"If a payer supports endpoint discovery, they **SHALL** have at most a single endpoint for each coverage (e.g., Medicare, Medicaid, or commercial) they provide coverage under.",SHALL,PAS Payer,true,,,"",""
+hl7.fhir.us.davinci-pas_2.2.1,spec-6,https://hl7.org/fhir/us/davinci-pas/2.2.1/en/specification.html#ci-c-spec-6,"If a payer does not support endpoint discovery, they **SHALL** expose only one PAS endpoint capable of handling all coverages.",SHALL,PAS Payer,true,,,"",""
+hl7.fhir.us.davinci-pas_2.2.1,spec-7,https://hl7.org/fhir/us/davinci-pas/2.2.1/en/specification.html#ci-c-spec-7,All of this **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.,SHOULD,PAS Payer,false,,,"",""
+hl7.fhir.us.davinci-pas_2.2.1,spec-9,https://hl7.org/fhir/us/davinci-pas/2.2.1/en/specification.html#ci-c-spec-9,"**NOTE**: The Claim Inquiry response does not include all of the information that can be returned in a request response, such as any request for additional information, so the inquire operation **SHOULD NOT** be used by the client while waiting for final results.",SHOULD NOT,"PAS Payer,PAS Client",false,,,"",""
+hl7.fhir.us.davinci-pas_2.2.1,spec-10,https://hl7.org/fhir/us/davinci-pas/2.2.1/en/specification.html#ci-c-spec-10,Provider and EHR Vendor organizations **MAY** leverage the [payer registry](https://www.hl7.org/fhir/us/davinci-pdex/payertopayerexchange.html#mtls-endpoint-discovery) developed by PDex (which will eventually fold into the national directory under FAST) as a means of determining which endpoints exist for which payers as candidates for configuration.,MAY,PAS Payer,false,,,"",""
+hl7.fhir.us.davinci-pas_2.2.1,spec-11,https://hl7.org/fhir/us/davinci-pas/2.2.1/en/specification.html#ci-c-spec-11,The Bundle **SHALL** be encoded in JSON.,SHALL,PAS Payer,false,,,"",""
+hl7.fhir.us.davinci-pas_2.2.1,spec-12,https://hl7.org/fhir/us/davinci-pas/2.2.1/en/specification.html#ci-c-spec-12,The first entry in the Bundle **SHALL** be a Claim resource complying with the [profile](StructureDefinition-profile-claim.html) defined in this IG to ensure the content is sufficient to appropriately populate an X12N/005010X217 message.,SHALL,PAS Payer,false,,,"",""
+hl7.fhir.us.davinci-pas_2.2.1,spec-13,https://hl7.org/fhir/us/davinci-pas/2.2.1/en/specification.html#ci-c-spec-13,"Additional Bundle entries **SHALL** be populated with any resources referenced by the Claim resource (and any resources referenced by *those* resources, fully traversing all references and complying with all identified profiles).",SHALL,PAS Payer,false,,,"",""
+hl7.fhir.us.davinci-pas_2.2.1,spec-14,https://hl7.org/fhir/us/davinci-pas/2.2.1/en/specification.html#ci-c-spec-14,Each unique resource instance **SHALL** only appear at most once in the Bundle.,SHALL,PAS Payer,false,,,"",""
+hl7.fhir.us.davinci-pas_2.2.1,spec-15,https://hl7.org/fhir/us/davinci-pas/2.2.1/en/specification.html#ci-c-spec-15,"Only one unique resource instance **SHOULD** be created to represent the same information. In other words, avoid creating multiple Practitioner instances for the same person.",SHOULD,PAS Payer,false,,,"",""
+hl7.fhir.us.davinci-pas_2.2.1,spec-16,https://hl7.org/fhir/us/davinci-pas/2.2.1/en/specification.html#ci-c-spec-16,"Bundle.entry.fullUrl values **SHALL** be:
+- the URL at which the resource is available from the EHR if exposed via the client's REST interface; or
+- the form ""urn:uuid:[some guid]""",SHALL,PAS Payer,false,,,"",""
+hl7.fhir.us.davinci-pas_2.2.1,spec-17,https://hl7.org/fhir/us/davinci-pas/2.2.1/en/specification.html#ci-c-spec-17,"All GUIDs used **SHALL** be unique, including across independent prior authorization submissions - with the exception that the same resource instance being referenced in distinct prior authorization request Bundles can have the same GUID.",SHALL,PAS Payer,false,,,"",""
+hl7.fhir.us.davinci-pas_2.2.1,spec-18,https://hl7.org/fhir/us/davinci-pas/2.2.1/en/specification.html#ci-c-spec-18,"Relevant resources referenced by those ""supporting information"" resources **SHALL** also be included (e.g. prescriber Practitioner and Medication for a MedicationRequest).",SHALL,PAS Payer,false,,,"",""
+hl7.fhir.us.davinci-pas_2.2.1,spec-19,https://hl7.org/fhir/us/davinci-pas/2.2.1/en/specification.html#ci-c-spec-19,Any such resource that has a US Core profile **SHALL** comply with the relevant US Core profiles.,SHALL,PAS Payer,false,,,"",""
+hl7.fhir.us.davinci-pas_2.2.1,spec-20,https://hl7.org/fhir/us/davinci-pas/2.2.1/en/specification.html#ci-c-spec-20,"All ""supporting information"" resources included in the Bundle **SHALL** be pointed to by the Claim resource using the Claim.supportingInfo.valueReference element.",SHALL,PAS Payer,false,,,"",""
+hl7.fhir.us.davinci-pas_2.2.1,spec-21,https://hl7.org/fhir/us/davinci-pas/2.2.1/en/specification.html#ci-c-spec-21,"To attach non-FHIR instance data such as PDFs, CDAs, JPGs, a DocumentReference instance **SHOULD** be used.",SHOULD,PAS Payer,false,,,"",""
+hl7.fhir.us.davinci-pas_2.2.1,spec-22,https://hl7.org/fhir/us/davinci-pas/2.2.1/en/specification.html#ci-c-spec-22,The Claim.supportingInfo.sequence for each entry **SHALL** be unique within the Claim.,SHALL,PAS Payer,false,,,"",""
+hl7.fhir.us.davinci-pas_2.2.1,spec-23,https://hl7.org/fhir/us/davinci-pas/2.2.1/en/specification.html#ci-c-spec-23,All resources **SHALL** comply with their respective profiles.,SHALL,PAS Payer,false,,,"",""
+hl7.fhir.us.davinci-pas_2.2.1,spec-24,https://hl7.org/fhir/us/davinci-pas/2.2.1/en/specification.html#ci-c-spec-24,"FHIR elements not marked as 'must support' **MAY** be included in resources within the Bundle, but client systems **SHOULD** have no expectation of such elements being processed by the payer unless prior arrangements have been made.",SHOULD / MAY,"PAS Client,PAS Payer",false,,,"",""
+hl7.fhir.us.davinci-pas_2.2.1,spec-25,https://hl7.org/fhir/us/davinci-pas/2.2.1/en/specification.html#ci-c-spec-25,"Systems that do not process such elements **SHALL** ignore unsupported elements unless they are 'modifier' elements, in which case the system **MAY** treat the presence of the element as an error.",SHALL / MAY,PAS Payer,false,,,"",""
+hl7.fhir.us.davinci-pas_2.2.1,spec-26,https://hl7.org/fhir/us/davinci-pas/2.2.1/en/specification.html#ci-c-spec-26,"In addition, the system **SHALL** make the entire PAS FHIR Bundle available to the intended payer.",SHALL,PAS Payer,false,,,"",""
+hl7.fhir.us.davinci-pas_2.2.1,spec-27,https://hl7.org/fhir/us/davinci-pas/2.2.1/en/specification.html#ci-c-spec-27,The method **MAY** be based on the X12 275 or another method that trading partners have agreed to use.,MAY,PAS Payer,false,,,"",""
+hl7.fhir.us.davinci-pas_2.2.1,spec-28,https://hl7.org/fhir/us/davinci-pas/2.2.1/en/specification.html#ci-c-spec-28,"If the X12 275 is used for this purpose, the 275 BDS01 Filter ID Code element **SHALL** be set to ""B64"" and the CAT02 Attachment Information Format Code element **SHALL** be sent to ""HL"".",SHALL,PAS Payer,false,,,"",""
+hl7.fhir.us.davinci-pas_2.2.1,spec-29,https://hl7.org/fhir/us/davinci-pas/2.2.1/en/specification.html#ci-c-spec-29,"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.",SHOULD,PAS Payer,false,,,"",""
+hl7.fhir.us.davinci-pas_2.2.1,spec-30,https://hl7.org/fhir/us/davinci-pas/2.2.1/en/specification.html#ci-c-spec-30,The Bundle **SHALL** start with a [ClaimResponse](StructureDefinition-profile-claimresponse-base.html) entry that contains information mapped from the 278 response.,SHALL,PAS Payer,false,,,"",""
+hl7.fhir.us.davinci-pas_2.2.1,spec-31,https://hl7.org/fhir/us/davinci-pas/2.2.1/en/specification.html#ci-c-spec-31,Each unique resource instance **SHALL** only appear at most once in the Bundle.,SHALL,PAS Payer,false,,,"",""
+hl7.fhir.us.davinci-pas_2.2.1,spec-32,https://hl7.org/fhir/us/davinci-pas/2.2.1/en/specification.html#ci-c-spec-32,"Only one unique resource instance **SHOULD** be created to represent the same information. In other words, avoid creating multiple Practitioner instances for the same person.",SHOULD,PAS Payer,false,,,"",""
+hl7.fhir.us.davinci-pas_2.2.1,spec-33,https://hl7.org/fhir/us/davinci-pas/2.2.1/en/specification.html#ci-c-spec-33,"When echoing back resources that are the same as were present in the prior authorization request, the system **SHALL** ensure that the same fullUrl and resource identifiers are used in the response as appeared in the request.",SHALL,PAS Payer,false,,,"",""
+hl7.fhir.us.davinci-pas_2.2.1,spec-34,https://hl7.org/fhir/us/davinci-pas/2.2.1/en/specification.html#ci-c-spec-34,Each item returned on the PAS ClaimResponse **SHALL** echo the same item.sequence as that same item had on the Claim. The item.sequence element **SHALL** serve as the main tracing identifier of items throughout requests and responses.,SHALL,PAS Payer,false,,,2.4.5.01,davinci_pas_server_suite_v221-Group02-pas_server_v221_claim_updates-Group05-pas_server_v221_claim_update_item_sequence_echo_test
+hl7.fhir.us.davinci-pas_2.2.1,spec-35,https://hl7.org/fhir/us/davinci-pas/2.2.1/en/specification.html#ci-c-spec-35,"In the case of an error in an Operation invocation (e.g., 4XX error), the receiving system **SHALL** return a single OperationOutcome that details why the Bundle could not be processed.",SHALL,PAS Payer,false,,,"",""
+hl7.fhir.us.davinci-pas_2.2.1,spec-36,https://hl7.org/fhir/us/davinci-pas/2.2.1/en/specification.html#ci-c-spec-36,"For instances where the authorized item is a modification of the requested item, the requested item details **SHALL** be returned in the ClaimResponse.item with an adjudication status of A6 - 'Modified'.",SHALL,PAS Payer,false,,,"",""
+hl7.fhir.us.davinci-pas_2.2.1,spec-37,https://hl7.org/fhir/us/davinci-pas/2.2.1/en/specification.html#ci-c-spec-37,The details of what was actually item **SHALL** be returned in the ClaimResponse.addItem.,SHALL,PAS Payer,false,,,"",""
+hl7.fhir.us.davinci-pas_2.2.1,spec-38,https://hl7.org/fhir/us/davinci-pas/2.2.1/en/specification.html#ci-c-spec-38,Recipients of the transactions **SHOULD** respond as indicated below and senders of the transaction **SHOULD** look for the following responses and then take appropriate actions.,SHOULD,"PAS Client,PAS Payer",false,,,"",""
+hl7.fhir.us.davinci-pas_2.2.1,spec-39,https://hl7.org/fhir/us/davinci-pas/2.2.1/en/specification.html#ci-c-spec-39,All transactions in PAS are synchronous and **SHALL** require one of the following HTTP responses:,SHALL,PAS Payer,false,,,"",""
+hl7.fhir.us.davinci-pas_2.2.1,spec-41,https://hl7.org/fhir/us/davinci-pas/2.2.1/en/specification.html#ci-c-spec-41,NOTE: These errors **SHOULD** not be returned to the provider but **SHOULD** be reviewed and addressed by technical staff.,SHOULD,PAS Payer,false,,,"",""
+hl7.fhir.us.davinci-pas_2.2.1,spec-43,https://hl7.org/fhir/us/davinci-pas/2.2.1/en/specification.html#ci-c-spec-43,Intermediaries **SHALL** interpret the 'not-applicable' code as no product or service code.,SHALL,PAS Payer,false,,,"",""
+hl7.fhir.us.davinci-pas_2.2.1,spec-44,https://hl7.org/fhir/us/davinci-pas/2.2.1/en/specification.html#ci-c-spec-44,This Claim Inquiry Response **SHALL** either reference a Claim or have a Data Absent Reason indicating why the Claim can not be referenced (eg. original claim received by fax).,SHALL,PAS Payer,false,,,"",""
+hl7.fhir.us.davinci-pas_2.2.1,spec-45,https://hl7.org/fhir/us/davinci-pas/2.2.1/en/specification.html#ci-c-spec-45,The referenced Claim instance **SHOULD** be returned if there is information in the Response that needs to be present can not be returned in the Claim Response instance.,SHOULD,PAS Payer,false,,,"",""
+hl7.fhir.us.davinci-pas_2.2.1,spec-46,https://hl7.org/fhir/us/davinci-pas/2.2.1/en/specification.html#ci-c-spec-46,"the returned ClaimResponse **SHALL** include the current results for all submitted items, including any items changed or canceled since the original authoriation request.",SHALL,PAS Payer,false,,,2.4.5.02,davinci_pas_server_suite_v221-Group02-pas_server_v221_claim_updates-Group05-pas_server_v221_claim_update_current_results_test
+hl7.fhir.us.davinci-pas_2.2.1,spec-47,https://hl7.org/fhir/us/davinci-pas/2.2.1/en/specification.html#ci-c-spec-47,"if a specific reference number (either the REF-NT or REF-BB) is submitted and is not the 'current' number (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.",SHALL,"PAS Client,PAS Payer",false,,,"",""
+hl7.fhir.us.davinci-pas_2.2.1,spec-48,https://hl7.org/fhir/us/davinci-pas/2.2.1/en/specification.html#ci-c-spec-48,"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,PAS Payer,false,,,"",""
+hl7.fhir.us.davinci-pas_2.2.1,spec-49,https://hl7.org/fhir/us/davinci-pas/2.2.1/en/specification.html#ci-c-spec-49,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,PAS Payer,false,,,"",""
+hl7.fhir.us.davinci-pas_2.2.1,spec-50,https://hl7.org/fhir/us/davinci-pas/2.2.1/en/specification.html#ci-c-spec-50,In such situations 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,PAS Payer,false,,,"",""
+hl7.fhir.us.davinci-pas_2.2.1,spec-51,https://hl7.org/fhir/us/davinci-pas/2.2.1/en/specification.html#ci-c-spec-51,Implementers **SHALL** support subscriptions to provide the final response.,SHALL,PAS Payer,false,,,"",""
+hl7.fhir.us.davinci-pas_2.2.1,spec-52,https://hl7.org/fhir/us/davinci-pas/2.2.1/en/specification.html#ci-c-spec-52,Servers **SHALL** permit access to the prior authorization response to systems other than the original submitter.,SHALL,PAS Payer,false,,,"",""
+hl7.fhir.us.davinci-pas_2.2.1,spec-53,https://hl7.org/fhir/us/davinci-pas/2.2.1/en/specification.html#ci-c-spec-53,"They **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.",SHALL,PAS Payer,false,,,"",""
+hl7.fhir.us.davinci-pas_2.2.1,spec-54,https://hl7.org/fhir/us/davinci-pas/2.2.1/en/specification.html#ci-c-spec-54,Implementers **SHALL** support the R4 Subscriptions referenced in the [Subscriptions for R5 Backport Implementation Guide](http://hl7.org/fhir/uv/subscriptions-backport/).,SHALL,PAS Payer,false,,,"",""
+hl7.fhir.us.davinci-pas_2.2.1,spec-55,https://hl7.org/fhir/us/davinci-pas/2.2.1/en/specification.html#ci-c-spec-55,Servers supporting subscriptions **SHALL** expose this as part of their CapabilityStatement,SHALL,PAS Payer,false,,,"",""
+hl7.fhir.us.davinci-pas_2.2.1,spec-56,https://hl7.org/fhir/us/davinci-pas/2.2.1/en/specification.html#ci-c-spec-56,Servers **SHALL** only support the [rest-hook channel type](https://hl7.org/fhir/uv/subscriptions-backport/channels.html#rest-hook-1),SHALL,PAS Payer,false,,,"",""
+hl7.fhir.us.davinci-pas_2.2.1,spec-57,https://hl7.org/fhir/us/davinci-pas/2.2.1/en/specification.html#ci-c-spec-57,This Subscription **SHALL** conform to the [PAS Subscription profile](StructureDefinition-profile-subscription.html).,SHALL,PAS Payer,false,,,"",""
+hl7.fhir.us.davinci-pas_2.2.1,spec-58,https://hl7.org/fhir/us/davinci-pas/2.2.1/en/specification.html#ci-c-spec-58,The Subscription filter criteria **SHALL** be org-identifier = [sending system identifier].,SHALL,PAS Payer,false,,,"",""
+hl7.fhir.us.davinci-pas_2.2.1,spec-59,https://hl7.org/fhir/us/davinci-pas/2.2.1/en/specification.html#ci-c-spec-59,Intermediaries **SHALL** ensure that subscriptions to monitor a particular sending system's prior authorizations are only created or modified by that sending system.,SHALL,PAS Payer,false,,,"",""
+hl7.fhir.us.davinci-pas_2.2.1,spec-60,https://hl7.org/fhir/us/davinci-pas/2.2.1/en/specification.html#ci-c-spec-60,"Once the [subscription](Subscription-PASSubscriptionExample.html) has been created, the Server **SHALL** send a [notification](Bundle-PASSubscriptionNotification.html) over the requested channel indicating that a prior authorization response submitted by the requesting provider organization has changed.",SHALL,PAS Payer,false,,,"",""
+hl7.fhir.us.davinci-pas_2.2.1,spec-61,https://hl7.org/fhir/us/davinci-pas/2.2.1/en/specification.html#ci-c-spec-61,This notification **SHALL** include a full PAS Response Bundle.,SHALL,PAS Payer,false,,,"",""
+hl7.fhir.us.davinci-pas_2.2.1,spec-62,https://hl7.org/fhir/us/davinci-pas/2.2.1/en/specification.html#ci-c-spec-62,"Due to the inquiry not supporting all of the required information needed in a PAS response, PAS Clients and Intermediaries **SHALL** only support subscriptions with content='full-resource'.",SHALL,"PAS Client,PAS Payer",false,,,"",""
+hl7.fhir.us.davinci-pas_2.2.1,spec-64,https://hl7.org/fhir/us/davinci-pas/2.2.1/en/specification.html#ci-c-spec-64,Servers **MAY** reject updates and require that a new request is made by providing the appropriate X12 error code.,MAY,"PAS Client,PAS Payer",false,,,"",""
+hl7.fhir.us.davinci-pas_2.2.1,spec-69,https://hl7.org/fhir/us/davinci-pas/2.2.1/en/specification.html#ci-c-spec-69,Cancelled entries: item and supportingInfo entries that have been removed from the request **SHALL** include the infoCancelled modifier extension with a valueBoolean of `true` in the Claim.item.modifierExtension or Claim.supportingInfo.modifierExtension element.,SHALL,"PAS Client,PAS Payer",false,,,"",""
+hl7.fhir.us.davinci-pas_2.2.1,spec-70,https://hl7.org/fhir/us/davinci-pas/2.2.1/en/specification.html#ci-c-spec-70,Canceled items **SHALL** additionally contain a certificationType extension with a code of 3 (Cancel) in the Claim.item.extension element.,SHALL,"PAS Client,PAS Payer",false,,,"",""
+hl7.fhir.us.davinci-pas_2.2.1,spec-71,https://hl7.org/fhir/us/davinci-pas/2.2.1/en/specification.html#ci-c-spec-71,"Entries added, modified, or cancelled compared to the immediately prior version of the Claim referenced in the Claim.related.claim element **SHALL** contain a [infoChanged extension](StructureDefinition-extension-infoChanged.html) within the Claim.item or the Claim.supportingInfo element.",SHALL,"PAS Client,PAS Payer",false,,,"",""
+hl7.fhir.us.davinci-pas_2.2.1,spec-73,https://hl7.org/fhir/us/davinci-pas/2.2.1/en/specification.html#ci-c-spec-73,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,PAS Payer,false,,,"",""
+hl7.fhir.us.davinci-pas_2.2.1,use-1,https://hl7.org/fhir/us/davinci-pas/2.2.1/en/usecases.html#ci-c-use-1,The intermediary **SHALL** always exchange a FHIR bundle with the EHR (figure 2.3),SHALL,PAS Payer,false,,,"",""
+hl7.fhir.us.davinci-pas_2.2.1,use-2,https://hl7.org/fhir/us/davinci-pas/2.2.1/en/usecases.html#ci-c-use-2,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,PAS Payer,false,,,"",""
+hl7.fhir.us.davinci-pas_2.2.1,use-3,https://hl7.org/fhir/us/davinci-pas/2.2.1/en/usecases.html#ci-c-use-3,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,PAS Payer,false,,,"",""
+hl7.fhir.us.davinci-pas_2.2.1,use-6,https://hl7.org/fhir/us/davinci-pas/2.2.1/en/usecases.html#ci-c-use-6,"All exchanges **SHOULD** meet Federal and state regulations, including any HIPAA restrictions and restrictions on sensitive data.",SHOULD,"PAS Client,PAS Payer",false,,,"",""
+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,,,,"",""
+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
+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
+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:
+ - is capable of detecting when events covered by the requested SubscriptionTopic occur, and
+ - is willing to make a simple best effort attempt at delivering a notification for each occurrence of a matching event.",SHALL,Server,,,,1.03,davinci_pas_server_suite_v221-pas_server_v221_subscription_setup-subscriptions_r4_server_creation_response_conformance
+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,,,,"",""
+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,,,,"",""
+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,,,,"",""
+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,,,,"",""
+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,,,,"",""
+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,,,,"",""
+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.04, 2.3.2.02, 2.3.2.03","davinci_pas_server_suite_v221-pas_server_v221_subscription_setup-subscriptions_r4_server_handshake_conformance, davinci_pas_server_suite_v221-Group02-pas_server_v221_pended_use_case-Group02-pas_server_v221_subscription_notification_conformance_pended, davinci_pas_server_suite_v221-Group02-pas_server_v221_pended_use_case-Group02-pas_server_v221_subscription_notification_full_resource_conformance_pended"
+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. 
+- For the status resource (entry[0]) the request SHALL be filled out to match a request to the $status operation. 
+- 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.04, 2.3.2.02, 2.3.2.03","davinci_pas_server_suite_v221-pas_server_v221_subscription_setup-subscriptions_r4_server_handshake_conformance, davinci_pas_server_suite_v221-Group02-pas_server_v221_pended_use_case-Group02-pas_server_v221_subscription_notification_conformance_pended, davinci_pas_server_suite_v221-Group02-pas_server_v221_pended_use_case-Group02-pas_server_v221_subscription_notification_full_resource_conformance_pended"
+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,,,,"",""
+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
+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
+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,,,,"",""
+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,,,,"",""
+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
+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.03, 1.04","davinci_pas_server_suite_v221-pas_server_v221_subscription_setup-subscriptions_r4_server_creation_response_conformance, davinci_pas_server_suite_v221-pas_server_v221_subscription_setup-subscriptions_r4_server_handshake_conformance"
+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,,,,2.3.2.02,davinci_pas_server_suite_v221-Group02-pas_server_v221_pended_use_case-Group02-pas_server_v221_subscription_notification_conformance_pended
+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,,,,2.3.2.02,davinci_pas_server_suite_v221-Group02-pas_server_v221_pended_use_case-Group02-pas_server_v221_subscription_notification_conformance_pended
+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.04, 2.3.2.02, 2.3.2.03","davinci_pas_server_suite_v221-pas_server_v221_subscription_setup-subscriptions_r4_server_handshake_conformance, davinci_pas_server_suite_v221-Group02-pas_server_v221_pended_use_case-Group02-pas_server_v221_subscription_notification_conformance_pended, davinci_pas_server_suite_v221-Group02-pas_server_v221_pended_use_case-Group02-pas_server_v221_subscription_notification_full_resource_conformance_pended"
+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.03,davinci_pas_server_suite_v221-pas_server_v221_subscription_setup-subscriptions_r4_server_creation_response_conformance
+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,,,,"",""
+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,,,,"",""
+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,,,,"",""
+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
+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
+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_v221-Group02-pas_server_v221_pended_use_case-Group02-pas_server_v221_subscription_notification_full_resource_conformance_pended
+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,,,,"",""
+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
+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,,,,"",""
+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,,,,"",""
+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,,,,"",""
+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
+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,,,,"",""
+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,,,,2.3.2.03,davinci_pas_server_suite_v221-Group02-pas_server_v221_pended_use_case-Group02-pas_server_v221_subscription_notification_full_resource_conformance_pended
+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,,,,2.3.2.03,davinci_pas_server_suite_v221-Group02-pas_server_v221_pended_use_case-Group02-pas_server_v221_subscription_notification_full_resource_conformance_pended
+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,,,,2.3.2.03,davinci_pas_server_suite_v221-Group02-pas_server_v221_pended_use_case-Group02-pas_server_v221_subscription_notification_full_resource_conformance_pended
+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,,,,"",""
+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,,,,"",""
+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.03,davinci_pas_server_suite_v221-pas_server_v221_subscription_setup-subscriptions_r4_server_creation_response_conformance
+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,,,,"",""
+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_v221-Group02-pas_server_v221_pended_use_case-Group02-pas_server_v221_subscription_notification_full_resource_conformance_pended
+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,,,,"",""
+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_v221-Group02-pas_server_v221_pended_use_case-Group02-pas_server_v221_subscription_notification_full_resource_conformance_pended
+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,,,,"",""
+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,,,,"",""
+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
+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,,,,"",""
+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,,,,"",""
+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,,,,"",""
+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_v221-Group02-pas_server_v221_pended_use_case-Group02-pas_server_v221_subscription_notification_full_resource_conformance_pended
+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,,,,"",""
+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_v221-Group02-pas_server_v221_pended_use_case-Group02-pas_server_v221_subscription_notification_full_resource_conformance_pended
+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.04, 2.3.2.02, 2.3.2.03","davinci_pas_server_suite_v221-pas_server_v221_subscription_setup-subscriptions_r4_server_handshake_conformance, davinci_pas_server_suite_v221-Group02-pas_server_v221_pended_use_case-Group02-pas_server_v221_subscription_notification_conformance_pended, davinci_pas_server_suite_v221-Group02-pas_server_v221_pended_use_case-Group02-pas_server_v221_subscription_notification_full_resource_conformance_pended"
+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.04, 2.3.2.02, 2.3.2.03","davinci_pas_server_suite_v221-pas_server_v221_subscription_setup-subscriptions_r4_server_handshake_conformance, davinci_pas_server_suite_v221-Group02-pas_server_v221_pended_use_case-Group02-pas_server_v221_subscription_notification_conformance_pended, davinci_pas_server_suite_v221-Group02-pas_server_v221_pended_use_case-Group02-pas_server_v221_subscription_notification_full_resource_conformance_pended"
+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,,,,"",""
+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,,,,"",""
+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,,,,"",""
+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,,,,"",""
+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,,,,"",""
+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,,,,"",""
+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,,,,"",""
+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
+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,,,,"",""
+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
+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,,,,"",""
+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
+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,,,,"",""
+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,,,,"",""
+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,,,,"",""
+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,,,,"",""
+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,,,,"",""
+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,,,,"",""
+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
+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,,,,2.3.2.03,davinci_pas_server_suite_v221-Group02-pas_server_v221_pended_use_case-Group02-pas_server_v221_subscription_notification_full_resource_conformance_pended
+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,,,,"",""
+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,,,,"",""
+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
+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
+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,,,,"",""
+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,,,,"",""
+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,,,,"",""
+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,,,,"",""
+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,,,,"",""
+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,,,,"",""
+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,,,,"",""
+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,,,,"",""
+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,,,,"",""
+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,,,,"",""
+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
+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,,,,"",""
+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,,,,"",""
+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,,,,"",""
+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,,,,"",""
+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,,,,"",""
+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
+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,,,,"",""
+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,,,,"",""
+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,,,,"",""
+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,,,,"",""
+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,,,,"",""
+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,,,,"",""
+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,,,,"",""
+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
+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.02,davinci_pas_server_suite_v221-pas_server_v221_subscription_setup-subscriptions_r4_server_notification_delivery
+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,,,,"",""
+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,,,,"",""
+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,,,,"",""
+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,,,,"",""
+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.04, 2.3.2.02, 2.3.2.03","davinci_pas_server_suite_v221-pas_server_v221_subscription_setup-subscriptions_r4_server_handshake_conformance, davinci_pas_server_suite_v221-Group02-pas_server_v221_pended_use_case-Group02-pas_server_v221_subscription_notification_conformance_pended, davinci_pas_server_suite_v221-Group02-pas_server_v221_pended_use_case-Group02-pas_server_v221_subscription_notification_full_resource_conformance_pended"
+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.04, 2.3.2.02, 2.3.2.03","davinci_pas_server_suite_v221-pas_server_v221_subscription_setup-subscriptions_r4_server_handshake_conformance, davinci_pas_server_suite_v221-Group02-pas_server_v221_pended_use_case-Group02-pas_server_v221_subscription_notification_conformance_pended, davinci_pas_server_suite_v221-Group02-pas_server_v221_pended_use_case-Group02-pas_server_v221_subscription_notification_full_resource_conformance_pended"

data/lib/davinci_pas_test_kit/{custom_groups/v2.0.1/notification/pas_subscription_notification_test.rb → server/abstract_pas_subscription_notification_wait_test.rb}

@@ -1,33 +1,27 @@
-require_relative '../../../urls'
-
 module DaVinciPASTestKit
-  module DaVinciPASV201
-    # TODO: none of file name, class name, or ID match
-    class PasUpdateNotificationTest < Inferno::Test
-      include URLs
-      id :prior_auth_claim_response_update_notification_validation
-      title 'Server notifies the client that the pended claim was updated.'
-      description %(
+  class AbstractPASSubscriptionNotificationWaitTest < Inferno::Test
+    id :pas_server_subscription_notification_wait
+    title 'Server notifies the client that the pended claim was updated.'
+    description %(
         This test validates that the server can notify the client that a final
         decision has been made about a pended claim so that the client can query
-        for the details. This test depends on prior successful subscription creation in
+        for the details. This test depends on a successful subscription creation in
         Test Group **1 Subscription Setup**.
       )
-      verifies_requirements 'hl7.fhir.us.davinci-pas_2.0.1@141'
 
-      input :access_token,
-            title: 'Notification Access Token',
-            description: %(
+    input :access_token,
+          title: 'Notification Access Token',
+          description: %(
               An access token that the server under test will send to Inferno on notifications
               so that the request gets associated with this test session. The token must be
               provided as a `Bearer` token in the `Authorization` header of HTTP requests
               sent to Inferno.
             )
 
-      run do
-        wait(
-          identifier: "notification #{access_token}",
-          message: %(
+    run do
+      wait(
+        identifier: "notification #{access_token}",
+        message: %(
             Inferno has received a 'Pended' claim response indicating that a final decision has not yet been made on the
             prior authorization request.
 
@@ -38,8 +32,7 @@ module DaVinciPASTestKit
             attempted to send a notification, you may
             **[click here](#{resume_skip_url}?token=notification+#{access_token})** to skip this test._
           )
-        )
-      end
+      )
     end
   end
 end

data/lib/davinci_pas_test_kit/server/claim_inquire_operation_test.rb

@@ -0,0 +1,31 @@
+require_relative 'claim_operation_logic'
+
+module DaVinciPASTestKit
+  class ClaimInquireOperationTest < Inferno::Test
+    include ClaimOperationLogic
+
+    id :pas_claim_inquire_operation_test
+    title 'Submission of a claim to the $inquire operation succeeds'
+    description %(
+        Server SHALL support PAS Inquiry requests: a POST interaction to
+        the /Claim/$inquire endpoint.
+        This test submits a Prior Authorization Inquiry request to the server and verifies that a
+        response is returned with HTTP status 2XX.
+      )
+
+    input :pa_inquire_request_payload,
+          title: 'PAS Inquire Request Payload',
+          description: 'Insert Bundle to be sent for PAS Inquire Request',
+          type: 'textarea',
+          optional: true
+    input_order :server_endpoint, :smart_credentials
+
+    def operation
+      'inquire'
+    end
+
+    run do
+      run_operation_test(pa_inquire_request_payload)
+    end
+  end
+end

data/lib/davinci_pas_test_kit/server/claim_operation_logic.rb

@@ -0,0 +1,67 @@
+require_relative '../cross_suite/tags'
+
+module DaVinciPASTestKit
+  module ClaimOperationLogic
+    def operation_tag
+      DaVinciPASTestKit.const_get(:"#{operation.upcase}_TAG")
+    end
+
+    def use_case
+      config.options[:use_case]
+    end
+
+    # The workflow tag applied to (and used to reload) the request. Tests that run a single
+    # tagged submission per use case (e.g. Claim Updates) set an explicit `request_tag`; the
+    # standard workflow tests fall back to the use-case-derived `*_WORKFLOW_TAG`.
+    def use_case_tag
+      config.options[:request_tag].presence ||
+        DaVinciPASTestKit.const_get(:"#{use_case.upcase}_WORKFLOW_TAG")
+    end
+
+    def request_bundles(request_payload)
+      parsed_payload = JSON.parse(request_payload)
+      [parsed_payload].flatten.compact
+    end
+
+    def perform_operation(request_payload)
+      start_time = Time.now
+      request = fhir_operation("/Claim/$#{operation}", body: request_payload, tags: [use_case_tag, operation_tag])
+      response_time = Time.now - start_time
+
+      if operation == 'submit' && response_time > 15
+        warning %(
+              The server took more that 15 seconds to respond to the Prior Authorization
+              request.
+
+              Response Time: #{response_time}
+            )
+      end
+
+      request
+    end
+
+    def check_response_status_and_payload(request)
+      assert_response_status([200, 201])
+      assert_valid_json(request.response_body, "Server response to $#{operation} was not json.")
+      resource = FHIR.from_contents(request.response_body)
+      if config.options[:ig_version] == 'v2.2.1' && operation == 'inquire'
+        assert resource.resourceType == 'Parameters',
+               "Expected Parameters resource for v2.2.1 inquire response, but received #{resource.resourceType}"
+      else
+        assert_resource_type(:bundle, resource:)
+      end
+    end
+
+    def run_operation_test(request_payload)
+      skip_if request_payload.blank?, "No bundle request provided to perform the #{operation} operation"
+      assert_valid_json(request_payload,
+                        "Provide valid json to use for the $#{operation} during the #{use_case.titleize} workflow.")
+
+      requests_performed = request_bundles(request_payload).map do |bundle|
+        perform_operation(bundle)
+      end
+
+      requests_performed.each { |request| check_response_status_and_payload(request) }
+    end
+  end
+end

data/lib/davinci_pas_test_kit/server/claim_submit_operation_test.rb

@@ -0,0 +1,32 @@
+require_relative 'claim_operation_logic'
+
+module DaVinciPASTestKit
+  class ClaimSubmitOperationTest < Inferno::Test
+    include ClaimOperationLogic
+
+    id :pas_claim_submit_operation_test
+    title 'Submission of a claim to the $submit operation succeeds'
+    description %(
+        Server SHALL support PAS Submit requests: a POST interaction to
+        the /Claim/$submit endpoint.
+        This test submits a Prior Authorization Submit request to the server and verifies that a
+        response is returned with HTTP status 2XX.
+        The server SHOULD respond within 15 seconds.
+      )
+
+    input :pa_submit_request_payload,
+          title: 'PAS Submit Request Payload',
+          description: 'Insert Bundle to be sent for PAS Submit Request',
+          type: 'textarea',
+          optional: true
+    input_order :server_endpoint, :smart_credentials
+
+    def operation
+      'submit'
+    end
+
+    run do
+      run_operation_test(pa_submit_request_payload)
+    end
+  end
+end

data/lib/davinci_pas_test_kit/{generated/v2.0.1/beneficiary/server_submit_request_beneficiary_must_support_test.rb → server/generated/v2.0.1/beneficiary/server_inquire_request_must_support_beneficiary_test.rb}

@@ -1,13 +1,10 @@
-require_relative '../../../must_support_test'
-require_relative '../../../generator/group_metadata'
-require_relative '../../../tags'
+require_relative '../../../../cross_suite/must_support/must_support_test'
 
 module DaVinciPASTestKit
   module DaVinciPASV201
-    class ServerSubmitRequestBeneficiaryMustSupportTest < Inferno::Test
-      include DaVinciPASTestKit::MustSupportTest
-
-      title 'All must support elements for Profile PAS Beneficiary Patient are observed across all instances submitted'
+    class ServerInquireRequestMustSupportBeneficiaryTest < DaVinciPASTestKit::MustSupportTest
+      id :pas_server_v201_inquire_request_must_support_beneficiary
+      title 'All must support elements for profile PAS Beneficiary Patient are observed on $inquire requests'
       description %(
         
         **USER INPUT VALIDATION**: This test validates input provided by the user instead of the system under test. Errors encountered will be treated as a skip instead of a failure.
@@ -49,34 +46,16 @@ module DaVinciPASTestKit
         * Patient.telecom.value
       )
 
-      id :pas_server_submit_request_v201_beneficiary_must_support_test
-
-      def resource_type
-        'Patient'
-      end
-
-      def user_input_validation
-        true
-      end
-
-      def self.metadata
-        @metadata ||= Generator::GroupMetadata.new(YAML.load_file(File.join(__dir__, 'metadata.yml'), aliases: true))
-      end
-
-      def scratch_resources
-        # The scratch key in MS test should be the same as the scratch key in the validation test for a given profile.
-        scratch[:submit_request_resources] ||= {}
-      end
-
-      def resources_of_interest
-        collection = tagged_resources(SUBMIT_TAG).presence || all_scratch_resources
-        collection.select { |res| res.resourceType == resource_type }
-      end
-
-      run do
-        perform_must_support_test(resources_of_interest)
-        validate_must_support(user_input_validation)
-      end
+      config(
+        options: {
+          resource_type: 'Patient',
+          profile_key: 'beneficiary',
+          user_input_validation: true,
+          ig_version: 'v2.0.1',
+          type: 'request',
+          operation: 'inquire'
+        }
+      )
     end
   end
 end