RubyGems - cancer_pathology_data_sharing_test_kit - Versions diffs - 0.10.0 → 0.10.1 - Mend

cancer_pathology_data_sharing_test_kit 0.10.0 → 0.10.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (16) hide show

checksums.yaml CHANGED Viewed

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: d3a6837db3c287966e32bd0b94d0e45b541b4d81829f4607b97cc99004215848
-  data.tar.gz: c29bb684be8f407a2aa0ccdabed2c858275b4f5b4d66ce060831772ddc780476
+  metadata.gz: 0a39bb5d0c23ebd530d1a30b2cde6ba488278a9df01a92c651b7f33b062e1add
+  data.tar.gz: '052906955093dd6ce6aff4a2fd3ddb9bc7c2c91d7322ef1d07751a36077a88e9'
 SHA512:
-  metadata.gz: 5be9ccb7bfff6621de1720904a4434a93b1a1665a9cdc9f296f9c4bbb79078189d91fde937d3ec957d291cf1b312e9182ed5c80995907e2c1e78618ef27a79b7
-  data.tar.gz: 3551b2d3baf1c1c7287b30ad18e0227515ac0c99d3073ee13bdbdfcb06c96b7f9353d0fa9256a7ffce6dcf9b59e310166829ff4c066e85e9c6c842e1fdcfbdf3
+  metadata.gz: 85a363e25bed54822a593cf60586565ac099c901f52ea5296f850ce499bc566fc4630c11dc95fb89a136a0ecd55afd2208ed737abdc189702352cb99cdde6ed4
+  data.tar.gz: 3c6e10c61fdf155a25a3592ca017b2a8a48db08610136ff248c56de9ad41b365e1fe9b2ba34cf33e1bd045e684476b734754855d29d0f8db2ba4a73adda38dfe

data/lib/cancer_pathology_data_sharing_test_kit/docs/data_access_suite_description.md CHANGED Viewed

@@ -1,16 +1,14 @@
 ## Overview
-The Cancer Pathology Data Sharing (CPDS) Data Access Test Suite verifies the ability of
-clinical systems to make [US Core](http://hl7.org/fhir/us/core/STU5.0.1/)
-data accessible to other systems per the
-STU 1.0.1 version of the HL7® FHIR® [Cancer Pathology Data Sharing IG](https://hl7.org/fhir/us/cancer-reporting/STU1.0.1/).
+The Cancer Pathology Data Sharing (CPDS) Data Access Test Suite validates that clinical systems implement the required FHIR APIs for sharing cancer pathology data as specified in the STU 1.0.1 version of the [Cancer Pathology Data Sharing IG](https://hl7.org/fhir/us/cancer-reporting/STU1.0.1/). This suite ensures systems can properly expose standardized pathology data through [US Core](http://hl7.org/fhir/us/core/STU5.0.1/) APIs.
 ## Scope
+The CPDS IG mandates specific API capabilities for both [Laboratory Information Systems (LIS)](https://hl7.org/fhir/us/cancer-reporting/STU1.0.1/CapabilityStatement-pathology-lab-information-system.html) and [Electronic Health Records (EHR)](https://hl7.org/fhir/us/cancer-reporting/STU1.0.1/CapabilityStatement-central-cancer-registry-reporting-ehr-pathology.html). This test suite validates:
-The CPDS IG requires that both [Laboratory Information System (LIS)](https://hl7.org/fhir/us/cancer-reporting/STU1.0.1/CapabilityStatement-pathology-lab-information-system.html)
-and [Electronic Health Record (EHR)](https://hl7.org/fhir/us/cancer-reporting/STU1.0.1/CapabilityStatement-central-cancer-registry-reporting-ehr-pathology.html)
-systems support "searching and retrieval of resources using US Core APIs". This test suite
-verifies that a system exposes the full list of US Core v5 APIs and profiles.
+- Implementation of US Core STU 5 search and read operations
+- Support for required search parameters and combinations
+- Proper population of must-support elements
+- Correct profile conformance for returned resources
+- Resolution of referenced resources
 Other capabilities that the CPDS IG requires of these systems are currently out of scope
 for this test suite, including
@@ -80,4 +78,4 @@ This test suite currently provides only one option for testers to adjust the req
 so that the system under test can identify Inferno as the requestor. If the **Access Token** input is populated,
 the provided value will be placed in the HTTP `Authorization` header with the prefix `Bearer `.
 Support for Inferno to obtain bearer tokens using SMART on FHIR workflows or other auth schemes may be added
-in the future based on community feedback.
+in the future based on community feedback.

data/lib/cancer_pathology_data_sharing_test_kit/docs/report_generation_suite_description.md CHANGED Viewed

@@ -1,13 +1,13 @@
 ## Overview
-The Cancer Pathology Data Sharing Report Generation Test Suite verifies the conformance of clinical systems,
-including laboratory information systems (LISs) & electronic health records (EHRs) to the report generation
-requirements in the STU 1.0.1 version of the HL7® FHIR®
-[Cancer Pathology Data Sharing (CPDS) IG](https://hl7.org/fhir/us/cancer-reporting/STU1.0.1/).
+The Cancer Pathology Data Sharing Report Generation Test Suite validates that clinical systems (Laboratory Information Systems and Electronic Health Records) can create pathology reports that conform to the STU 1.0.1 version of the HL7® FHIR® [Cancer Pathology Data Sharing (CPDS) IG](https://hl7.org/fhir/us/cancer-reporting/STU1.0.1/). This suite ensures systems can properly structure and encode pathology data for cancer registry reporting.
 ## Scope
-This test suite focuses on the report creation portion of a system's role in submitting pathology reports to
-central cancer registries. Specifically, these tests verify that a system can produce a set of comformant
-and complete [Pathology Cancer Exchange Bundle(s)](https://hl7.org/fhir/us/cancer-reporting/STU1.0.1/StructureDefinition-us-pathology-exchange-bundle.html).
+This test suite validates the creation of standardized pathology reports for cancer registry submission. It verifies that systems can generate [Pathology Cancer Exchange Bundles](https://hl7.org/fhir/us/cancer-reporting/STU1.0.1/StructureDefinition-us-pathology-exchange-bundle.html) that include all required components:
+- Patient demographics (US Core Patient)
+- Encounter details (US Core Encounter)
+- Diagnostic findings (US Pathology Diagnostic Report)
+- Specimen information (US Pathology Specimen)
+- Service requests and practitioner details
 The IG defines other capabilities of clinical systems that are currently out of scope for this suite, including:
 - The gathering of report content from other systems, if necessary.
@@ -115,4 +115,4 @@ of this test suite may update this approach based on community feedback and IG u
 The CPDS IG refers to the MedMorph framework for submission which uses FHIR Messaging. Currently, this test suite
 does not support submission of reports using this standards-based approach and instead requires manual provision of
 the reports using Inferno inputs. Future versions may include support for FHIR Messaging or other approaches
-to submission.
+to submission.

data/lib/cancer_pathology_data_sharing_test_kit/report_generation_suite/data_absent/data_absent_reason_code_system.rb CHANGED Viewed

@@ -3,11 +3,26 @@ module CancerPathologyDataSharingTestKit
     id :cpds_data_absent_reason_code_system
     title 'Server represents missing data with the DataAbsentReason CodeSystem'
     description %(
-            For coded data elements with example, preferred, or extensible binding
-            strengths to ValueSets which do not include an appropriate "unknown"
-            code, servers SHALL use the "unknown" code from the DataAbsentReason
-            CodeSystem.
-        )
+      For coded data elements (fields bound to value sets), the CPDS IG specifies how to handle missing data:
+      Primary Approach:
+      * If the value set includes an appropriate "unknown" code, that code SHALL be used
+      * Example: Using SNOMED CT "unknown" code for fields bound to SNOMED CT value sets
+      Alternative Approach:
+      * For value sets with example, preferred, or extensible binding strengths that do not include
+        an appropriate "unknown" code, servers SHALL use the "unknown" code from the
+        [DataAbsentReason CodeSystem](http://hl7.org/fhir/R4/codesystem-data-absent-reason.html)
+      * This ensures consistent representation of unknown values across all coded fields
+      This test validates that when appropriate "unknown" codes are not available in the bound
+      value sets, the system correctly uses the DataAbsentReason CodeSystem's "unknown" code
+      to represent missing data in coded fields.
+      Note: This is different from the DataAbsentReason Extension, which is used for non-coded
+      fields. The DataAbsentReason CodeSystem is specifically for coded fields where the bound
+      value set lacks an appropriate "unknown" code.
+    )
     input :dar_code_found,
           title: 'Data Absent Reason CodeSystem Found',
           locked: true,

data/lib/cancer_pathology_data_sharing_test_kit/report_generation_suite/data_absent/data_absent_reason_extension.rb CHANGED Viewed

@@ -1,11 +1,33 @@
 module CancerPathologyDataSharingTestKit
   class DataAbsentReasonExtension < Inferno::Test
     id :cpds_data_absent_reason_extension
-    title 'Server represents missing data with the DataAbsentReason Extension'
+    title 'DataAbsentReason Extension Implementation for Non-Coded Fields'
     description %(
-            For non-coded data elements, servers SHALL use the DataAbsentReason
-            Extension to represent missing data in a required field
-        )
+      The Cancer Pathology Data Sharing IG requires specific handling of missing data in required fields.
+      For non-coded fields that are required but the data is not available, systems SHALL use the
+      [DataAbsentReason Extension](http://hl7.org/fhir/StructureDefinition/data-absent-reason) to explicitly
+      indicate why the data is not present.
+      The extension must be used with one of these values to indicate why data is missing:
+      * unknown - The value is not known and there is no expectation that it will be known
+      * asked-unknown - The source was queried but does not know the value
+      * temp-unknown - The value is not known at this time but is expected to be known later
+      * not-asked - The source was not asked for the value
+      * asked-declined - The source was asked for the value but declined to answer
+      * masked - The information is available but not provided due to security, privacy, or other reasons
+      * not-applicable - The field is not applicable to this concept
+      * unsupported - The source system does not support this field
+      * as-text - The information is available but only as text
+      * error - The information is not available due to an error
+      * not-performed - The task/step associated with this element was not performed
+      * not-permitted - The user does not have the necessary rights to view this information
+      This test validates that the system properly implements this extension pattern when representing
+      missing non-coded data elements, as specified in the [CPDS Missing Data Guidance](https://hl7.org/fhir/us/cancer-reporting/STU1.0.1/specification.html#must-support-and-missing-data).
+      For coded fields (those bound to value sets), systems should instead use the appropriate "unknown" code
+      from the value set rather than the DataAbsentReason extension.
+    )
     input :dar_extension_found,
           title: 'Data Absent Reason Extension Found',
           locked: true,

data/lib/cancer_pathology_data_sharing_test_kit/report_generation_suite/data_absent/sending_hide_missing.rb CHANGED Viewed

@@ -3,9 +3,26 @@ module CancerPathologyDataSharingTestKit
     id :cpds_data_absent_sending_hide_missing
     title 'Sender does not send data element(s) with missing information'
     description %(
-        In situations where information on a particular data element is not present, the Sender SHALL NOT include the data element
-       in the resource instance if the cardinality is 0..n.
-      )
+      The CPDS IG provides specific guidance for handling optional data elements (those with cardinality 0..n)
+      when the information is not available. This requirement helps reduce message size and processing overhead
+      while maintaining semantic clarity.
+      Key Requirements:
+      * When information for an optional data element is not available, the Sender SHALL NOT include
+        the empty element in the resource instance
+      * This applies only to elements with cardinality 0..n (optional elements)
+      * For required elements (cardinality 1..n or 1..1), use the appropriate missing data pattern instead:
+        * DataAbsentReason Extension for non-coded fields
+        * "Unknown" codes from value sets for coded fields
+      Examples:
+      * DO NOT include an empty 'note' element if there are no notes
+      * DO NOT include an empty 'identifier' array if there are no identifiers
+      * DO NOT include null or empty string values in optional elements
+      This test verifies that the system correctly omits optional elements when their data is not available,
+      rather than including them with empty or null values.
+    )
     run do
       identifier = SecureRandom.hex(32)

data/lib/cancer_pathology_data_sharing_test_kit/report_generation_suite/data_absent_group.rb CHANGED Viewed

@@ -5,18 +5,35 @@ require_relative 'data_absent/data_absent_reason_code_system'
 module CancerPathologyDataSharingTestKit
   class DataAbsentGroup < Inferno::TestGroup
     id :cpds_data_absent_reason
-    title 'Missing Data Tests'
-    short_description 'Verify that the server is capable of representing missing data.'
+    title 'Cancer Pathology Missing Data Representation'
+    short_description 'Verify compliance with CPDS IG missing data requirements.'
     description %(
-      The [CPDS Missing Data
-      Guidance](https://hl7.org/fhir/us/cancer-reporting/STU1.0.1/specification.html#must-support-and-missing-data)
-      gives instructions on how to represent various types of missing data.
-      In the previous resource tests, each resource returned from the server was
-      checked for the presence of missing data. These tests will pass if the
-      specified method of representing missing data was observed in the earlier
-      tests.
+      The Cancer Pathology Data Sharing IG provides specific [Missing Data Guidance](https://hl7.org/fhir/us/cancer-reporting/STU1.0.1/specification.html#must-support-and-missing-data)
+      for handling required data elements that may not be available. The IG defines different approaches based on the type of field:
+      For Non-Coded Fields:
+      * Systems SHALL use the DataAbsentReason Extension to explicitly indicate why required data is missing
+      * The extension must use standardized codes like 'unknown', 'asked-unknown', 'temp-unknown', etc.
+      * This applies to string, dateTime, and other non-coded fields
+      For Coded Fields (bound to ValueSets):
+      * Systems SHALL use the appropriate "unknown" code from the specified value set
+      * The DataAbsentReason Extension should NOT be used for these fields
+      * Example: Using "unknown" SNOMED CT code for a field bound to SNOMED CT concepts
+      Display Requirements:
+      * Systems SHALL support the ability to hide missing data in displays
+      * This helps reduce visual clutter while still maintaining the complete data
+      * Display preferences should be configurable by users
+      These tests validate that resources properly implement all three aspects of missing data handling:
+      1. Correct use of DataAbsentReason Extension for non-coded fields
+      2. Proper use of "unknown" codes from value sets for coded fields
+      3. Support for configurable display of missing data
+      Each resource previously tested has been analyzed for correct implementation of these missing data patterns
+      as specified in the IG.
     )
     run_as_group

data/lib/cancer_pathology_data_sharing_test_kit/report_generation_suite/exchange_bundle_group.rb CHANGED Viewed

@@ -23,38 +23,72 @@ module CancerPathologyDataSharingTestKit
     description %(
       # Background
-      Theses tests verify that the system under test can generate conformant and complete cancer pathology reports
-      following the requirements in the [Cancer Pathology Exchange Bundle profile](https://hl7.org/fhir/us/cancer-reporting/STU1.0.1/StructureDefinition-us-pathology-exchange-bundle.html).
-      The tester will provide a list of Bundles generated by the system under test in the **Cancer Reports** input.
-      Inferno will verify the conformance of each report and that the set of reports contains examples
-      of all entry slices and each element that the Bundle profile and referenced profiles indicate must be supported.
+      These tests verify that the system under test can generate conformant and complete cancer pathology reports
+      according to the [Cancer Pathology Data Sharing Implementation Guide](https://hl7.org/fhir/us/cancer-reporting/STU1.0.1/).
+      The tests focus on validating the [Cancer Pathology Exchange Bundle profile](https://hl7.org/fhir/us/cancer-reporting/STU1.0.1/StructureDefinition-us-pathology-exchange-bundle.html)
+      and all its required components.
       # Testing Methodology
-      The provided Bundles are parsed and the individual resources within them are separated out
-      and assigned a target profile based on their resource type.
+      ## Report Submission
+      The tester provides one or more cancer pathology report bundles through the **Cancer Reports** input.
+      Each bundle should represent a complete pathology report ready for submission to a cancer registry.
+      ## Bundle Structure Validation
+      Each bundle is validated to ensure:
+      * Type is set to "transaction"
+      * Timestamp is present indicating when the bundle was created
+      * All required entries are present with correct cardinality
+      * Resources conform to their required profiles
+      * References between resources are valid and resolvable
+      ## Required Resources
+      Each cancer pathology report bundle must contain:
+      * Patient Demographics (1..1)
+        * Must conform to [US Core Patient](http://hl7.org/fhir/us/core/STU5.0.1/StructureDefinition-us-core-patient.html)
+        * Contains essential patient identification and demographic data
+      * Encounter Information (1..1)
+        * Must conform to [US Core Encounter](http://hl7.org/fhir/us/core/STU5.0.1/StructureDefinition-us-core-encounter.html)
+        * Documents the context of the pathology examination
+      * Diagnostic Report (1..1)
+        * Must conform to [US Pathology Diagnostic Report](https://hl7.org/fhir/us/cancer-reporting/STU1.0.1/StructureDefinition-us-pathology-diagnostic-report.html)
+        * Contains the core pathology findings and interpretations
+      * Specimen Details (1..*)
+        * Must conform to [US Pathology Specimen](https://hl7.org/fhir/us/cancer-reporting/STU1.0.1/StructureDefinition-us-pathology-specimen.html)
+        * Describes the specimens examined
+      * Service Request (1..1)
+        * Must conform to [Cancer Pathology Service Request](https://hl7.org/fhir/us/cancer-reporting/STU1.0.1/StructureDefinition-us-pathology-service-request.html)
+        * Documents the original order/request
+      * Organization Information (1..*)
+        * Must conform to [US Core Organization](http://hl7.org/fhir/us/core/STU5.0.1/StructureDefinition-us-core-organization.html)
+        * Identifies the facilities involved
+      * Provider Information
+        * Practitioners (1..*)
+          * Must conform to [US Core Practitioner](http://hl7.org/fhir/us/core/STU5.0.1/StructureDefinition-us-core-practitioner.html)
+        * PractitionerRoles (1..*)
+          * Must conform to [US Core PractitionerRole](http://hl7.org/fhir/us/core/STU5.0.1/StructureDefinition-us-core-practitionerrole.html)
+        * Identifies the healthcare providers involved and their roles
       ## Profile Validation
-      Each resource extracted from the bundles is expected to conform to
-      its target profile. Each element in each resource is checked against
-      teminology binding and cardinality requirements by the HL7 FHIR validator.
-      While the [Cancer Pathology Exchange Bundle profile](https://hl7.org/fhir/us/cancer-reporting/STU1.0.1/StructureDefinition-us-pathology-exchange-bundle.html)
-      slices entries by profile, Inferno checks that any instances of the profiled resource type
-      conform to the indicated profile and there are not more instances of the profiled resource type than allowed
-      by the slice cardinality. Specifically, each report must contain:
-      - Exactly one Patient, which must conform to the [US Core Patient profile](http://hl7.org/fhir/us/core/STU5.0.1/StructureDefinition-us-core-patient.html).
-      - At most one Encounter, which, if present, must conform to the [US Core Encounter profile](http://hl7.org/fhir/us/core/STU5.0.1/StructureDefinition-us-core-encounter.html).
-      - Exactly one DiagnosticReport, which must conform to the [US Pathology Diagnostic Report profile](https://hl7.org/fhir/us/cancer-reporting/STU1.0.1/StructureDefinition-us-pathology-diagnostic-report.html).
-      - One or more Specimens, each of which must conform to the [US Pathology Specimen profile](https://hl7.org/fhir/us/cancer-reporting/STU1.0.1/StructureDefinition-us-pathology-specimen.html).
-      Additionally, each report may include:
-      - Any number of ServiceRequests, each of which must conform to the [US Pathology Service Requests profile](https://hl7.org/fhir/us/cancer-reporting/STU1.0.1/StructureDefinition-us-pathology-service-request.html).
-      - Any number of PractitionRoles, each of which must conform to the [US Pathology Related Practitioner Roles profile](https://hl7.org/fhir/us/cancer-reporting/STU1.0.1/StructureDefinition-us-pathology-related-practitioner-role.html).
-      ## Must Support
-      Must Support tests in this group check that each element of the target profile marked
-      as "must support" is observed at least once across instances assigned to that profile.
-      If one or more elements are not observed, the test will fail.
+      For each resource type, the tests verify:
+      * Conformance to the required profile
+      * Presence of all required elements
+      * Correct use of required terminologies and value sets
+      * Valid references to other resources
+      * Proper cardinality of elements and slices
+      ## Must Support Validation
+      For each profile, the tests verify that all elements marked as "must support" are demonstrated
+      at least once across the submitted reports. This ensures systems can:
+      * Populate all required data elements
+      * Handle all required data types and structures
+      * Support all required workflows and use cases
+      ## Missing Data Handling
+      The tests also verify proper implementation of missing data patterns:
+      * Use of DataAbsentReason Extension for non-coded required fields
+      * Use of appropriate "unknown" codes for coded fields
+      * Proper handling of optional missing elements
     )
     run_as_group

data/lib/cancer_pathology_data_sharing_test_kit/report_generation_suite.rb CHANGED Viewed

@@ -29,6 +29,14 @@ module CancerPathologyDataSharingTestKit
       }
     ]
+    requirement_sets(
+      {
+        identifier: 'hl7.fhir.us.cancer-reporting_1.0.1',
+        title: 'Cancer Pathology Data Sharing IG STU 1.0.1',
+        actor: 'Report Creator'
+      }
+    )
     GENERAL_MESSAGE_FILTERS = [
       %r{Sub-extension url 'introspect' is not defined by the Extension http://fhir-registry\.smarthealthit\.org/StructureDefinition/oauth-uris},
       %r{Sub-extension url 'revoke' is not defined by the Extension http://fhir-registry\.smarthealthit\.org/StructureDefinition/oauth-uris},

data/lib/cancer_pathology_data_sharing_test_kit/requirements/cancer_pathology_data_sharing_test_kit_requirements.csv ADDED Viewed

@@ -0,0 +1,34 @@
+Req Set,ID,URL,Requirement,Conformance,Actors,Sub-Requirement(s),Conditionality,Not Tested Reason,Not Tested Details
+hl7.fhir.us.cancer-reporting_1.0.1,1,https://hl7.org/fhir/us/cancer-reporting/STU1.0.1/specification.html#claiming-conformance-to-this-specification,"This specification conforms to US Core Profiles, to claim conformance to this specification, servers [data suppliers] SHALL: … Be able to populate all profile data elements that have a minimum cardinality >= 1",SHALL,Data Supplier,,false,,
+hl7.fhir.us.cancer-reporting_1.0.1,2,https://hl7.org/fhir/us/cancer-reporting/STU1.0.1/specification.html#claiming-conformance-to-this-specification,"This specification conforms to US Core Profiles, to claim conformance to this specification, servers [data supplier] SHALL: … Be able to populate all profile data elements …  flagged as Must Support as defined by that profile’s StructureDefinition",SHALL,Data Supplier,,true,,
+hl7.fhir.us.cancer-reporting_1.0.1,3,https://hl7.org/fhir/us/cancer-reporting/STU1.0.1/specification.html#claiming-conformance-to-this-specification,"To claim conformance to this specification, servers [data supplier] SHALL:  ... Conform to this IG’s Server Capability Statement expectations",SHALL,Data Supplier,"hl7.fhir.us.cancer-reporting_1.0.1@15,16,17",true,,
+hl7.fhir.us.cancer-reporting_1.0.1,4,https://hl7.org/fhir/us/cancer-reporting/STU1.0.1/specification.html#must-support-and-missing-data,"As part of the sending of a US Pathology Bundle [([definition](https://hl7.org/fhir/us/cancer-reporting/STU1.0.1/StructureDefinition-us-pathology-exchange-bundle.html))], the Sender SHALL be capable of including all elements defined in the profiles that have a MustSupport flag",SHALL,Report Creator,,false,,
+hl7.fhir.us.cancer-reporting_1.0.1,5,https://hl7.org/fhir/us/cancer-reporting/STU1.0.1/specification.html#must-support-and-missing-data,"As part of the sending of a US Pathology Bundle [([definition](https://hl7.org/fhir/us/cancer-reporting/STU1.0.1/StructureDefinition-us-pathology-exchange-bundle.html))], the Sender ... SHALL populate all elements with a MustSupport flag if the information exists",SHALL,Report Creator,,false,,
+hl7.fhir.us.cancer-reporting_1.0.1,6,https://hl7.org/fhir/us/cancer-reporting/STU1.0.1/specification.html#must-support-and-missing-data,"In situations where information on a particular data element is not present, the Sender SHALL NOT include the data element in the resource instance if the cardinality is 0..n",SHALL NOT,Report Creator,,true,,
+hl7.fhir.us.cancer-reporting_1.0.1,7,https://hl7.org/fhir/us/cancer-reporting/STU1.0.1/specification.html#must-support-and-missing-data,"If the information does not exist and the cardinality of the element is >= 1..*, the Sender [of the [US Pathology Bundle](https://hl7.org/fhir/us/cancer-reporting/STU1.0.1/StructureDefinition-us-pathology-exchange-bundle.html)] SHALL use the [dataAbsentReason](http://hl7.org/fhir/ValueSet/data-absent-reason) extension where it is defined. ",SHALL,Report Creator,,true,,
+hl7.fhir.us.cancer-reporting_1.0.1,8,https://hl7.org/fhir/us/cancer-reporting/STU1.0.1/specification.html#must-support-and-missing-data,Populating the element [in the [US Pathology Bundle](https://hl7.org/fhir/us/cancer-reporting/STU1.0.1/StructureDefinition-us-pathology-exchange-bundle.html)] with the value set absent reason or using the dataAbsent Reason SHOULD be handled by the Sending System and not require provider action.,SHOULD,Report Creator,,true,,
+hl7.fhir.us.cancer-reporting_1.0.1,9,https://hl7.org/fhir/us/cancer-reporting/STU1.0.1/specification.html#must-support-and-missing-data,The Receiving System [of the [US Pathology Bundle](https://hl7.org/fhir/us/cancer-reporting/STU1.0.1/StructureDefinition-us-pathology-exchange-bundle.html)] SHALL be capable of processing resource instances containing required and allowed data elements without generating an error or causing the application to fail.,SHALL,Report Receiver,,true,,
+hl7.fhir.us.cancer-reporting_1.0.1,10,https://hl7.org/fhir/us/cancer-reporting/STU1.0.1/specification.html#must-support-and-missing-data,"Receiving Systems [of the [US Pathology Bundle](https://hl7.org/fhir/us/cancer-reporting/STU1.0.1/StructureDefinition-us-pathology-exchange-bundle.html)] SHOULD be capable of processing (display, store, etc.) the data elements based on the utility of the specific element to the receiver.",SHOULD,Report Receiver,,true,,
+hl7.fhir.us.cancer-reporting_1.0.1,11,https://hl7.org/fhir/us/cancer-reporting/STU1.0.1/specification.html#must-support-and-missing-data,"When receiving a US Pathology Bundle [([definition](https://hl7.org/fhir/us/cancer-reporting/STU1.0.1/StructureDefinition-us-pathology-exchange-bundle.html))] from the Sender, the Receiving System SHALL interpret missing data elements within resource instances as data not present in the Senders systems.",SHALL,Report Receiver,,true,,
+hl7.fhir.us.cancer-reporting_1.0.1,12,https://hl7.org/fhir/us/cancer-reporting/STU1.0.1/specification.html#must-support-and-missing-data,Receiving Systems [of the [US Pathology Bundle](https://hl7.org/fhir/us/cancer-reporting/STU1.0.1/StructureDefinition-us-pathology-exchange-bundle.html)] SHALL be able to process resource instances containing data elements asserting missing information [following [US Core requirements](https://hl7.org/fhir/us/core/STU5/general-requirements.html#missing-data)] without generating an error or causing the application to fail.,SHALL,Report Receiver,,true,,
+hl7.fhir.us.cancer-reporting_1.0.1,13,https://hl7.org/fhir/us/cancer-reporting/STU1.0.1/specification.html#conformance-to-us-core-profile,"Where this IG does not additionally constrain a US Core profile, the actors shall follow the US Core definition of [Must Support and Missing Data](http://hl7.org/fhir/us/core/general-guidance.html)",SHALL,Data Supplier,,false,,
+hl7.fhir.us.cancer-reporting_1.0.1,14,https://hl7.org/fhir/us/cancer-reporting/STU1.0.1/specification.html#privacy-and-security,Systems implementing this guide are expected to follow the general [FHIR Security guidelines](https://www.hl7.org/fhir/security.html),SHALL,"Data Supplier, Report Creator Report Receiver",,false,,
+hl7.fhir.us.cancer-reporting_1.0.1,15,https://hl7.org/fhir/us/cancer-reporting/STU1.0.1/specification.html#privacy-and-security,Systems implementing this guide are expected to follow ... applicable public and private laws and policies.,SHALL,"Data Supplier, Report Creator Report Receiver",,false,,
+hl7.fhir.us.cancer-reporting_1.0.1,16,https://www.hl7.org/fhir/us/cancer-reporting/CapabilityStatement-central-cancer-registry-reporting-ehr-pathology.html#rest,"The focus of the EHR is to allow creation, modification and deletion of ServiceRequests",SHALL,Data Supplier,,false,,
+hl7.fhir.us.cancer-reporting_1.0.1,17,https://www.hl7.org/fhir/us/cancer-reporting/CapabilityStatement-central-cancer-registry-reporting-ehr-pathology.html#rest,The focus of the EHR is to allow ... searching and retrieval of resources using US Core APIs,SHALL,Data Supplier,,true,,
+hl7.fhir.us.cancer-reporting_1.0.1,18,https://www.hl7.org/fhir/us/cancer-reporting/CapabilityStatement-central-cancer-registry-reporting-ehr-pathology.html#rest,Implementations must meet the general security requirements documented in the security section of the implementation guide,SHALL,Data Supplier,"hl7.fhir.us.cancer-reporting_1.0.1@14,15",false,,
+hl7.fhir.us.cancer-reporting_1.0.1,19,https://hl7.org/fhir/us/cancer-reporting/STU1.0.1/CapabilityStatement-central-cancer-registry-reporting-ehr-pathology.html#resourcesCap1,"[SHALL Support the following interactions for [ServiceRequest] (https://hl7.org/fhir/us/cancer-reporting/STU1.0.1/CapabilityStatement-central-cancer-registry-reporting-ehr-pathology.html#ServiceRequest1-1): read, create, update, delete]",SHALL,Data Supplier,,false,,
+hl7.fhir.us.cancer-reporting_1.0.1,20,https://www.hl7.org/fhir/us/cancer-reporting/StructureDefinition-us-pathology-message-header.html#root,This MessageHeader profile [([definition](https://www.hl7.org/fhir/us/cancer-reporting/StructureDefinition-us-pathology-message-header.html#root))] is expected to be used [when reporting cancer pathology information] by systems when sending to public health registries.,SHALL,Report Creator,,false,,
+hl7.fhir.us.cancer-reporting_1.0.1,21,https://www.hl7.org/fhir/us/cancer-reporting/StructureDefinition-us-pathology-message-header.html#root,This MessageHeader profile [([definition](https://www.hl7.org/fhir/us/cancer-reporting/StructureDefinition-us-pathology-message-header.html#root))] is expected to be used [when receiving cancer pathology information]  by systems when sending to public health registries.,SHALL,Report Receiver,,false,,
+hl7.fhir.us.cancer-reporting_1.0.1,22,https://www.hl7.org/fhir/us/cancer-reporting/StructureDefinition-us-pathology-message-header.html#root,"This MessageHeader profile [([definition](https://www.hl7.org/fhir/us/cancer-reporting/StructureDefinition-us-pathology-message-header.html#root))] ... is not expected and not appropriate to be used in any other cases, such as when information exchange between a pathology laboratory and a clinical EHR system.",SHOULD NOT,Report Creator,,false,,
+hl7.fhir.us.cancer-reporting_1.0.1,23,https://www.hl7.org/fhir/us/cancer-reporting/StructureDefinition-us-pathology-content-bundle.html#root,This [[US Pathology Cancer Registry Content Bundle](https://www.hl7.org/fhir/us/cancer-reporting/StructureDefinition-us-pathology-content-bundle.html)] profile defines the structure of a bundle [when reporting cancer pathology information from a] pathology information environment [LIS] to an EHR environment.,SHALL,Report Creator,,false,,
+hl7.fhir.us.cancer-reporting_1.0.1,24,https://www.hl7.org/fhir/us/cancer-reporting/StructureDefinition-us-pathology-content-bundle.html#root,This [[US Pathology Cancer Registry Content Bundle](https://www.hl7.org/fhir/us/cancer-reporting/StructureDefinition-us-pathology-content-bundle.html)] profile defines the structure of a bundle [when reporting cancer pathology information from a] pathology information environment [LIS] to an EHR environment.,SHALL,Report Receiver,,false,,
+hl7.fhir.us.cancer-reporting_1.0.1,25,https://www.hl7.org/fhir/us/cancer-reporting/StructureDefinition-us-pathology-content-bundle.html#root,This [[US Pathology Cancer Registry Content Bundle](https://www.hl7.org/fhir/us/cancer-reporting/StructureDefinition-us-pathology-content-bundle.html)] profile ... is not intended for central cancer registry reporting.,SHALL NOT,Report Creator,,false,,
+hl7.fhir.us.cancer-reporting_1.0.1,26,https://www.hl7.org/fhir/us/cancer-reporting/StructureDefinition-us-pathology-content-bundle.html#root,[Use the] US Pathology Registry Bundle [([definition](https://www.hl7.org/fhir/us/cancer-reporting/StructureDefinition-us-pathology-reporting-bundle.html))] for [reporting from the EHR to the public health registry],SHALL,Report Creator,,false,,
+hl7.fhir.us.cancer-reporting_1.0.1,27,https://www.hl7.org/fhir/us/cancer-reporting/StructureDefinition-us-pathology-content-bundle.html#root,[Use the] US Pathology Registry Bundle [([definition](https://www.hl7.org/fhir/us/cancer-reporting/StructureDefinition-us-pathology-reporting-bundle.html))] for [reporting from the EHR to the public health registry],SHALL,Report Receiver,,false,,
+hl7.fhir.us.cancer-reporting_1.0.1,28,https://www.hl7.org/fhir/us/cancer-reporting/StructureDefinition-us-pathology-content-bundle.html#root,"US Core profiles are expected for Encounter, Organization, Patient, Practitioner, and Procedure [instances referenced and included in the [US Pathology Cancer Registry Content Bundle](https://www.hl7.org/fhir/us/cancer-reporting/StructureDefinition-us-pathology-content-bundle.html)], when such information is known",SHOULD,Report Creator,,true,,
+hl7.fhir.us.cancer-reporting_1.0.1,29,https://www.hl7.org/fhir/us/cancer-reporting/StructureDefinition-us-pathology-exchange-bundle.html#root,This [[US Pathology Exchange Bundle](https://www.hl7.org/fhir/us/cancer-reporting/StructureDefinition-us-pathology-exchange-bundle.html)] collection bundle profile  defines the structure [and should be used] for reporting to central cancer registry reporting from a pathology environment and/or from an EHR enviroment.,SHALL,Report Creator,,false,,
+hl7.fhir.us.cancer-reporting_1.0.1,30,https://www.hl7.org/fhir/us/cancer-reporting/StructureDefinition-us-pathology-exchange-bundle.html#root,This [[US Pathology Exchange Bundle](https://www.hl7.org/fhir/us/cancer-reporting/StructureDefinition-us-pathology-exchange-bundle.html)] collection bundle profile  defines the structure [and should be used] for reporting to central cancer registry reporting from a pathology environment and/or from an EHR enviroment.,SHALL,Report Receiver,,false,,
+hl7.fhir.us.cancer-reporting_1.0.1,31,https://www.hl7.org/fhir/us/cancer-reporting/StructureDefinition-us-pathology-exchange-bundle.html#root,"To properly process this [[US Pathology Exchange](https://www.hl7.org/fhir/us/cancer-reporting/StructureDefinition-us-pathology-exchange-bundle.html)] transaction bundle, post to the root endpoint of the server (rather than the Bundle endpoint).",SHALL,Report Creator,,false,,
+hl7.fhir.us.cancer-reporting_1.0.1,32,https://www.hl7.org/fhir/us/cancer-reporting/StructureDefinition-us-pathology-exchange-bundle.html#root,"US Core profiles are expected for Encounter, Organization, Patient, Practitioner, and Procedure [instances referenced and included in the [US Pathology Exchange Bundle](https://www.hl7.org/fhir/us/cancer-reporting/StructureDefinition-us-pathology-exchange-bundle.html)], when such information is known",SHOULD,Report Creator,,true,,
+hl7.fhir.us.cancer-reporting_1.0.1,33,https://www.hl7.org/fhir/us/cancer-reporting/StructureDefinition-us-pathology-diagnostic-report.html,[When using the [US Pathology Diagnostic Report profile](https://www.hl7.org/fhir/us/cancer-reporting/StructureDefinition-us-pathology-diagnostic-report.html)] It is expected that labs will populate dateTimes with the most specific time information known when sending to EHRs (YYYY-MM-DD).,SHALL,Report Creator,,false,,

data/lib/cancer_pathology_data_sharing_test_kit/requirements/generated/cpds_data_access_requirements_coverage.csv ADDED Viewed

@@ -0,0 +1,11 @@
+Req Set,ID,URL,Requirement,Conformance,Actors,Conditionality,Not Tested Reason,Not Tested Details,Cancer Pathology Data Sharing Data Access Test Suite Short ID(s),Cancer Pathology Data Sharing Data Access Test Suite Full ID(s)
+hl7.fhir.us.cancer-reporting_1.0.1,1,https://hl7.org/fhir/us/cancer-reporting/STU1.0.1/specification.html#claiming-conformance-to-this-specification,"This specification conforms to US Core Profiles, to claim conformance to this specification, servers [data suppliers] SHALL: … Be able to populate all profile data elements that have a minimum cardinality >= 1",SHALL,Data Supplier,false,,,"",""
+hl7.fhir.us.cancer-reporting_1.0.1,2,https://hl7.org/fhir/us/cancer-reporting/STU1.0.1/specification.html#claiming-conformance-to-this-specification,"This specification conforms to US Core Profiles, to claim conformance to this specification, servers [data supplier] SHALL: … Be able to populate all profile data elements …  flagged as Must Support as defined by that profile’s StructureDefinition",SHALL,Data Supplier,true,,,"",""
+hl7.fhir.us.cancer-reporting_1.0.1,3,https://hl7.org/fhir/us/cancer-reporting/STU1.0.1/specification.html#claiming-conformance-to-this-specification,"To claim conformance to this specification, servers [data supplier] SHALL:  ... Conform to this IG’s Server Capability Statement expectations",SHALL,Data Supplier,true,,,"",""
+hl7.fhir.us.cancer-reporting_1.0.1,13,https://hl7.org/fhir/us/cancer-reporting/STU1.0.1/specification.html#conformance-to-us-core-profile,"Where this IG does not additionally constrain a US Core profile, the actors shall follow the US Core definition of [Must Support and Missing Data](http://hl7.org/fhir/us/core/general-guidance.html)",SHALL,Data Supplier,false,,,"",""
+hl7.fhir.us.cancer-reporting_1.0.1,14,https://hl7.org/fhir/us/cancer-reporting/STU1.0.1/specification.html#privacy-and-security,Systems implementing this guide are expected to follow the general [FHIR Security guidelines](https://www.hl7.org/fhir/security.html),SHALL,"Data Supplier,Report Creator Report Receiver",false,,,"",""
+hl7.fhir.us.cancer-reporting_1.0.1,15,https://hl7.org/fhir/us/cancer-reporting/STU1.0.1/specification.html#privacy-and-security,Systems implementing this guide are expected to follow ... applicable public and private laws and policies.,SHALL,"Data Supplier,Report Creator Report Receiver",false,,,"",""
+hl7.fhir.us.cancer-reporting_1.0.1,16,https://www.hl7.org/fhir/us/cancer-reporting/CapabilityStatement-central-cancer-registry-reporting-ehr-pathology.html#rest,"The focus of the EHR is to allow creation, modification and deletion of ServiceRequests",SHALL,Data Supplier,false,,,"",""
+hl7.fhir.us.cancer-reporting_1.0.1,17,https://www.hl7.org/fhir/us/cancer-reporting/CapabilityStatement-central-cancer-registry-reporting-ehr-pathology.html#rest,The focus of the EHR is to allow ... searching and retrieval of resources using US Core APIs,SHALL,Data Supplier,true,,,"",""
+hl7.fhir.us.cancer-reporting_1.0.1,18,https://www.hl7.org/fhir/us/cancer-reporting/CapabilityStatement-central-cancer-registry-reporting-ehr-pathology.html#rest,Implementations must meet the general security requirements documented in the security section of the implementation guide,SHALL,Data Supplier,false,,,"",""
+hl7.fhir.us.cancer-reporting_1.0.1,19,https://hl7.org/fhir/us/cancer-reporting/STU1.0.1/CapabilityStatement-central-cancer-registry-reporting-ehr-pathology.html#resourcesCap1,"[SHALL Support the following interactions for [ServiceRequest] (https://hl7.org/fhir/us/cancer-reporting/STU1.0.1/CapabilityStatement-central-cancer-registry-reporting-ehr-pathology.html#ServiceRequest1-1): read, create, update, delete]",SHALL,Data Supplier,false,,,"",""

data/lib/cancer_pathology_data_sharing_test_kit/requirements/generated/cpds_report_generation_requirements_coverage.csv ADDED Viewed

@@ -0,0 +1,16 @@
+Req Set,ID,URL,Requirement,Conformance,Actors,Conditionality,Not Tested Reason,Not Tested Details,Cancer Pathology Data Sharing Report Generation Test Suite Short ID(s),Cancer Pathology Data Sharing Report Generation Test Suite Full ID(s)
+hl7.fhir.us.cancer-reporting_1.0.1,4,https://hl7.org/fhir/us/cancer-reporting/STU1.0.1/specification.html#must-support-and-missing-data,"As part of the sending of a US Pathology Bundle [([definition](https://hl7.org/fhir/us/cancer-reporting/STU1.0.1/StructureDefinition-us-pathology-exchange-bundle.html))], the Sender SHALL be capable of including all elements defined in the profiles that have a MustSupport flag",SHALL,Report Creator,false,,,"",""
+hl7.fhir.us.cancer-reporting_1.0.1,5,https://hl7.org/fhir/us/cancer-reporting/STU1.0.1/specification.html#must-support-and-missing-data,"As part of the sending of a US Pathology Bundle [([definition](https://hl7.org/fhir/us/cancer-reporting/STU1.0.1/StructureDefinition-us-pathology-exchange-bundle.html))], the Sender ... SHALL populate all elements with a MustSupport flag if the information exists",SHALL,Report Creator,false,,,"",""
+hl7.fhir.us.cancer-reporting_1.0.1,6,https://hl7.org/fhir/us/cancer-reporting/STU1.0.1/specification.html#must-support-and-missing-data,"In situations where information on a particular data element is not present, the Sender SHALL NOT include the data element in the resource instance if the cardinality is 0..n",SHALL NOT,Report Creator,true,,,"",""
+hl7.fhir.us.cancer-reporting_1.0.1,7,https://hl7.org/fhir/us/cancer-reporting/STU1.0.1/specification.html#must-support-and-missing-data,"If the information does not exist and the cardinality of the element is >= 1..*, the Sender [of the [US Pathology Bundle](https://hl7.org/fhir/us/cancer-reporting/STU1.0.1/StructureDefinition-us-pathology-exchange-bundle.html)] SHALL use the [dataAbsentReason](http://hl7.org/fhir/ValueSet/data-absent-reason) extension where it is defined. ",SHALL,Report Creator,true,,,"",""
+hl7.fhir.us.cancer-reporting_1.0.1,8,https://hl7.org/fhir/us/cancer-reporting/STU1.0.1/specification.html#must-support-and-missing-data,Populating the element [in the [US Pathology Bundle](https://hl7.org/fhir/us/cancer-reporting/STU1.0.1/StructureDefinition-us-pathology-exchange-bundle.html)] with the value set absent reason or using the dataAbsent Reason SHOULD be handled by the Sending System and not require provider action.,SHOULD,Report Creator,true,,,"",""
+hl7.fhir.us.cancer-reporting_1.0.1,20,https://www.hl7.org/fhir/us/cancer-reporting/StructureDefinition-us-pathology-message-header.html#root,This MessageHeader profile [([definition](https://www.hl7.org/fhir/us/cancer-reporting/StructureDefinition-us-pathology-message-header.html#root))] is expected to be used [when reporting cancer pathology information] by systems when sending to public health registries.,SHALL,Report Creator,false,,,"",""
+hl7.fhir.us.cancer-reporting_1.0.1,22,https://www.hl7.org/fhir/us/cancer-reporting/StructureDefinition-us-pathology-message-header.html#root,"This MessageHeader profile [([definition](https://www.hl7.org/fhir/us/cancer-reporting/StructureDefinition-us-pathology-message-header.html#root))] ... is not expected and not appropriate to be used in any other cases, such as when information exchange between a pathology laboratory and a clinical EHR system.",SHOULD NOT,Report Creator,false,,,"",""
+hl7.fhir.us.cancer-reporting_1.0.1,23,https://www.hl7.org/fhir/us/cancer-reporting/StructureDefinition-us-pathology-content-bundle.html#root,This [[US Pathology Cancer Registry Content Bundle](https://www.hl7.org/fhir/us/cancer-reporting/StructureDefinition-us-pathology-content-bundle.html)] profile defines the structure of a bundle [when reporting cancer pathology information from a] pathology information environment [LIS] to an EHR environment.,SHALL,Report Creator,false,,,"",""
+hl7.fhir.us.cancer-reporting_1.0.1,25,https://www.hl7.org/fhir/us/cancer-reporting/StructureDefinition-us-pathology-content-bundle.html#root,This [[US Pathology Cancer Registry Content Bundle](https://www.hl7.org/fhir/us/cancer-reporting/StructureDefinition-us-pathology-content-bundle.html)] profile ... is not intended for central cancer registry reporting.,SHALL NOT,Report Creator,false,,,"",""
+hl7.fhir.us.cancer-reporting_1.0.1,26,https://www.hl7.org/fhir/us/cancer-reporting/StructureDefinition-us-pathology-content-bundle.html#root,[Use the] US Pathology Registry Bundle [([definition](https://www.hl7.org/fhir/us/cancer-reporting/StructureDefinition-us-pathology-reporting-bundle.html))] for [reporting from the EHR to the public health registry],SHALL,Report Creator,false,,,"",""
+hl7.fhir.us.cancer-reporting_1.0.1,28,https://www.hl7.org/fhir/us/cancer-reporting/StructureDefinition-us-pathology-content-bundle.html#root,"US Core profiles are expected for Encounter, Organization, Patient, Practitioner, and Procedure [instances referenced and included in the [US Pathology Cancer Registry Content Bundle](https://www.hl7.org/fhir/us/cancer-reporting/StructureDefinition-us-pathology-content-bundle.html)], when such information is known",SHOULD,Report Creator,true,,,"",""
+hl7.fhir.us.cancer-reporting_1.0.1,29,https://www.hl7.org/fhir/us/cancer-reporting/StructureDefinition-us-pathology-exchange-bundle.html#root,This [[US Pathology Exchange Bundle](https://www.hl7.org/fhir/us/cancer-reporting/StructureDefinition-us-pathology-exchange-bundle.html)] collection bundle profile  defines the structure [and should be used] for reporting to central cancer registry reporting from a pathology environment and/or from an EHR enviroment.,SHALL,Report Creator,false,,,"",""
+hl7.fhir.us.cancer-reporting_1.0.1,31,https://www.hl7.org/fhir/us/cancer-reporting/StructureDefinition-us-pathology-exchange-bundle.html#root,"To properly process this [[US Pathology Exchange](https://www.hl7.org/fhir/us/cancer-reporting/StructureDefinition-us-pathology-exchange-bundle.html)] transaction bundle, post to the root endpoint of the server (rather than the Bundle endpoint).",SHALL,Report Creator,false,,,"",""
+hl7.fhir.us.cancer-reporting_1.0.1,32,https://www.hl7.org/fhir/us/cancer-reporting/StructureDefinition-us-pathology-exchange-bundle.html#root,"US Core profiles are expected for Encounter, Organization, Patient, Practitioner, and Procedure [instances referenced and included in the [US Pathology Exchange Bundle](https://www.hl7.org/fhir/us/cancer-reporting/StructureDefinition-us-pathology-exchange-bundle.html)], when such information is known",SHOULD,Report Creator,true,,,"",""
+hl7.fhir.us.cancer-reporting_1.0.1,33,https://www.hl7.org/fhir/us/cancer-reporting/StructureDefinition-us-pathology-diagnostic-report.html,[When using the [US Pathology Diagnostic Report profile](https://www.hl7.org/fhir/us/cancer-reporting/StructureDefinition-us-pathology-diagnostic-report.html)] It is expected that labs will populate dateTimes with the most specific time information known when sending to EHRs (YYYY-MM-DD).,SHALL,Report Creator,false,,,"",""

data/lib/cancer_pathology_data_sharing_test_kit/requirements/hl7.fhir.us.cancer-reporting_1.0.1_requirements.xlsx ADDED Viewed

Binary file

data/lib/cancer_pathology_data_sharing_test_kit/us_core_data_access_suite.rb CHANGED Viewed

@@ -24,6 +24,14 @@ module CancerPathologyDataSharingTestKit
       }
     ]
+    requirement_sets(
+      {
+        identifier: 'hl7.fhir.us.cancer-reporting_1.0.1',
+        title: 'Cancer Pathology Data Sharing IG STU 1.0.1',
+        actor: 'Data Supplier'
+      }
+    )
     GENERAL_MESSAGE_FILTERS = [
       %r{Sub-extension url 'introspect' is not defined by the Extension http://fhir-registry\.smarthealthit\.org/StructureDefinition/oauth-uris},
       %r{Sub-extension url 'revoke' is not defined by the Extension http://fhir-registry\.smarthealthit\.org/StructureDefinition/oauth-uris},

data/lib/cancer_pathology_data_sharing_test_kit/version.rb CHANGED Viewed

@@ -1,4 +1,4 @@
 module CancerPathologyDataSharingTestKit
-  VERSION = '0.10.0'.freeze
-  LAST_UPDATED = '2025-07-22'.freeze # TODO: update next release
+  VERSION = '0.10.1'.freeze
+  LAST_UPDATED = '2025-07-30'.freeze # TODO: update next release
 end

metadata CHANGED Viewed

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: cancer_pathology_data_sharing_test_kit
 version: !ruby/object:Gem::Version
-  version: 0.10.0
+  version: 0.10.1
 platform: ruby
 authors:
 - Inferno Team
 autorequire:
 bindir: bin
 cert_chain: []
-date: 2025-07-23 00:00:00.000000000 Z
+date: 2025-07-30 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: inferno_core
@@ -92,6 +92,10 @@ files:
 - lib/cancer_pathology_data_sharing_test_kit/report_generation_suite/exchange_bundle/us_pathology_exchange_bundle/metadata.yml
 - lib/cancer_pathology_data_sharing_test_kit/report_generation_suite/exchange_bundle/us_pathology_exchange_bundle/us_pathology_exchange_bundle_must_support_test.rb
 - lib/cancer_pathology_data_sharing_test_kit/report_generation_suite/exchange_bundle_group.rb
+- lib/cancer_pathology_data_sharing_test_kit/requirements/cancer_pathology_data_sharing_test_kit_requirements.csv
+- lib/cancer_pathology_data_sharing_test_kit/requirements/generated/cpds_data_access_requirements_coverage.csv
+- lib/cancer_pathology_data_sharing_test_kit/requirements/generated/cpds_report_generation_requirements_coverage.csv
+- lib/cancer_pathology_data_sharing_test_kit/requirements/hl7.fhir.us.cancer-reporting_1.0.1_requirements.xlsx
 - lib/cancer_pathology_data_sharing_test_kit/urls.rb
 - lib/cancer_pathology_data_sharing_test_kit/us_core_data_access_suite.rb
 - lib/cancer_pathology_data_sharing_test_kit/us_core_data_access_suite/us_core_group.rb