carin_for_blue_button_test_kit 0.15.1 → 0.15.3

data/lib/carin_for_blue_button_test_kit/requirements/generated/c4bb_v110_requirements_coverage.csv

@@ -0,0 +1 @@
+Req Set,ID,URL,Requirement,Conformance,Actors,Conditionality,Not Tested Reason,Not Tested Details,CARIN IG for Blue Button® v1.1.0 Short ID(s),CARIN IG for Blue Button® v1.1.0 Full ID(s)

data/lib/carin_for_blue_button_test_kit/requirements/generated/c4bb_v200_client_requirements_coverage.csv

@@ -0,0 +1,47 @@
+Req Set,ID,URL,Requirement,Conformance,Actors,Conditionality,Not Tested Reason,Not Tested Details,CARIN IG for Blue Button® v2.0.0 Client Test Suite Short ID(s),CARIN IG for Blue Button® v2.0.0 Client Test Suite Full ID(s)
+hl7.fhir.us.carin-bb_2.0.0,1,https://hl7.org/fhir/us/carin-bb/STU2/Background.html#smart-application-launch,The CARIN IG for Blue Button® requires the use of the SMART App Launch Framework’s standalone launch sequence as it will clarify that applications maintain a patient context for the duration of the connection.,SHALL,"Health Plan,Consumer",false,,,3.01,c4bb_v200_client-c4bb_client_v200_visual_inspection_and_attestation-c4bb_authentication
+hl7.fhir.us.carin-bb_2.0.0,3,http://hl7.org/fhir/us/carin-bb/STU2/Conformance_Requirements.html#must-support,[*Must Support* on profile data elements means] Consumer App actors SHALL be capable of processing resource instances containing the data elements without generating an error or causing the application to fail.,SHALL,Consumer,false,,,2.8.01,c4bb_v200_client-c4bb_data_access-c4bb_client_attestation_test_group-client_claims_data_attestation
+hl7.fhir.us.carin-bb_2.0.0,4,http://hl7.org/fhir/us/carin-bb/STU2/Conformance_Requirements.html#must-support,[*Must Support* on profile data elements means] Consumer App actors SHALL be capable of displaying the data elements for human use.,SHALL,Consumer,false,,,3.02,c4bb_v200_client-c4bb_client_v200_visual_inspection_and_attestation-c4bb_must_support_display
+hl7.fhir.us.carin-bb_2.0.0,6,http://hl7.org/fhir/us/carin-bb/STU2/Conformance_Requirements.html#must-support,"[*Must Support* on profile data elements means w]hen querying Health Plan API actors, Consumer App actors SHALL interpret missing data elements within resource instances as data not present in the Health Plan API actors system.",SHALL,Consumer,false,,,3.03,c4bb_v200_client-c4bb_client_v200_visual_inspection_and_attestation-c4bb_must_support_missing
+hl7.fhir.us.carin-bb_2.0.0,8,http://hl7.org/fhir/us/carin-bb/STU2/Conformance_Requirements.html#must-support,[*Must Support* on profile data elements means] Consumer App actors SHALL be able to process resource instances containing data elements asserting missing information.,SHALL,Consumer,false,,,3.04,c4bb_v200_client-c4bb_client_v200_visual_inspection_and_attestation-c4bb_must_support_absent_reason
+hl7.fhir.us.carin-bb_2.0.0,13,http://hl7.org/fhir/us/carin-bb/STU2/Conformance_Requirements.html#conformance-to-us-core-profiles,Any actor acting [as] a FHIR Client in this IG SHALL … [b]e able to process and retain all profile data elements that have a minimum cardinality >= 1 and/or flagged as Must Support as defined by that profiles StructureDefinition.,SHALL,Consumer,false,,,2.8.01,c4bb_v200_client-c4bb_data_access-c4bb_client_attestation_test_group-client_claims_data_attestation
+hl7.fhir.us.carin-bb_2.0.0,14,http://hl7.org/fhir/us/carin-bb/STU2/Conformance_Requirements.html#conformance-to-us-core-profiles,Any actor acting [as] a FHIR Client in this IG SHALL … [c]onform to the US Core Client Capability Statement expectations for that profiles type.,SHALL,Consumer,false,,,"2.2.02, 2.3.02, 2.4.02, 2.5.02, 2.6.02, 2.7.06","c4bb_v200_client-c4bb_data_access-c4bb_patient_profile_test_group-patient_required_searches, c4bb_v200_client-c4bb_data_access-c4bb_coverage_profile_test_group-coverage_required_searches, c4bb_v200_client-c4bb_data_access-c4bb_organization_profile_test_group-organization_required_searches, c4bb_v200_client-c4bb_data_access-c4bb_practitioner_profile_test_group-practitioner_required_searches, c4bb_v200_client-c4bb_data_access-c4bb_relatedperson_profile_test_group-relatedperson_required_searches, c4bb_v200_client-c4bb_data_access-c4bb_explanationofbenefit_profiles_test_group-eob_required_searches"
+hl7.fhir.us.carin-bb_2.0.0,16,http://hl7.org/fhir/us/carin-bb/STU2/Conformance_Requirements.html#profiling-constraints,"If a Health Plan API includes additional information, there SHALL be no expectation that client applications support the data in any way in order to be conformant with this specification.",SHALL NOT,Consumer,true,,,"",""
+hl7.fhir.us.carin-bb_2.0.0,48,http://hl7.org/fhir/us/carin-bb/STU2/Security_And_Privacy_Considerations.html#general-considerations,"Members need to be able to direct the communication of this information through authenticated, authorized, and secure channels.",SHALL,"Health Plan,Consumer",false,,,3.01,c4bb_v200_client-c4bb_client_v200_visual_inspection_and_attestation-c4bb_authentication
+hl7.fhir.us.carin-bb_2.0.0,49,http://hl7.org/fhir/us/carin-bb/STU2/Security_And_Privacy_Considerations.html#general-considerations,Exchange of this information needs to be protected with proper security and privacy protections to avoid malicious or unintentional exposure of such information.,SHALL,"Health Plan,Consumer",false,,,"",""
+hl7.fhir.us.carin-bb_2.0.0,50,http://hl7.org/fhir/us/carin-bb/STU2/Security_And_Privacy_Considerations.html#general-considerations,All consumer-directed payer data exchanges must be appropriately secured in transit and access limited only to authorized individuals.,SHALL,"Health Plan,Consumer",false,,,"",""
+hl7.fhir.us.carin-bb_2.0.0,52,http://hl7.org/fhir/us/carin-bb/STU2/Security_And_Privacy_Considerations.html#securityprivacy-related-technologies-including-explicit-consent-and-security-labels,"1. While past ONC regulations did have optional rules for data labeling and consent directives, as of May 2020, ONC has elected to not establish rules for either data labeling and consent directives as part of the Final Rule for the 21st Century Cures Act.
+2. At present there is no explicit regulatory requirement for the use of these technologies in conjunction with this guide.
+3. However, to meet the statutes, regulations, and guiding principles above, consent directives and security labels MAY be considered and used.
+4. Organizations which plan to take advantage of these additional capabilities are responsible for negotiating support for these mechanisms between trading partners. The FHIR implementation guide defining the recommended standard is the FHIR Data Segmentation for Privacy IG.",MAY,"Health Plan,Consumer",false,,,"",""
+hl7.fhir.us.carin-bb_2.0.0,53,http://hl7.org/fhir/us/carin-bb/STU2/Security_And_Privacy_Considerations.html#security-considerations-and-guidance,"All implementers of the CARIN Consumer-Directed Payer Data Exchange Implementation Guide (IG) should follow the FHIR Security guidance, Security and Privacy Module, and the FHIR Implementer’s Safety Checklist guidance as defined in the FHIR standard where applicable and not otherwise superseded by this section of the IG.",SHOULD,"Health Plan,Consumer",false,,,"",""
+hl7.fhir.us.carin-bb_2.0.0,54,http://hl7.org/fhir/us/carin-bb/STU2/Security_And_Privacy_Considerations.html#exchange-security,The exchange of information SHOULD use the current version...of Transport Level Security (TLS) as specified by the current release of NIST guidelines (SP 800-52).,SHOULD,"Health Plan,Consumer",false,,,"",""
+hl7.fhir.us.carin-bb_2.0.0,56,http://hl7.org/fhir/us/carin-bb/STU2/Security_And_Privacy_Considerations.html#exchange-security,Implementers of this Implementation Guide SHOULD support SMART on FHIR Authorization best practices Transport Security section.,SHOULD,"Health Plan,Consumer",false,,,"",""
+hl7.fhir.us.carin-bb_2.0.0,59,http://hl7.org/fhir/us/carin-bb/STU2/Security_And_Privacy_Considerations.html#authentication-and-authorization-requirements,Implementations SHOULD consider the SMART on FHIR Best Practices in Authorization found [here](https://docs.smarthealthit.org/authorization/best-practices/).,SHOULD,"Health Plan,Consumer",false,,,"",""
+hl7.fhir.us.carin-bb_2.0.0,83,http://hl7.org/fhir/us/carin-bb/STU2/Security_And_Privacy_Considerations.html#authentication-and-authorization-requirements,"If UDAP is supported, then all Server systems and Client applications that can protect private cryptographic keys and all systems of record SHOULD support UDAP JWT-Based Consumer Authentication for the authentication of client applications using asymmetric cryptography.",SHOULD,"Health Plan,Consumer",true,,,"",""
+hl7.fhir.us.carin-bb_2.0.0,90,http://hl7.org/fhir/us/carin-bb/STU2/CapabilityStatement-c4bb.html#root,Apps will use the meta.lastUpdated values to determine if the reference resources are as of the current date or date of service.,SHALL,Consumer,false,,,3.05,c4bb_v200_client-c4bb_client_v200_visual_inspection_and_attestation-c4bb_last_updated
+hl7.fhir.us.carin-bb_2.0.0,94,http://hl7.org/fhir/us/carin-bb/STU2/CapabilityStatement-c4bb.html#title,Apps will use the meta.lastUpdated values to determine if the reference resources are as of the current date or date of service.,SHALL,Consumer,false,,,3.05,c4bb_v200_client-c4bb_client_v200_visual_inspection_and_attestation-c4bb_last_updated
+hl7.fhir.us.carin-bb_2.0.0,107,http://hl7.org/fhir/us/carin-bb/STU2/CapabilityStatement-c4bb.html#explanationofbenefit,Clients MAY request referenced resources as part of an EOB search (by supplying the _include parameter) or directly using read or vread.,MAY,Consumer,false,,,"",""
+hl7.fhir.us.carin-bb_2.0.0,109,http://hl7.org/fhir/us/carin-bb/STU2/CapabilityStatement-c4bb.html#explanationofbenefit,"“:iterate"" should be used if you request to include Coverage:payor in the EOB response bundle, e.g. GET [base]/ExplanationOfBenefit?_id[parameter=value]&_include=ExplanationOfBenefit:coverage&_include:iterate=Coverage:payor.",SHOULD,Consumer,false,,,"",""
+hl7.fhir.us.carin-bb_2.0.0,121,http://hl7.org/fhir/us/carin-bb/STU2/StructureDefinition-C4BB-ExplanationOfBenefit.html#notes-on-fields,.supportinginfo.sequence rule:  client app implementations should look-up supportingInfo elements based on category values instead of sequence values,SHOULD,Consumer,false,,,"",""
+hl7.fhir.us.carin-bb_2.0.0,122,http://hl7.org/fhir/us/carin-bb/STU2/StructureDefinition-C4BB-ExplanationOfBenefit.html#notes-on-fields,".careTeam.sequence rule:
+…
+ Client app implementations SHOULD NOT assign any significance to the sequence values.",SHOULD NOT,Consumer,false,,,"",""
+hl7.fhir.us.carin-bb_2.0.0,137,http://hl7.org/fhir/us/carin-bb/STU2/StructureDefinition-C4BB-ExplanationOfBenefit-Inpatient-Institutional.html#notes-on-fields,".diagnosis.sequence rule:  
+…
+Client app implementations should not assign any significance to the sequence values.",SHOULD NOT,Consumer,false,,,"",""
+hl7.fhir.us.carin-bb_2.0.0,138,http://hl7.org/fhir/us/carin-bb/STU2/StructureDefinition-C4BB-ExplanationOfBenefit-Inpatient-Institutional.html#notes-on-fields,".diagnosis.sequence rule:  
+…
+Client app implementations should use the values of diagnosis.type to identify primary, secondary, etc.",SHOULD,Consumer,false,,,"",""
+hl7.fhir.us.carin-bb_2.0.0,139,http://hl7.org/fhir/us/carin-bb/STU2/StructureDefinition-C4BB-ExplanationOfBenefit-Inpatient-Institutional.html#notes-on-fields,".procedure.sequence rule: 
+…
+Client app implementations should not assign any significance to the sequence values.",SHOULD NOT,Consumer,false,,,"",""
+hl7.fhir.us.carin-bb_2.0.0,140,http://hl7.org/fhir/us/carin-bb/STU2/StructureDefinition-C4BB-ExplanationOfBenefit-Inpatient-Institutional.html#notes-on-fields,".procedure.sequence rule: 
+…
+Client app implementations should use the values of procedure.type to identify primary and secondary procedures",SHOULD,Consumer,false,,,"",""
+hl7.fhir.us.carin-bb_2.0.0,147,http://hl7.org/fhir/us/carin-bb/STU2/StructureDefinition-C4BB-ExplanationOfBenefit-Oral.html#notes-on-fields,".diagnosis.sequence rule:  diagnosis.sequence values do not necessarily indicate any order in which the diagnosis was reported or identified.  Client app implementations should not assign any significance to the sequence values.  Client app implementations should use the values of diagnosis.type to identify primary, secondary, etc.",SHOULD NOT,Consumer,false,,,"",""
+hl7.fhir.us.carin-bb_2.0.0,166,https://hl7.org/fhir/us/carin-bb/STU2/StructureDefinition-C4BB-ExplanationOfBenefit-Professional-NonClinician.html#notes-on-fields,.diagnosis.sequence rule:  diagnosis.sequence values do not necessarily indicate any order in which the diagnosis was reported or identified.  Client app implementations should not assign any significance to the sequence values.,SHOULD NOT,Consumer,false,,,"",""
+hl7.fhir.us.carin-bb_2.0.0,167,https://hl7.org/fhir/us/carin-bb/STU2/StructureDefinition-C4BB-ExplanationOfBenefit-Professional-NonClinician.html#notes-on-fields,".diagnosis.sequence rule:  diagnosis.sequence values do not necessarily indicate any order in which the diagnosis was reported or identified.  ...Client app implementations should use the values of diagnosis.type to identify primary, secondary, etc.",SHOULD,Consumer,false,,,"",""
+hl7.fhir.us.carin-bb_2.0.0,180,https://hl7.org/fhir/us/carin-bb/STU2/StructureDefinition-C4BB-Organization.html,.meta.lastUpdated: ... Apps will use the meta.lastUpdated value to determine if the Reference resources are as of the current date or date of service.,SHALL,Consumer,false,,,3.05,c4bb_v200_client-c4bb_client_v200_visual_inspection_and_attestation-c4bb_last_updated
+hl7.fhir.us.carin-bb_2.0.0,184,https://hl7.org/fhir/us/carin-bb/STU2/StructureDefinition-C4BB-Patient.html#notes-on-fields,.meta.lastUpdated: ... Apps will use the meta.lastUpdated value to determine if the Reference resources are as of the current date or date of service.,SHALL,Consumer,false,,,3.05,c4bb_v200_client-c4bb_client_v200_visual_inspection_and_attestation-c4bb_last_updated
+hl7.fhir.us.carin-bb_2.0.0,188,https://hl7.org/fhir/us/carin-bb/STU2/StructureDefinition-C4BB-Practitioner.html#notes-on-fields,.meta.lastUpdated: … Apps will use the meta.lastUpdated value to determine if the Reference resources are as of the current date or date of service.,SHALL,Consumer,false,,,3.05,c4bb_v200_client-c4bb_client_v200_visual_inspection_and_attestation-c4bb_last_updated