cancer_registry_reporting_test_kit 0.9.0

data/lib/cancer_registry_reporting_test_kit/requirements/cancer-registry-reporting-test-kit_out_of_scope_requirements.csv

@@ -0,0 +1,77 @@
+Req Set,ID,Reason,Details
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,15,Not Verifiable,Broken link meaning that specific requirements are not known.
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,16,Not Tested,"Transport of data outside of US Core API use, including the use of MedMorph, is not yet mature enough to test."
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,17,Not Tested,"Transport of data outside of US Core API use, including the use of MedMorph, is not yet mature enough to test."
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,18,Not Tested,"Transport of data outside of US Core API use, including the use of MedMorph, is not yet mature enough to test."
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,22,Not Tested,"Requirement 101 nearly the same, but 101 goes into more detail."
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,23,Not Tested,Attestation
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,36,Not Tested,"Use of the MedMorph framework, including the use of Subscriptions, is not yet mature enough to test."
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,37,Not Tested,"Use of the MedMorph framework, including the use of Subscriptions, is not yet mature enough to test."
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,38,Not Tested,"Use of the MedMorph framework, including the use of Subscriptions, is not yet mature enough to test."
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,39,Not Tested,"Use of the MedMorph framework, including the use of Subscriptions, is not yet mature enough to test."
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,40,Not Tested,"Use of the MedMorph framework, including the use of Subscriptions, is not yet mature enough to test."
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,41,Not Tested,"Use of the MedMorph framework, including the use of Subscriptions, is not yet mature enough to test."
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,42,Not Tested,"Use of the MedMorph framework, including the use of Subscriptions, is not yet mature enough to test."
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,44,Not Tested,
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,46,Not Tested,"Use of the MedMorph framework, including the use of Subscriptions, is not yet mature enough to test."
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,47,Not Tested,"Use of the MedMorph framework, including the use of Subscriptions, is not yet mature enough to test."
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,48,Not Tested,"Use of the MedMorph framework, including the use of Subscriptions, is not yet mature enough to test."
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,49,Not Tested,"Use of the MedMorph framework, including the use of Subscriptions, is not yet mature enough to test."
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,50,Not Tested,"Use of the MedMorph framework, including the use of Subscriptions, is not yet mature enough to test."
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,51,Not Tested,"Use of the MedMorph framework, including the use of Subscriptions, is not yet mature enough to test."
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,52,Not Tested,"Use of the MedMorph framework, including the use of Subscriptions, is not yet mature enough to test."
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,53,Not Tested,"Use of the MedMorph framework, including the use of Subscriptions, is not yet mature enough to test."
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,56,Not Tested,"Use of the MedMorph framework, including the use of Subscriptions, is not yet mature enough to test."
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,57,Not Tested,"Use of the MedMorph framework, including the use of Subscriptions, is not yet mature enough to test."
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,58,Not Tested,"Use of the MedMorph framework, including the use of Subscriptions, is not yet mature enough to test."
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,59,Not Tested,Use of the MedMorph framework is not yet mature enough to test.
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,60,Not Tested,Use of the MedMorph framework is not yet mature enough to test.
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,61,Not Tested,"Use of the MedMorph framework, including the use of Subscriptions, is not yet mature enough to test."
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,62,Not Tested,"Use of the MedMorph framework, including the use of Subscriptions, is not yet mature enough to test."
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,63,Not Tested,"Use of the MedMorph framework, including the use of Subscriptions, is not yet mature enough to test."
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,64,Not Tested,Use of the MedMorph framework is not yet mature enough to test.
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,65,Not Tested,Use of the MedMorph framework is not yet mature enough to test.
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,67,Not Tested,Use of the EHR's APIs to access data will not be tested at this time.
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,69,Not Tested,"Use of the MedMorph framework, including its use of FHIR Messaging, is not yet mature enough to test."
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,70,Not Tested,"Use of the MedMorph framework, including its use of FHIR Messaging, is not yet mature enough to test."
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,71,Not Tested,"Use of the MedMorph framework, including its use of FHIR Messaging, is not yet mature enough to test."
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,72,Not Tested,Use of the MedMorph framework is not yet mature enough to test.
+hl7.fhir.us.mcode_3.0.0,2,Not Verifiable,"Cannot know from testing whether the resource ""should"" be for a primary or secondary cancer"
+hl7.fhir.us.mcode_3.0.0,4,Not Tested,Focus on SHALL requirements
+hl7.fhir.us.mcode_3.0.0,5,Not Tested,Focus on SHALL requirements
+hl7.fhir.us.mcode_3.0.0,7,Not Verifiable,
+hl7.fhir.us.mcode_3.0.0,8,Not Tested,Focus on SHALL requirements
+hl7.fhir.us.mcode_3.0.0,10,Not Tested,Focus on SHALL requirements
+hl7.fhir.us.mcode_3.0.0,13,Not Tested,Focus on SHALL requirements
+hl7.fhir.us.mcode_3.0.0,14,Not Tested,Will test broadly that a data sender can return conformant PrimaryCancerDisorder resources
+hl7.fhir.us.mcode_3.0.0,15,Not Verifiable,"""would reasonably be expected to conform to this profile"" is too subjective"
+hl7.fhir.us.mcode_3.0.0,30,Not Tested,Focus on SHALL requirements
+hl7.fhir.us.mcode_3.0.0,33,Not Tested,Focus on SHALL requirements
+hl7.fhir.us.mcode_3.0.0,34,Not Tested,Focus on SHALL requirements
+hl7.fhir.us.mcode_3.0.0,35,Not Verifiable,"Depending on the field (e.g. free text), it is difficult to check if a field's value is ""nonsense"""
+hl7.fhir.us.mcode_3.0.0,37,Not Tested,Focus on SHALL requirements
+hl7.fhir.us.mcode_3.0.0,38,Not Tested,Focus on the profiles that are required
+hl7.fhir.us.mcode_3.0.0,51,Not Tested,Focus on SHALL requirements
+hl7.fhir.us.mcode_3.0.0,55,Not Tested,Focus on SHALL requirements
+hl7.fhir.us.mcode_3.0.0,67,Not Tested,Focus on SHALL requirements
+hl7.fhir.us.mcode_3.0.0,69,Not Tested,Focus on SHALL requirements
+hl7.fhir.us.mcode_3.0.0,70,Not Tested,Will test broadly that a data sender can return conformant SecondaryCancerDisorder resources
+hl7.fhir.us.mcode_3.0.0,71,Not Tested,Focus on SHALL requirements
+hl7.fhir.us.mcode_3.0.0,72,Not Tested,Focus on SHALL requirements
+hl7.fhir.us.mcode_3.0.0,74,Not Tested,Focus on SHALL requirements
+hl7.fhir.us.mcode_3.0.0,76,Not Tested,Focus on SHALL requirements
+hl7.fhir.us.mcode_3.0.0,78,Not Tested,Focus on SHALL requirements
+hl7.fhir.us.mcode_3.0.0,80,Not Tested,Focus on SHALL requirements
+hl7.fhir.us.mcode_3.0.0,84,Not Tested,Focus on SHALL requirements
+hl7.fhir.us.mcode_3.0.0,85,Not Tested,Will test broadly that a data sender can return conformant RadioTherapyCourseSummary resources
+hl7.fhir.us.mcode_3.0.0,86,Not Tested,Focus on SHALL requirements
+hl7.fhir.us.mcode_3.0.0,87,Not Tested,Focus on SHALL requirements
+hl7.fhir.us.mcode_3.0.0,89,Not Verifiable,Can't tell if a resource is the initial diagnosis
+hl7.fhir.us.mcode_3.0.0,90,Not Tested,Focus on SHALL requirements
+hl7.fhir.us.mcode_3.0.0,91,Not Tested,Focus on SHALL requirements
+hl7.fhir.us.mcode_3.0.0,92,Not Tested,Focus on SHALL requirements
+hl7.fhir.us.mcode_3.0.0,93,Not Tested,Focus on SHALL requirements
+hl7.fhir.us.mcode_3.0.0,94,Not Verifiable,Difficult to programmatically check if these 3 values are self-consistent
+hl7.fhir.us.mcode_3.0.0,95,Not Tested,Focus on SHALL requirements
+hl7.fhir.us.mcode_3.0.0,97,Not Tested,Focus on SHALL requirements
+hl7.fhir.us.mcode_3.0.0,98,Not Tested,Focus on SHALL requirements

data/lib/cancer_registry_reporting_test_kit/requirements/cancer-registry-reporting-test-kit_requirements.csv

@@ -0,0 +1,162 @@
+Req Set,ID,URL,Requirement,Conformance,Actor,Sub-Requirement(s),Conditionality
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,1,https://www.hl7.org/fhir/us/central-cancer-registry-reporting/STU1/spec.html#must-support-definition,[EHR] Systems SHALL be capable of populating data elements as specified by the profiles and returning data elements [with the must support flag] using the specified APIs in the capability statement,SHALL,EHR,,true
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,2,https://www.hl7.org/fhir/us/central-cancer-registry-reporting/STU1/spec.html#must-support-definition,[HDEA] Systems SHALL be capable of processing resource instances [returned by EHRs] containing the MUST SUPPORT data elements without generating an error or causing the application to fail.,SHALL,HDEA,,true
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,6,https://www.hl7.org/fhir/us/central-cancer-registry-reporting/STU1/spec.html#must-support-definition,"In situations where information on a particular data element is not present and the reason for absence is unknown, [EHR] Systems SHALL NOT include the data elements in the resource instance returned from executing the API requests.",SHALL NOT,EHR,,true
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,7,https://www.hl7.org/fhir/us/central-cancer-registry-reporting/STU1/spec.html#must-support-definition,[HDEA] Systems SHALL interpret missing data elements within resource instances returned from API requests as data not present.,SHALL,HDEA,,true
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,9,https://www.hl7.org/fhir/us/central-cancer-registry-reporting/STU1/spec.html#must-support-definition,"When data is not available for any of the mandatory elements specified in the IG [to be returned in response to a data query], a data absent reason extension should be added to satisfy the requirement along with an appropriate value from the [data-absent-reason value set](http://hl7.org/fhir/ValueSet/data-absent-reason)",SHOULD,EHR,,true
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,10,https://www.hl7.org/fhir/us/central-cancer-registry-reporting/STU1/spec.html#must-support-definition,"When data is not available for any of the mandatory elements specified in the IG [for inclusion within a cancer report], a data absent reason extension should be added to satisfy the requirement along with an appropriate value from the [data-absent-reason value set](http://hl7.org/fhir/ValueSet/data-absent-reason)",SHOULD,HDEA,,true
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,11,https://www.hl7.org/fhir/us/central-cancer-registry-reporting/STU1/spec.html#mcode-fhir-ig-usage,Implementers SHOULD use the [mCode Disease characterization](http://hl7.org/fhir/us/mcode/STU3/group-disease.html) when using the above [mCode] profiles [to extract information from the EHR],SHOULD,EHR,hl7.fhir.us.mcode_3.0.0@88-98,false
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,12,https://www.hl7.org/fhir/us/central-cancer-registry-reporting/STU1/spec.html#mcode-fhir-ig-usage,Implementers SHOULD use the …  [mCode Treatment guidance](https://www.hl7.org/fhir/us/mcode/group-treatment.html) when using the above [mCode] profiles [to extract information from the EHR],SHOULD,EHR,,false
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,13,https://www.hl7.org/fhir/us/central-cancer-registry-reporting/STU1/spec.html#overall-security-requirements,Implementations must meet the general security requirements documented in [FHIR Security guidance](http://hl7.org/fhir/security.html),SHALL,"EHR, HDEA, Trusted Third Party, Cancer Registry",,false
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,14,https://www.hl7.org/fhir/us/central-cancer-registry-reporting/STU1/spec.html#overall-security-requirements,EHR needs to meet the security requirements as outlined in the [Authentication and Authorization Requirements](https://www.hl7.org/fhir/us/central-cancer-registry-reporting/STU1/spec.html#authentication-and-authorization-requirements),SHALL,EHR,"hl7.fhir.us.central-cancer-registry-reporting_1.0.0@16,20,22,23",false
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,15,https://www.hl7.org/fhir/us/central-cancer-registry-reporting/STU1/spec.html#overall-security-requirements,Implementers of this IG SHOULD follow the [HIPAA guidance](https://www.naaccr.org/hippa) [(broken link)] to ensure applicable security and privacy laws are implemented.,SHOULD,"EHR, HDEA, Trusted Third Party, Cancer Registry",,false
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,16,https://www.hl7.org/fhir/us/central-cancer-registry-reporting/STU1/spec.html#authentication-and-authorization-requirements,EHR[s] ... are required to conform to the [MedMorph Authentication and Authorization Requirements](http://hl7.org/fhir/us/medmorph/STU1/spec.html#authentication-and-authorization-requirements) for the following interactions: HDEA accessing data from the EHR.,SHALL,EHR,,false
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,17,https://www.hl7.org/fhir/us/central-cancer-registry-reporting/STU1/spec.html#authentication-and-authorization-requirements,Health Data Exchange App[s] (backend services app[s]) ... are required to conform to the [MedMorph Authentication and Authorization Requirements](http://hl7.org/fhir/us/medmorph/STU1/spec.html#authentication-and-authorization-requirements) for the following interactions: HDEA accessing data from the EHR.,SHALL,HDEA,,false
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,18,https://www.hl7.org/fhir/us/central-cancer-registry-reporting/STU1/spec.html#authentication-and-authorization-requirements,"Health Data Exchange App[s] (backend services app[s]) ... are required to conform to the [MedMorph Authentication and Authorization Requirements](http://hl7.org/fhir/us/medmorph/STU1/spec.html#authentication-and-authorization-requirements) for the following interactions:
+HDEA posting data to the Central Cancer Registry data store via the TTP or directly to the Central Cancer Registry.",SHALL,HDEA,,false
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,20,https://www.hl7.org/fhir/us/central-cancer-registry-reporting/STU1/spec.html#authentication-and-authorization-requirements,EHRs SHALL support the system/*.read scopes.,SHALL,EHR,,false
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,22,https://www.hl7.org/fhir/us/central-cancer-registry-reporting/STU1/spec.html#authentication-and-authorization-requirements,The healthcare organization’s existing processes along with the EHRs authorization server SHALL verify consent …  before allowing the HDEA to access the data to be included in the central cancer registry report.,SHALL,EHR,,true
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,23,https://www.hl7.org/fhir/us/central-cancer-registry-reporting/STU1/spec.html#authentication-and-authorization-requirements,The healthcare organization’s existing processes along with the EHRs authorization server SHALL verify ... other policy requirements before allowing the HDEA to access the data to be included in the central cancer registry report.,SHALL,EHR,,true
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,31,https://www.hl7.org/fhir/us/central-cancer-registry-reporting/STU1/spec.html#ehr-requirements,The EHR SHALL support the requirements as outlined in the [EHR Capability Statement](https://www.hl7.org/fhir/us/central-cancer-registry-reporting/STU1/CapabilityStatement-central-cancer-registry-reporting-ehr.html),SHALL,EHR,"hl7.fhir.us.central-cancer-registry-reporting_1.0.0@32,34-44",false
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,32,https://www.hl7.org/fhir/us/central-cancer-registry-reporting/STU1/CapabilityStatement-central-cancer-registry-reporting-ehr.html#rest-behavior,Implementations must meet the general security requirements documented in [FHIR Security guidance](http://hl7.org/fhir/security.html),SHALL,EHR,,false
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,34,https://www.hl7.org/fhir/us/central-cancer-registry-reporting/STU1/CapabilityStatement-central-cancer-registry-reporting-ehr.html#us-core-support,The EHR SHALL implement the [US Core Server capability statement](http://hl7.org/fhir/us/core/STU3.1.1/CapabilityStatement-us-core-server.html) as foundational FHIR APIs needed by the Central Cancer Registry Reporting IG,SHALL,EHR,hl7.fhir.us.core_5.0.1,false
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,35,https://www.hl7.org/fhir/us/central-cancer-registry-reporting/STU1/CapabilityStatement-central-cancer-registry-reporting-ehr.html#mcode-support,The EHR SHALL implement the [mCode profiles](https://www.hl7.org/fhir/us/central-cancer-registry-reporting/STU1/spec.html#mcode-fhir-ig-usage) outlined to support the Central Cancer Registry Reporting IG.,SHALL,EHR,"hl7.fhir.us.mcode_3.0.0@2-5,7-16,22-24,25,27,30-35,37-39,43-46,48-51,53-55,57,58,60,62,64-80,83-87,99,101,103,107-110",false
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,36,https://www.hl7.org/fhir/us/central-cancer-registry-reporting/STU1/CapabilityStatement-central-cancer-registry-reporting-ehr.html#resource-summary,[EHRs] Shall support the following interactions for [Backported Subscription](http://hl7.org/fhir/uv/subscriptions-backport/StructureDefinition-backport-subscription.html): read,SHALL,EHR,,false
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,37,https://www.hl7.org/fhir/us/central-cancer-registry-reporting/STU1/CapabilityStatement-central-cancer-registry-reporting-ehr.html#resource-summary,"[EHRs] May support the following interactions for [Backported Subscription](http://hl7.org/fhir/uv/subscriptions-backport/StructureDefinition-backport-subscription.html): create, update, delete",MAY,EHR,,false
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,38,https://www.hl7.org/fhir/us/central-cancer-registry-reporting/STU1/CapabilityStatement-central-cancer-registry-reporting-ehr.html#resource-summary,[EHRs] Shall support the following interactions for [Backported Subscription](http://hl7.org/fhir/uv/subscriptions-backport/StructureDefinition-backport-subscription.html): $status,SHALL,EHR,,false
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,39,https://www.hl7.org/fhir/us/central-cancer-registry-reporting/STU1/CapabilityStatement-central-cancer-registry-reporting-ehr.html#resource-summary,[EHRs] Shall support the following interactions for [Encounter Close Subscription Topic](http://hl7.org/fhir/us/medmorph/StructureDefinition-medmorph-encounter-end-subscription.html): read,SHALL,EHR,,false
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,40,"https://www.hl7.org/fhir/us/central-cancer-registry-reporting/STU1/CapabilityStatement-central-cancer-registry-reporting-ehr.html#resource-summary, https://www.hl7.org/fhir/us/central-cancer-registry-reporting/STU1/spec.html#subscription-requirements","[EHRs] May support the following interactions for [Encounter Close Subscription Topic](http://hl7.org/fhir/us/medmorph/StructureDefinition-medmorph-encounter-end-subscription.html): create, update, delete",MAY,EHR,,false
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,41,https://www.hl7.org/fhir/us/central-cancer-registry-reporting/STU1/CapabilityStatement-central-cancer-registry-reporting-ehr.html#resource-summary,[EHRs] Shall support the following interactions [Backport Subscription Notification Bundle](http://hl7.org/fhir/uv/subscriptions-backport/StructureDefinition-backport-subscription-notification-r4.html): create,SHALL,EHR,,false
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,42,https://www.hl7.org/fhir/us/central-cancer-registry-reporting/STU1/CapabilityStatement-central-cancer-registry-reporting-ehr.html#resource-summary,[EHRs] Shall support the following interactions [Backport Subscription Status](http://hl7.org/fhir/uv/subscriptions-backport/StructureDefinition-backport-subscription-status-r4.html): read,SHALL,EHR,,false
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,43,https://www.hl7.org/fhir/us/central-cancer-registry-reporting/STU1/CapabilityStatement-central-cancer-registry-reporting-ehr.html#resource-summary,"[EHRs] Shall support the following interactions [US Core APIs](http://hl7.org/fhir/us/core/STU3.1.1/CapabilityStatement-us-core-server.html): search, read",SHALL,EHR,,false
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,44,https://www.hl7.org/fhir/us/central-cancer-registry-reporting/STU1/CapabilityStatement-central-cancer-registry-reporting-ehr.html#resource-summary,"[Medication Administration resource](http://hl7.org/fhir/R4/medicationadministration.html) Shall support the following interactions: search, read",DEPRECATED,EHR,,false
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,46,https://www.hl7.org/fhir/us/central-cancer-registry-reporting/STU1/spec.html#subscription-requirements,EHRs SHALL support notifications based on the [encounter-end Subscription Topic.](http://hl7.org/fhir/us/medmorph/STU1/StructureDefinition-medmorph-encounter-end-subscription.html),SHALL,EHR,,false
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,47,https://www.hl7.org/fhir/us/central-cancer-registry-reporting/STU1/spec.html#subscription-requirements,EHRs SHALL support [rest-hook](http://hl7.org/fhir/R4/subscription.html#2.46.7.1) Subscription channel to notify the HDEA,SHALL,EHR,,false
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,48,https://www.hl7.org/fhir/us/central-cancer-registry-reporting/STU1/spec.html#subscription-requirements,"EHRs MAY support the creation, deletion, updation of Subscriptions for the [encounter-end Subscription Topic]{http://hl7.org/fhir/us/medmorph/STU1/StructureDefinition-medmorph-encounter-end-subscription.html)",MAY,EHR,,false
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,49,https://www.hl7.org/fhir/us/central-cancer-registry-reporting/STU1/spec.html#subscription-requirements,EHRs Should support Notification Bundles with [full resource payload](http://hl7.org/fhir/uv/subscriptions-backport/STU1.1/payloads.html#full-resource) ... as outlined in the Backport Subscriptions IG [[link](https://build.fhir.org/ig/HL7/fhir-subscription-backport-ig/index.html)],SHOULD,EHR,,false
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,50,https://www.hl7.org/fhir/us/central-cancer-registry-reporting/STU1/spec.html#subscription-requirements,EHRs Should support Notification Bundles with ... [Id-only payload](http://hl7.org/fhir/uv/subscriptions-backport/STU1.1/payloads.html#id-only) as outlined in the Backport Subscriptions IG [[link](https://build.fhir.org/ig/HL7/fhir-subscription-backport-ig/index.html)],SHOULD,EHR,,false
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,51,https://www.hl7.org/fhir/us/central-cancer-registry-reporting/STU1/spec.html#subscription-requirements,EHRs MAY support operations and APIs for Subscription ... resources as outlined in the [EHR Capability Statement](https://www.hl7.org/fhir/us/central-cancer-registry-reporting/STU1/CapabilityStatement-central-cancer-registry-reporting-ehr.html),MAY,EHR,,false
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,52,https://www.hl7.org/fhir/us/central-cancer-registry-reporting/STU1/spec.html#subscription-requirements,EHRs MAY support operations and APIs for … Notification Bundle ... resources as outlined in the [EHR Capability Statement](https://www.hl7.org/fhir/us/central-cancer-registry-reporting/STU1/CapabilityStatement-central-cancer-registry-reporting-ehr.html),MAY,EHR,,false
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,53,https://www.hl7.org/fhir/us/central-cancer-registry-reporting/STU1/spec.html#subscription-requirements,EHRs MAY support operations and APIs for … Subscription Status resources as outlined in the [EHR Capability Statement](https://www.hl7.org/fhir/us/central-cancer-registry-reporting/STU1/CapabilityStatement-central-cancer-registry-reporting-ehr.html),MAY,EHR,,false
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,54,https://www.hl7.org/fhir/us/central-cancer-registry-reporting/STU1/spec.html#data-api-requirements,EHRs SHALL support the APIs as outlined in the [EHR Capability Statement](https://www.hl7.org/fhir/us/central-cancer-registry-reporting/STU1/CapabilityStatement-central-cancer-registry-reporting-ehr.html) for the HDEA to access patient data.,SHALL,EHR,"hl7.fhir.us.central-cancer-registry-reporting_1.0.0@32,34-44",false
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,55,https://www.hl7.org/fhir/us/central-cancer-registry-reporting/STU1/spec.html#authorization-requirements-1,The HDEA SHALL support the [Authentication and Authorization Requirements](https://www.hl7.org/fhir/us/central-cancer-registry-reporting/STU1/spec.html#authentication-and-authorization-requirements) outlined above as a client.,SHALL,HDEA,"hl7.fhir.us.central-cancer-registry-reporting_1.0.0@17,18",false
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,56,https://www.hl7.org/fhir/us/central-cancer-registry-reporting/STU1/spec.html#subscription-requirements-1,The HDEA SHALL create Subscriptions for the [encounter-end Subscription Topic](http://hl7.org/fhir/us/medmorph/STU1/StructureDefinition-medmorph-encounter-end-subscription.html),SHALL,HDEA,,false
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,57,https://www.hl7.org/fhir/us/central-cancer-registry-reporting/STU1/spec.html#subscription-requirements-1,The HDEA SHALL support [rest-hook](http://hl7.org/fhir/R4/subscription.html#2.46.7.1) Subscription channel to receive notifications from the EHR.,SHALL,HDEA,,false
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,58,https://www.hl7.org/fhir/us/central-cancer-registry-reporting/STU1/spec.html#subscription-notification-api,The HDEA SHALL support a POST API /receive-notification with a payload of the Subscription Notification Bundle to receive the notifications from the EHR,SHALL,HDEA,,true
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,59,https://www.hl7.org/fhir/us/central-cancer-registry-reporting/STU1/spec.html#knowledge-artifact-processing-requirements,The HDEA SHALL allow the healthcare organization to activate ... a specific Knowledge Artifact. Activation indicates applying the Knowledge Artifact ... for events occurring within the healthcare organization,SHALL,HDEA,,false
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,60,https://www.hl7.org/fhir/us/central-cancer-registry-reporting/STU1/spec.html#knowledge-artifact-processing-requirements,The HDEA SHALL allow the healthcare organization to … deactivate a specific Knowledge Artifact. …deactivation indicates not applying the Knowledge Artifact for events occurring within the healthcare organization,SHALL,HDEA,,false
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,61,https://www.hl7.org/fhir/us/central-cancer-registry-reporting/STU1/spec.html#knowledge-artifact-processing-requirements,HDEA SHALL process the MedMorph Central Cancer Registry Reporting Knowledge Artifact and create Subscription resources in the EHR for each trigger event.,SHALL,HDEA,,true
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,62,https://www.hl7.org/fhir/us/central-cancer-registry-reporting/STU1/spec.html#knowledge-artifact-processing-requirements,"For the Central Cancer Registry Reporting IG, the HDEA SHALL create the Subscription for the [encounter-close Subscription Topic](http://hl7.org/fhir/us/medmorph/STU1/StructureDefinition-medmorph-encounter-end-subscription.html) trigger event",SHALL,HDEA,,true
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,63,https://www.hl7.org/fhir/us/central-cancer-registry-reporting/STU1/spec.html#knowledge-artifact-processing-requirements,"Upon deactivation of a Knowledge Artifact, The HDEA SHALL delete the Subscriptions previously created by the BSA (Backend service app /aka HDEA) for the Knowledge Artifact. (e.g delete the Subscription created for encounter-close trigger event)",SHALL,HDEA,,true
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,64,https://www.hl7.org/fhir/us/central-cancer-registry-reporting/STU1/spec.html#knowledge-artifact-processing-requirements,The HDEA SHALL implement FhirPath expression processing to process the Central Cancer Registry Reporting Knowledge Artifact actions,SHALL,HDEA,,true
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,65,https://www.hl7.org/fhir/us/central-cancer-registry-reporting/STU1/spec.html#knowledge-artifact-processing-requirements,The HDEA SHALL use the default queries outlined by the Central Cancer Registry Reporting Knowledge Artifact unless overridden by the healthcare organization,SHALL,HDEA,,true
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,66,https://www.hl7.org/fhir/us/central-cancer-registry-reporting/STU1/spec.html#knowledge-artifact-processing-requirements,The HDEA SHALL ensure no duplicate reports are submitted for the same patient and encounter occurring within a healthcare organization,SHALL,HDEA,,true
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,67,https://www.hl7.org/fhir/us/central-cancer-registry-reporting/STU1/spec.html#data-api-requirements-1,The HDEA acting as a client SHALL use the APIs as outlined in the [EHR Capability Statement](https://www.hl7.org/fhir/us/central-cancer-registry-reporting/STU1/CapabilityStatement-central-cancer-registry-reporting-ehr.html) to access patient data from the EHR,SHALL,HDEA,"",false
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,68,https://www.hl7.org/fhir/us/central-cancer-registry-reporting/STU1/spec.html#report-generation-requirements,The HDEA SHALL create a central cancer registry report following the constraints  identified in Central [Cancer Registry Content Bundle](https://www.hl7.org/fhir/us/central-cancer-registry-reporting/STU1/StructureDefinition-ccrr-content-bundle.html),SHALL,HDEA,,false
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,69,https://www.hl7.org/fhir/us/central-cancer-registry-reporting/STU1/spec.html#report-generation-requirements,The HDEA SHALL package the central cancer registry report following the constraints identified [indicated by elements with the Must Support flag] in [Central Cancer Registry Reporting Bundle](https://www.hl7.org/fhir/us/central-cancer-registry-reporting/STU1/StructureDefinition-ccrr-reporting-bundle.html).,SHALL,HDEA,,false
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,70,https://www.hl7.org/fhir/us/central-cancer-registry-reporting/STU1/spec.html#report-generation-requirements,The HDEA SHALL submit the message containing the central cancer registry report to the endpoint identified in the MedMorph Central Cancer Registry Reporting Knowledge Artifact unless overridden by the healthcare organization,SHALL,HDEA,,true
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,71,https://www.hl7.org/fhir/us/central-cancer-registry-reporting/STU1/spec.html#report-generation-requirements,The HDEA SHALL submit the message containing the central cancer registry report to the endpoint identified in the MedMorph Central Cancer Registry Reporting Knowledge Artifact (when) overidden by the healthcare organization,SHALL NOT,HDEA,,true
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,72,https://www.hl7.org/fhir/us/central-cancer-registry-reporting/STU1/spec.html#medmorph-ra-requirements,The HDEA SHALL implement the MedMorph HDEA requirements as outlined in the [MedMorph HDEA requirements](http://hl7.org/fhir/us/medmorph/STU1/CapabilityStatement-medmorph-healthdata-exchange-app-client.html),SHALL,HDEA,,false
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,83,https://hl7.org/fhir/us/central-cancer-registry-reporting/STU1/StructureDefinition-ccrr-composition.html#guidance-on-populating-the-data-for-each-section,[The subject element of the [Central Cancer Registry Report Composition](https://hl7.org/fhir/us/central-cancer-registry-reporting/STU1/StructureDefinition-ccrr-composition.html) SHOULD be the] Patient who is the subject of the closed encounter,SHOULD,HDEA,,false
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,84,https://hl7.org/fhir/us/central-cancer-registry-reporting/STU1/StructureDefinition-ccrr-composition.html#guidance-on-populating-the-data-for-each-section,"[The encounter element of the [Central Cancer Registry Report Composition](https://hl7.org/fhir/us/central-cancer-registry-reporting/STU1/StructureDefinition-ccrr-composition.html) SHOULD be t]he encounter that triggered the HDEA (i.e, closed encounter)",SHOULD,HDEA,,false
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,85,https://hl7.org/fhir/us/central-cancer-registry-reporting/STU1/StructureDefinition-ccrr-composition.html#guidance-on-populating-the-data-for-each-section,[The] Primary Cancer Condition [section of the [Central Cancer Registry Report Composition](https://hl7.org/fhir/us/central-cancer-registry-reporting/STU1/StructureDefinition-ccrr-composition.html) SHOULD contain all] Condition[s] with a category of “encounter-diagnosis” for the closed encounter with a Condition.code value that is on the reportability list. All Conditions ... [which] do not have a clinicalStatuses of inactive can be considered to determine the primary cancer condition along with a verificationStatus of confirmed.,SHOULD,HDEA,,true
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,86,https://hl7.org/fhir/us/central-cancer-registry-reporting/STU1/StructureDefinition-ccrr-composition.html#guidance-on-populating-the-data-for-each-section,[The] Secondary Cancer Condition [section of the [Central Cancer Registry Report Composition](https://hl7.org/fhir/us/central-cancer-registry-reporting/STU1/StructureDefinition-ccrr-composition.html) SHOULD contain all] Condition[s] with a category of “encounter-diagnosis” for the closed encounter with a Condition.code that is present in the Secondary Cancer Disorder Value Set.All Conditions ... [which] do not have a clinicalStatuses of inactive can be considered to determine the primary cancer condition along with a verificationStatus of Confirmed,SHOULD,HDEA,,true
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,87,https://hl7.org/fhir/us/central-cancer-registry-reporting/STU1/StructureDefinition-ccrr-composition.html#guidance-on-populating-the-data-for-each-section,"[The] Cancer Stage Group [section of the [Central Cancer Registry Report Composition](https://hl7.org/fhir/us/central-cancer-registry-reporting/STU1/StructureDefinition-ccrr-composition.html) SHOULD contain a]ll Observations with the Cancer Stage Group information and a status of final, amended, or corrected",SHOULD,HDEA,,false
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,88,https://hl7.org/fhir/us/central-cancer-registry-reporting/STU1/StructureDefinition-ccrr-composition.html#guidance-on-populating-the-data-for-each-section,"[The [Central Cancer Registry Report Composition](https://hl7.org/fhir/us/central-cancer-registry-reporting/STU1/StructureDefinition-ccrr-composition.html) MAY contain all] TNM Primary Tumor Category: ... Observation with TNM tumor information having a status of final, amended, or corrected",SHOULD,HDEA,,false
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,89,https://hl7.org/fhir/us/central-cancer-registry-reporting/STU1/StructureDefinition-ccrr-composition.html#guidance-on-populating-the-data-for-each-section,"[The [Central Cancer Registry Report Composition](https://hl7.org/fhir/us/central-cancer-registry-reporting/STU1/StructureDefinition-ccrr-composition.html) MAY contain all] TNM Regional Nodes Category: ... Observation with TNM Regional Nodes information having a status of final, amended, or corrected",SHOULD,HDEA,,false
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,90,https://hl7.org/fhir/us/central-cancer-registry-reporting/STU1/StructureDefinition-ccrr-composition.html#guidance-on-populating-the-data-for-each-section,"[The [Central Cancer Registry Report Composition](https://hl7.org/fhir/us/central-cancer-registry-reporting/STU1/StructureDefinition-ccrr-composition.html) MAY contain all] TNM Distant Metastases Category: ... Observation with TNM Metastases information having a status of final, amended, or corrected",SHOULD,HDEA,,false
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,91,https://hl7.org/fhir/us/central-cancer-registry-reporting/STU1/StructureDefinition-ccrr-composition.html#guidance-on-populating-the-data-for-each-section,"[The] Radiotherapy Course Summary [section of the [Central Cancer Registry Report Composition](https://hl7.org/fhir/us/central-cancer-registry-reporting/STU1/StructureDefinition-ccrr-composition.html) SHOULD contain a]ll Procedures with the Radiotherapy course summary information having a status of completed, not-done, stopped, entered-in-error, unknown and a category of 108290001-Radiation Oncology and/or Radiotherapy (Procedure).",SHOULD,HDEA,,true
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,92,https://hl7.org/fhir/us/central-cancer-registry-reporting/STU1/StructureDefinition-ccrr-composition.html#guidance-on-populating-the-data-for-each-section,"[The Plan of Care section of the [Central Cancer Registry Report Composition](https://hl7.org/fhir/us/central-cancer-registry-reporting/STU1/StructureDefinition-ccrr-composition.html) SHOULD contain all] Cancer-Related Medication Request[s]: Medications requested during the closed encounter with a status of active, completed, cancelled, entered-in-error, stopped, unknown and an intent of order.",SHOULD,HDEA,,true
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,93,https://hl7.org/fhir/us/central-cancer-registry-reporting/STU1/StructureDefinition-ccrr-composition.html#guidance-on-populating-the-data-for-each-section,"[The Medications Administered section of the [Central Cancer Registry Report Composition](https://hl7.org/fhir/us/central-cancer-registry-reporting/STU1/StructureDefinition-ccrr-composition.html) SHOULD contain all] Cancer-Related Medication Administration: Medications administered during the closed encounter with a status of completed, in-progress, entered-in-error, stopped or unknown.",SHOULD,HDEA,,true
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,94,https://hl7.org/fhir/us/central-cancer-registry-reporting/STU1/StructureDefinition-ccrr-composition.html#guidance-on-populating-the-data-for-each-section,[The ODH section of the [Central Cancer Registry Report Composition](https://hl7.org/fhir/us/central-cancer-registry-reporting/STU1/StructureDefinition-ccrr-composition.html) SHOULD contain all] Usual Work information for the patient with a status of final.,SHOULD,HDEA,,false
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,95,https://hl7.org/fhir/us/central-cancer-registry-reporting/STU1/StructureDefinition-ccrr-composition.html#guidance-on-populating-the-data-for-each-section,[The Results section of the [Central Cancer Registry Report Composition](https://hl7.org/fhir/us/central-cancer-registry-reporting/STU1/StructureDefinition-ccrr-composition.html) SHOULD contain all r]esults linked to the encounter or ordered during the encounter or results received during the Encounter with a status of final,SHOULD,HDEA,,true
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,96,https://hl7.org/fhir/us/central-cancer-registry-reporting/STU1/StructureDefinition-ccrr-composition.html#guidance-on-populating-the-data-for-each-section,"[The Vital Signs section of the [Central Cancer Registry Report Composition](https://hl7.org/fhir/us/central-cancer-registry-reporting/STU1/StructureDefinition-ccrr-composition.html) SHOULD contain a]ll vital signs for the encounter with a status of final, corrected, unknown or amended",SHOULD,HDEA,,false
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,97,https://hl7.org/fhir/us/central-cancer-registry-reporting/STU1/StructureDefinition-ccrr-composition.html#guidance-on-populating-the-data-for-each-section,[The Procedures section of the [Central Cancer Registry Report Composition](https://hl7.org/fhir/us/central-cancer-registry-reporting/STU1/StructureDefinition-ccrr-composition.html) SHOULD contain all p]rocedures performed during the closed encounter with a status of completed or unknown.,SHOULD,HDEA,,true
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,98,https://hl7.org/fhir/us/central-cancer-registry-reporting/STU1/StructureDefinition-ccrr-composition.html#guidance-on-populating-the-data-for-each-section,[The Results section of the [Central Cancer Registry Report Composition](https://hl7.org/fhir/us/central-cancer-registry-reporting/STU1/StructureDefinition-ccrr-composition.html) SHOULD contain all] DiagnosticReport Profile for Laboratory Results Reporting [instances representing r]esults linked to the encounter or ordered during the encounter or results received during the Encounter and a Status of final,SHOULD,HDEA,,true
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,99,https://hl7.org/fhir/us/central-cancer-registry-reporting/STU1/StructureDefinition-ccrr-composition.html#guidance-on-populating-the-data-for-each-section,[The Notes section of the [Central Cancer Registry Report Composition](https://hl7.org/fhir/us/central-cancer-registry-reporting/STU1/StructureDefinition-ccrr-composition.html) SHOULD contain all] DiagnosticReport Profile for Report and Note exchange [instances representing r]esults linked to the encounter or ordered during the encounter or results received during the Encounter and a Status of final,SHOULD,HDEA,,true
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,100,https://hl7.org/fhir/us/central-cancer-registry-reporting/STU1/StructureDefinition-ccrr-composition.html#guidance-on-populating-the-data-for-each-section,[The Notes section of the [Central Cancer Registry Report Composition](https://hl7.org/fhir/us/central-cancer-registry-reporting/STU1/StructureDefinition-ccrr-composition.html) SHOULD contain all] DocumentReference [instances representing] ... notes created during the encounter with a status of current,SHOULD,HDEA,,false
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,101,https://hl7.org/fhir/us/central-cancer-registry-reporting/STU1/StructureDefinition-ccrr-composition.html#guidance-on-populating-the-data-for-each-section,[The Social History section of the [Central Cancer Registry Report Composition](https://hl7.org/fhir/us/central-cancer-registry-reporting/STU1/StructureDefinition-ccrr-composition.html) SHOULD contain all] Smoking Status [Observations] associated with the patient with a status of final.,SHOULD,HDEA,,false
+hl7.fhir.us.central-cancer-registry-reporting_1.0.0,102,https://www.hl7.org/fhir/us/central-cancer-registry-reporting/STU1/spec.html#must-support-definition,[HDEA] Systems SHALL be capable of populating data elements as specified by the profiles  [with the must support flag],SHALL,HDEA,,true
+hl7.fhir.us.mcode_3.0.0,2,https://hl7.org/fhir/us/mcode/STU3/StructureDefinition-mcode-primary-cancer-condition.html,"Cancers that are not clearly secondary (i.e., of uncertain origin or behavior) should be documented as primary.",SHOULD,EHR,,
+hl7.fhir.us.mcode_3.0.0,3,https://hl7.org/fhir/us/mcode/STU3/StructureDefinition-mcode-primary-cancer-condition.html#usage,Staging information SHALL be captured in an Observation that conforms to the StageGroup profile,SHALL,EHR,,
+hl7.fhir.us.mcode_3.0.0,4,https://hl7.org/fhir/us/mcode/STU3/StructureDefinition-mcode-primary-cancer-condition.html#usage,"Stage group MAY appear in [Primary Cancer Condition Profile], in stage.summary and stage.type",MAY,EHR,,
+hl7.fhir.us.mcode_3.0.0,5,https://hl7.org/fhir/us/mcode/STU3/StructureDefinition-mcode-primary-cancer-condition.html#usage,"[If the Stage Group appears in the Primary Cancer Condition Profile], mCODE Data Senders ... MAY ignore it in favor of the TNMStageGroup Observation",MAY,EHR,,true
+hl7.fhir.us.mcode_3.0.0,7,https://hl7.org/fhir/us/mcode/STU3/StructureDefinition-mcode-primary-cancer-condition.html#usage,"If present, cancer staging information summarized in this profile should reflect the most recent staging assessment on the patient",SHOULD,EHR,,true
+hl7.fhir.us.mcode_3.0.0,8,https://hl7.org/fhir/us/mcode/STU3/StructureDefinition-mcode-primary-cancer-condition.html#usage,"If present, cancer staging information summarized in this profile … should be updated if and when there is a new staging assessment.",SHOULD,EHR,,true
+hl7.fhir.us.mcode_3.0.0,9,https://hl7.org/fhir/us/mcode/STU3/StructureDefinition-mcode-primary-cancer-condition.html#usage,"For SNOMED CT coding [of cancer conditions], use a code from the disorder hierarchy under SNOMED CT 363346000 ‘Malignant neoplastic disease (disorder)’ excluding codes descending from SNOMED CT 128462008 ‘Secondary malignant neoplastic disease (disorder)’.",SHALL,EHR,,true
+hl7.fhir.us.mcode_3.0.0,10,https://hl7.org/fhir/us/mcode/STU3/StructureDefinition-mcode-primary-cancer-condition.html#usage,"For SNOMED CT coding [of cancer conditions]... if body location is not [implied by the code], the site of the primary tumor should be specified in the body site attribute.",SHOULD,EHR,,true
+hl7.fhir.us.mcode_3.0.0,11,https://hl7.org/fhir/us/mcode/STU3/StructureDefinition-mcode-primary-cancer-condition.html#usage,"For ICD-10-CM coding [of cancer conditions], use one of the codes given in this value set representing primary malignant neoplasms and neoplasms of uncertain or unspecified behavior.",SHALL,EHR,,true
+hl7.fhir.us.mcode_3.0.0,12,https://hl7.org/fhir/us/mcode/STU3/StructureDefinition-mcode-primary-cancer-condition.html#usage,"If ICD-O-3 is used [to code cancer conditions], the primary cancer disorder code must be specifically be SNOMED CT 363346000 ‘Malignant neoplastic disease (disorder)’.",SHALL,EHR,,true
+hl7.fhir.us.mcode_3.0.0,13,https://hl7.org/fhir/us/mcode/STU3/StructureDefinition-mcode-primary-cancer-condition.html#usage,"[When using ICD-O-3 encoding of cancer conditions, t]he ICD-O-3 morphology and topography codes should be entered in the HistologyMorphologyBehavior and body location fields, respectively.",SHOULD,EHR,,true
+hl7.fhir.us.mcode_3.0.0,14,https://hl7.org/fhir/us/mcode/STU3/StructureDefinition-mcode-primary-cancer-condition.html#conformance,Condition resources associated with an in-scope patient with a Condition.code in the value set PrimaryCancerDisorderVS SHALL conform to this profile.,SHALL,EHR,,
+hl7.fhir.us.mcode_3.0.0,15,https://hl7.org/fhir/us/mcode/STU3/StructureDefinition-mcode-primary-cancer-condition.html#conformance,A producer of resources SHOULD ensure that any resource instance associated with an in-scope patient that would reasonably be expected to conform to this profile SHOULD be published in this form,SHOULD,EHR,,
+hl7.fhir.us.mcode_3.0.0,16,https://hl7.org/fhir/us/mcode/STU3/conformance-general.html#follow-conformance-requirements-for-supported-profiles,Senders ... must conform to the expectations set [by mCode profiles],SHALL,EHR,,
+hl7.fhir.us.mcode_3.0.0,22,https://hl7.org/fhir/us/mcode/STU3/conformance-profiles.html#profile-level-conformance-expectations,The list of implemented profiles SHALL be published in a CapabilityStatement.,SHALL,EHR,,
+hl7.fhir.us.mcode_3.0.0,23,https://hl7.org/fhir/us/mcode/STU3/conformance-profiles.html#profile-level-conformance-expectations,The list of implemented profiles SHALL be published in a CapabilityStatement.,SHALL,mCode Data Receiver,,
+hl7.fhir.us.mcode_3.0.0,24,https://hl7.org/fhir/us/mcode/STU3/conformance-profiles.html#profile-level-conformance-expectations,"For each implemented profile, a Data Sender SHALL follow that profile’s conformance statement describing what data SHALL or SHOULD conform to that profile",SHALL,EHR,,
+hl7.fhir.us.mcode_3.0.0,25,https://hl7.org/fhir/us/mcode/STU3/conformance-profiles.html#profile-level-conformance-expectations,Support of data elements that reference other profiles MAY require implementers to support additional profiles,MAY,EHR,,
+hl7.fhir.us.mcode_3.0.0,27,https://hl7.org/fhir/us/mcode/STU3/conformance-profiles.html#profile-level-conformance-expectations,A Sender has the responsibility for creating instances that... must pass validation against the selected profile.,SHALL,EHR,,
+hl7.fhir.us.mcode_3.0.0,30,https://hl7.org/fhir/us/mcode/STU3/conformance-profiles.html#profile-level-conformance-expectations,Every Data Sender SHOULD populate [meta.profile] in each instance,SHOULD,EHR,,
+hl7.fhir.us.mcode_3.0.0,31,https://hl7.org/fhir/us/mcode/STU3/conformance-profiles.html#implementing-a-data-element,"[If a data sender is not playing a limited role limited or specialized role in clinical or information workflows], a Data Sender SHALL be capable of populating [an implemented mCode data] element",SHALL,EHR,,true
+hl7.fhir.us.mcode_3.0.0,32,https://hl7.org/fhir/us/mcode/STU3/conformance-profiles.html#implementing-a-data-element,"If the [implemented data] element’s minimum cardinality is greater than zero, and the Sender lacks the data necessary to populate the element, then the US Core rules on missing data SHALL be followed",SHALL,EHR,,true
+hl7.fhir.us.mcode_3.0.0,33,https://hl7.org/fhir/us/mcode/STU3/conformance-profiles.html#implementing-a-data-element,"If the [implemented data]  element’s minimum cardinality is zero and the Sender lacks the data necessary to populate the element, the element SHOULD be entirely omitted.",SHOULD,EHR,,true
+hl7.fhir.us.mcode_3.0.0,34,https://hl7.org/fhir/us/mcode/STU3/conformance-profiles.html#implementing-a-data-element,"If there is a specific reason the data is missing [for an implemented data element with a minimum cardiinality of zero], a data absent reason MAY be substituted",MAY,EHR,,true
+hl7.fhir.us.mcode_3.0.0,35,https://hl7.org/fhir/us/mcode/STU3/conformance-profiles.html#implementing-a-data-element,[If the implemented data element's mimum cardinality is greater than zero] Senders SHALL NOT substitute nonsense or filler values for missing values.,SHALL NOT,EHR,,
+hl7.fhir.us.mcode_3.0.0,37,https://hl7.org/fhir/us/mcode/STU3/conformance-profiles.html#must-implement-versus-must-support,"Outside of data elements that must be implemented, additional data elements MAY be implemented.",MAY,EHR,,
+hl7.fhir.us.mcode_3.0.0,38,https://hl7.org/fhir/us/mcode/STU3/conformance-profiles.html#must-implement-versus-must-support,"If a data element is implemented [outside of the ones that must be implemented], the profile must be interpreted as if an MS flag were present on that element.",SHALL,EHR,,true
+hl7.fhir.us.mcode_3.0.0,39,https://hl7.org/fhir/us/mcode/STU3/conformance-profiles.html#must-implement-versus-must-support,"An implementer SHALL implement data elements that are considered as ""Must Implement"", which means that they are in implemented profiles (as declared in the Sender's Capability Statement)",SHALL,EHR,,
+hl7.fhir.us.mcode_3.0.0,43,https://hl7.org/fhir/us/mcode/STU3/conformance-profiles.html#must-implement-rules,"For an implemented profile, a top-level element with an MS flag SHALL be implemented.",SHALL,"EHR, mCode Data Receiver",,
+hl7.fhir.us.mcode_3.0.0,44,https://hl7.org/fhir/us/mcode/STU3/conformance-profiles.html#must-implement-rules,"For an implemented profile,  A nested element (at the second-level or below) with MS flag whose parents all are implemented SHALL be implemented. This includes parent elements that have been implemented electively.",SHALL,"EHR, mCode Data Receiver",,
+hl7.fhir.us.mcode_3.0.0,45,https://hl7.org/fhir/us/mcode/STU3/conformance-profiles.html#must-implement-rules,"For an implemented profile, An element whose cardinality is 0..0 does NOT need to be implemented, regardless of MS flag",SHALL NOT,"EHR, mCode Data Receiver",,
+hl7.fhir.us.mcode_3.0.0,46,https://hl7.org/fhir/us/mcode/STU3/conformance-profiles.html#must-implement-rules,"For an implemented profile, a required element SHALL be implemented, regardless of whether that element has an MS flag.",SHALL,"EHR, mCode Data Receiver",,
+hl7.fhir.us.mcode_3.0.0,48,https://hl7.org/fhir/us/mcode/STU3/conformance-profiles.html#definition-of-required,An mCODE data element is required if ... The element is a top-level element and its minimum cardinality is > 0 in the profile,SHALL,"EHR, mCode Data Receiver",,
+hl7.fhir.us.mcode_3.0.0,49,https://hl7.org/fhir/us/mcode/STU3/conformance-profiles.html#definition-of-required,"An mCODE data element is required if... the element is not a top-level element (a second-level property or below), its minimum cardinality is > 0, and all elements directly containing that element have minimum cardinality > 0 in the profile.",SHALL,"EHR, mCode Data Receiver",,
+hl7.fhir.us.mcode_3.0.0,50,https://hl7.org/fhir/us/mcode/STU3/conformance-profiles.html#must-implement-summary,"If an MS element is a complex data type (such as a CodeableConcept) with no MS flag on any immediate sub-element, the data sender SHALL implement at least one sub-element",SHALL,EHR,,
+hl7.fhir.us.mcode_3.0.0,51,https://hl7.org/fhir/us/mcode/STU3/conformance-profiles.html#must-implement-summary,"If an MS element is a complex data type (such as a CodeableConcept) with no MS flag on any immediate sub-element, the data sender SHOULD implement every sub-element for which the server might possess data",SHOULD,EHR,,
+hl7.fhir.us.mcode_3.0.0,53,https://hl7.org/fhir/us/mcode/STU3/conformance-profiles.html#must-implement-summary,"If an MS element is a complex data type (such as a CodeableConcept) with an MS flag on one or more immediate sub-elements, the sub-elements that are explicitly flagged SHALL be implemented",SHALL,"EHR, mCode Data Receiver",,
+hl7.fhir.us.mcode_3.0.0,54,https://hl7.org/fhir/us/mcode/STU3/conformance-profiles.html#must-implement-summary,"If an MS element is a choice[x] type  with no MS flag on any choice, the data sender SHALL implement at least one datatype choice",SHALL,EHR,,
+hl7.fhir.us.mcode_3.0.0,55,https://hl7.org/fhir/us/mcode/STU3/conformance-profiles.html#must-implement-summary,"If an MS element is a choice[x] type  with no MS flag on any choice, the data sender SHOULD implement every datatype for which the server might possess data",SHOULD,EHR,,
+hl7.fhir.us.mcode_3.0.0,57,https://hl7.org/fhir/us/mcode/STU3/conformance-profiles.html#must-implement-summary,"If an MS element is a choice[x] with an MS flag on one or more choice, the datatype choice(s) that are explicitly flagged SHALL be implemented",SHALL,"EHR, mCode Data Receiver",,
+hl7.fhir.us.mcode_3.0.0,58,https://hl7.org/fhir/us/mcode/STU3/conformance-profiles.html#must-implement-summary,"If an MS element is a Reference() data type with no MS flag on any reference resource or profile, the data sender SHALL implement all resources or profiles in the reference that are in the Sender's capability statement",SHALL,EHR,,
+hl7.fhir.us.mcode_3.0.0,60,https://hl7.org/fhir/us/mcode/STU3/conformance-profiles.html#must-implement-summary,"If an MS element is a Reference() data type with an MS flag on one or more of the referenced types, the data sender SHALL implement the resources or profiles that are explicitly flagged and in the  Sender's capability statement",SHALL,EHR,,
+hl7.fhir.us.mcode_3.0.0,62,https://hl7.org/fhir/us/mcode/STU3/conformance-profiles.html#must-implement-summary,"If an MS element is an array that is sliced, with no MS flag on any slice, the data sender SHALL be able to populate the array, with no requriement on implementing a particular slice",SHALL,EHR,,
+hl7.fhir.us.mcode_3.0.0,64,https://hl7.org/fhir/us/mcode/STU3/conformance-profiles.html#must-implement-summary,"If an MS element is an array that is sliced, with MS flags on one or more slices, actor SHALL implement the slices that have MS flags",SHALL,"EHR, mCode Data Receiver",,
+hl7.fhir.us.mcode_3.0.0,65,https://hl7.org/fhir/us/mcode/STU3/StructureDefinition-mcode-secondary-cancer-condition.html#usage,"For SNOMED CT coding [of secondary cancer conditions], use a code from the disorder hierarchy under secondary malignant neoplastic disease (SNOMED CT 128462008)",SHALL,EHR,,true
+hl7.fhir.us.mcode_3.0.0,66,https://hl7.org/fhir/us/mcode/STU3/StructureDefinition-mcode-secondary-cancer-condition.html#usage,"For ICD-10-CM coding [of secondary cancer conditions], use one of the codes given in this value set representing secondary  malignant neoplasms and neoplasms of uncertain or unspecified behavior.",SHALL,EHR,,true
+hl7.fhir.us.mcode_3.0.0,67,https://hl7.org/fhir/us/mcode/STU3/StructureDefinition-mcode-secondary-cancer-condition.html#usage,"For ICD-10-CM coding [of secondary cancer conditions],... If body site is not precoordinated (implied by the code), it should be specified separately using the body location.",SHOULD,EHR,,true
+hl7.fhir.us.mcode_3.0.0,68,https://hl7.org/fhir/us/mcode/STU3/StructureDefinition-mcode-secondary-cancer-condition.html#usage,"If ICD-O-3 is used [for coding of secondary cancer conditions], the disorder code must be specifically be SNOMED CT 128462008 (Secondary malignant neoplastic disease)",SHALL,EHR,,true
+hl7.fhir.us.mcode_3.0.0,69,https://hl7.org/fhir/us/mcode/STU3/StructureDefinition-mcode-secondary-cancer-condition.html#usage,"If ICD-O-3 is used [for coding of secondary cancer conditions], the ICD-O-3 morphology and topography codes should be entered in the HistologyMorphologyBehavior and body location fields, respectively.",SHOULD,EHR,,true
+hl7.fhir.us.mcode_3.0.0,70,https://hl7.org/fhir/us/mcode/STU3/StructureDefinition-mcode-secondary-cancer-condition.html#conformance,Condition resources associated with an in-scope patient with a Condition.code in the value set SecondaryCancerDisorderVS SHALL conform to this profile.,SHALL,EHR,,
+hl7.fhir.us.mcode_3.0.0,71,https://hl7.org/fhir/us/mcode/STU3/StructureDefinition-mcode-secondary-cancer-condition.html#conformance,A producer of resources SHOULD ensure that any resource instance associated with an in-scope patient that would reasonably be expected to conform to this [secondary cancer condition] profile SHOULD be published in this form,SHOULD,EHR,,
+hl7.fhir.us.mcode_3.0.0,72,https://hl7.org/fhir/us/mcode/STU3/StructureDefinition-mcode-secondary-cancer-condition.html#conformance,Any resource intended to conform to this profile SHOULD populate meta.profile ,SHOULD,EHR,,
+hl7.fhir.us.mcode_3.0.0,73,https://hl7.org/fhir/us/mcode/STU3/StructureDefinition-mcode-tnm-stage-group.html#conformance,"Observation resources associated with an in-scope patient with Observation.code of LOINC 21908-9, 21902-2, or 21914-7 SHALL conform to this profile.",SHALL,EHR,,
+hl7.fhir.us.mcode_3.0.0,74,https://hl7.org/fhir/us/mcode/STU3/StructureDefinition-mcode-tnm-stage-group.html#conformance,A producer of resources SHOULD ensure that any resource instance associated with an mCode patient that would reasonably be expected to conform to this profile SHOULD be published in this form,SHOULD,EHR,,
+hl7.fhir.us.mcode_3.0.0,75,https://hl7.org/fhir/us/mcode/STU3/StructureDefinition-mcode-tnm-distant-metastases-category.html#conformance,"Observation resources associated with an in-scope patient with Observation.code of LOINC 21907-1, 21901-4, 21913-9 SHALL conform to this profile.",SHALL,EHR,,
+hl7.fhir.us.mcode_3.0.0,76,https://hl7.org/fhir/us/mcode/STU3/StructureDefinition-mcode-tnm-distant-metastases-category.html#conformance,A producer of resources SHOULD ensure that any resource instance associated with an mCode patient that would reasonably be expected to conform to this profile SHOULD be published in this form,SHOULD,EHR,,
+hl7.fhir.us.mcode_3.0.0,77,https://hl7.org/fhir/us/mcode/STU3/StructureDefinition-mcode-tnm-primary-tumor-category.html#conformance,"Observation resources associated with an in-scope patient with Observation.code of LOINC 21905-5, 21899-0, 21911-3 SHALL conform to this profile.",SHALL,EHR,,
+hl7.fhir.us.mcode_3.0.0,78,https://hl7.org/fhir/us/mcode/STU3/StructureDefinition-mcode-tnm-primary-tumor-category.html#conformance,A producer of resources SHOULD ensure that any resource instance associated with an mCode patient that would reasonably be expected to conform to this profile SHOULD be published in this form,SHOULD,EHR,,
+hl7.fhir.us.mcode_3.0.0,79,https://hl7.org/fhir/us/mcode/STU3/StructureDefinition-mcode-tnm-regional-nodes-category.html#conformance,"Observation resources associated with an in-scope patient with Observation.code of LOINC 21906-3, 21900-6, or 21912-1 SHALL conform to this profile.",SHALL,EHR,,
+hl7.fhir.us.mcode_3.0.0,80,https://hl7.org/fhir/us/mcode/STU3/StructureDefinition-mcode-tnm-regional-nodes-category.html#conformance,A producer of resources SHOULD ensure that any resource instance associated with an mCode patient that would reasonably be expected to conform to this profile SHOULD be published in this form,SHOULD,EHR,,
+hl7.fhir.us.mcode_3.0.0,83,https://hl7.org/fhir/us/mcode/STU3/StructureDefinition-mcode-cancer-related-medication-administration.html#conformance,MedicationAdministration resources associated with an in-scope patient SHALL conform to this profile.,SHALL,EHR,,
+hl7.fhir.us.mcode_3.0.0,84,https://hl7.org/fhir/us/mcode/STU3/StructureDefinition-mcode-cancer-related-medication-administration.html#conformance,A producer of resources SHOULD ensure that any resource instance associated with an in-scope patient that would reasonably be expected to conform to this profile SHOULD be published in this form.,SHOULD,EHR,,
+hl7.fhir.us.mcode_3.0.0,85,https://hl7.org/fhir/us/mcode/STU3/StructureDefinition-mcode-radiotherapy-course-summary.html#conformance,Procedure resources whose code is mcode-radiotherapy-course-summary (code system http://hl7.org/fhir/us/mcode/CodeSystem/mcode-resource-identifier-cs) SHALL conform to this profile,SHALL,EHR,,
+hl7.fhir.us.mcode_3.0.0,86,https://hl7.org/fhir/us/mcode/STU3/StructureDefinition-mcode-radiotherapy-course-summary.html#conformance,a producer of resources SHOULD ensure that any resource instance associated with an in-scope patient that would reasonably be expected to conform to this profile SHOULD be published in this form,SHOULD,EHR,,
+hl7.fhir.us.mcode_3.0.0,87,https://hl7.org/fhir/us/mcode/STU3/StructureDefinition-mcode-radiotherapy-course-summary.html#conformance,Any resource intended to conform to this profile SHOULD populate meta.profile,SHOULD,EHR,,
+hl7.fhir.us.mcode_3.0.0,88,https://hl7.org/fhir/us/mcode/STU3/group-disease.html#representing-the-cancer-diagnosis,"If using the ICD-O-3 morphology code, it should have the form HHHH/B G where HHHH is the 4-digit histology code, B is the 1-digit behavior code (i.e., /1, /2, or /3 suffix for primary cancers, and /6 suffix for secondary cancers), and G is the grade or equivalent in leukemias and lymphomas (1 digit)",SHOULD,EHR,,true
+hl7.fhir.us.mcode_3.0.0,89,https://hl7.org/fhir/us/mcode/STU3/group-disease.html#clinical-status,"On initial diagnosis, the Condition.clinicalStatus element [SHALL]  be active",SHALL,EHR,,
+hl7.fhir.us.mcode_3.0.0,90,https://hl7.org/fhir/us/mcode/STU3/group-disease.html#clinical-status,Subsequent changes to the disease status should be recorded by updating the Condition.clinicalStatus element,SHOULD,EHR,,
+hl7.fhir.us.mcode_3.0.0,91,https://hl7.org/fhir/us/mcode/STU3/group-disease.html#clinical-status,"When the value of CancerDiseaseStatus indicates remission, the Condition.clinicalStatus should be updated to reflect that finding.",SHOULD,EHR,,
+hl7.fhir.us.mcode_3.0.0,92,https://hl7.org/fhir/us/mcode/STU3/group-disease.html#how-to-report-staging-information,CancerStage is a parent profile that should be used only if a more specific profile corresponding to a particular staging system is unavailable,SHOULD,EHR,,
+hl7.fhir.us.mcode_3.0.0,93,https://hl7.org/fhir/us/mcode/STU3/group-disease.html#how-to-report-staging-information,In the CancerStage profile and its descendants... Observation.method [MAY also be used] if the staging system is implicit in Observation.code.,MAY,EHR,,true
+hl7.fhir.us.mcode_3.0.0,94,https://hl7.org/fhir/us/mcode/STU3/group-disease.html#staging,"The data sender must assure that [for staging Observations] the values in these three fields (Observation.code, Observation.method, and Observation.valueCodeableConcept) are self-consistent",SHALL,EHR,,
+hl7.fhir.us.mcode_3.0.0,95,https://hl7.org/fhir/us/mcode/STU3/group-disease.html#tnm-staging,mCODE strongly recommends that the implementers align with AJCC’s convention of representing the staging category value including the classification prefix.,SHOULD,EHR,,
+hl7.fhir.us.mcode_3.0.0,96,https://hl7.org/fhir/us/mcode/STU3/group-disease.html#tnm-staging,"If using the AJCC's convention of represeting staging category, the selected prefix SHALL be consistent with the Observation.code value.",SHALL,EHR,,true
+hl7.fhir.us.mcode_3.0.0,97,https://hl7.org/fhir/us/mcode/STU3/group-disease.html#non-tnm-staging,Prognostic factors related to the cancer stage group can be specified with the Observation.derivedFrom element,MAY,EHR,,
+hl7.fhir.us.mcode_3.0.0,98,https://hl7.org/fhir/us/mcode/STU3/group-disease.html#summary-stage-information-in-primarycancercondition,Representing stage information in PrimaryCancerCondition without an explicit staging system [MAY be used] only if the staging system is implicit in the stage type (Condition.stage.type),MAY,EHR,,
+hl7.fhir.us.mcode_3.0.0,99,https://hl7.org/fhir/us/mcode/STU3/conformance-general.html#populate-and-meaningfully-process-mcode-resources,"mCODE Senders MUST be able to populate data elements Must-Support (MS) obligations, for all profiles they support (as declared in their CapabilityStatement).",SHALL,EHR,,
+hl7.fhir.us.mcode_3.0.0,101,https://hl7.org/fhir/us/mcode/STU3/conformance-general.html#publish-a-capabilitystatement-identifying-supported-profiles-and-operations,"Each mCODE participant SHALL publish a FHIR CapabilityStatement listing their supported profiles, by declaring the profile in CapabilityStatement.rest.resource.supportedProfile.",SHALL,EHR,,
+hl7.fhir.us.mcode_3.0.0,103,https://hl7.org/fhir/us/mcode/STU3/conformance-general.html#publish-a-capabilitystatement-identifying-supported-profiles-and-operations,The CapabilityStatement SHALL be returned in response to a GET [base]/metadata request.,SHALL,EHR,,
+hl7.fhir.us.mcode_3.0.0,107,https://hl7.org/fhir/us/mcode/STU3/conformance-general.html#support-us-core-conformance-requirements,Conformance requirements from US Core [SHALL] apply to RESTful interactions... in mCode,SHALL,"EHR, mCode Data Receiver",,
+hl7.fhir.us.mcode_3.0.0,108,https://hl7.org/fhir/us/mcode/STU3/conformance-general.html#support-us-core-conformance-requirements,Conformance requirements from US Core [SHALL] apply to... Searches... In mCode,SHALL,"EHR, mCode Data Receiver",,
+hl7.fhir.us.mcode_3.0.0,109,https://hl7.org/fhir/us/mcode/STU3/conformance-general.html#support-us-core-conformance-requirements,Conformance requirements from US Core [SHALL] apply to... Resource formats in mCode,SHALL,"EHR, mCode Data Receiver",,
+hl7.fhir.us.mcode_3.0.0,110,https://hl7.org/fhir/us/mcode/STU3/conformance-general.html#support-us-core-conformance-requirements,"mCODE “inherits” all US Core conformance requirements, [so implementers SHALL implement all US Core conformance requirements]",SHALL,"EHR, mCode Data Receiver",,