Validation Results for ScalableConsentManagement

Generated Wed May 27 15:41:50 UTC 2026, FHIR version 4.0.1 for hl7.fhir.us.consent-management#1.0.0-preview (canonical = http://hl7.org/fhir/us/consent-management (history)). See Full QA Report & IP

Quality Checks
Publisher Version:	IG Publisher Version: v2.2.8
Publication Code:	consent-management . PackageId = hl7.fhir.us.consent-management, Canonical = http://hl7.org/fhir/us/consent-management
Realm Check for US:	Snomed: The IG doesn't use SNOMED CT Profiles: All OK
Language Info:	Stated Languages: n/a. IG Resource Lang: en. 1 of 47 (2%) of resources have a language. Population Policy: NONE
Publication Request:	package-id hl7.fhir.us.consent-management version 1.0.0-preview path http://hl7.org/fhir/us/consent-management/2026Jan Pub-Mode working release status preview Release-Label STU 1 PReview Sequence (Group) STU 1 (current: n/a, others = 'STU 1') desc A FHIR IG that provides APIs for managing consent at scale across multiple consent management repositories. RelatedIgs (None Found) A publication already exists at http://hl7.org/fhir/us/consent-management/2026Jan Proposed path for this publication should usually be the canonical with the version or sequence appended and then some kind of label (typically '-snapshot')
Supressed Messages:	57 Suppressed Issues
Dependency Checks:	Package Version FHIR Canonical Web Base Comment hl7.fhir.us.consent-management 1.0.0-preview R4 http://hl7.org/fhir/us/consent-management hl7.terminology.r4 7.1.0 M R4 http://terminology.hl7.org http://terminology.hl7.org/7.1.0 hl7.fhir.uv.extensions.r4 5.2.0 O R4 http://hl7.org/fhir/extensions http://hl7.org/fhir/extensions/5.2.0 Latest Release is 5.3.0 hl7.fhir.uv.extensions.r4 5.3.0 M R4 http://hl7.org/fhir/extensions http://hl7.org/fhir/extensions/5.3.0 hl7.terminology.r4 7.1.0 M R4 http://terminology.hl7.org http://terminology.hl7.org/7.1.0 (as above) hl7.fhir.us.core 6.1.0 O R4 http://hl7.org/fhir/us/core http://hl7.org/fhir/us/core/STU6.1 Latest Release is 8.0.1 hl7.terminology.r4 5.0.0 O R4 http://terminology.hl7.org http://terminology.hl7.org/5.0.0 Latest Release is 7.1.0 hl7.fhir.uv.extensions.r4 1.0.0 O R4 http://hl7.org/fhir/extensions http://hl7.org/fhir/extensions/1.0.0 Latest Release is 5.3.0 hl7.fhir.uv.bulkdata 2.0.0 O R4 http://hl7.org/fhir/uv/bulkdata http://hl7.org/fhir/uv/bulkdata/STU2 Latest Release is 3.0.0 hl7.fhir.uv.smart-app-launch 2.1.0 O R4 http://hl7.org/fhir/smart-app-launch http://hl7.org/fhir/smart-app-launch/STU2.1 Latest Release is 2.2.0 hl7.terminology.r4 5.0.0 O R4 http://terminology.hl7.org http://terminology.hl7.org/5.0.0 (as above). Latest Release is 7.1.0 us.nlm.vsac 0.11.0 O R4 http://fhir.org/packages/us.nlm.vsac http://fhir.org/packages/us.nlm.vsac Latest Release is 0.24.0 hl7.fhir.uv.sdc 3.0.0 O R4 http://hl7.org/fhir/uv/sdc http://hl7.org/fhir/uv/sdc/STU3 Latest Release is 4.0.0 hl7.fhir.r4.examples 4.0.1 O R4 http://hl7.org/fhir http://hl7.org/fhir/R4 Latest Release is 5.0.0 us.cdc.phinvads 0.12.0 M R4 http://fhir.org/packages/us.cdc.phinvads http://fhir.org/packages/us.cdc.phinvads ihe.formatcode.fhir 1.1.0 O R4 https://profiles.ihe.net/fhir/ihe.formatcode.fhir https://profiles.ihe.net/fhir/ihe.formatcode.fhir/1.1.0 Latest Release is 1.5.0 hl7.fhir.uv.subscriptions-backport.r4 1.1.0 M R4 http://hl7.org/fhir/uv/subscriptions-backport http://hl7.org/fhir/uv/subscriptions-backport/STU1.1 FHIR Version Mismatch hl7.terminology.r4 5.0.0 O R4 http://terminology.hl7.org http://terminology.hl7.org/5.0.0 (as above). Latest Release is 7.1.0 ihe.iti.pcf 1.1.0 M R4 https://profiles.ihe.net/ITI/PCF https://profiles.ihe.net/ITI/PCF/1.1.0 hl7.terminology.r4 5.3.0 O R4 http://terminology.hl7.org http://terminology.hl7.org/5.3.0 Latest Release is 7.1.0 hl7.fhir.uv.extensions.r4 1.0.0 O R4 http://hl7.org/fhir/extensions http://hl7.org/fhir/extensions/1.0.0 (as above). Latest Release is 5.3.0 us.nlm.vsac 0.9.0 O R4 http://fhir.org/packages/us.nlm.vsac http://fhir.org/packages/us.nlm.vsac Latest Release is 0.24.0 ihe.iti.balp 1.1.4 M R4 https://profiles.ihe.net/ITI/BALP https://profiles.ihe.net/ITI/BALP/1.1.4 Matched to latest patch release (1.1.x->1.1.4) hl7.terminology.r4 6.5.0 O R4 http://terminology.hl7.org http://terminology.hl7.org/6.5.0 Latest Release is 7.1.0 hl7.fhir.uv.extensions.r4 5.2.0 O R4 http://hl7.org/fhir/extensions http://hl7.org/fhir/extensions/5.2.0 (as above). Latest Release is 5.3.0 hl7.fhir.uv.extensions.r4 5.2.0 O R4 http://hl7.org/fhir/extensions http://hl7.org/fhir/extensions/5.2.0 (as above). Latest Release is 5.3.0 ihe.iti.balp 1.1.4 M R4 https://profiles.ihe.net/ITI/BALP https://profiles.ihe.net/ITI/BALP/1.1.4 Matched to latest patch release (1.1.x->1.1.4) (as above) hl7.fhir.uv.sdc 3.0.0 O R4 http://hl7.org/fhir/uv/sdc http://hl7.org/fhir/uv/sdc/STU3 (as above). Latest Release is 4.0.0 hl7.fhir.uv.xver-r5.r4 0.1.0 U R4 http://hl7.org/fhir/uv/xver http://hl7.org/fhir/uv/xver-r5.r4/0.1.0 hl7.terminology.r4 7.1.0 M R4 http://terminology.hl7.org http://terminology.hl7.org/7.1.0 (as above) hl7.fhir.uv.extensions.r4 5.2.0 O R4 http://hl7.org/fhir/extensions http://hl7.org/fhir/extensions/5.2.0 (as above). Latest Release is 5.3.0 hl7.fhir.uv.tools.r4 1.1.2 M R4 http://hl7.org/fhir/tools http://hl7.org/fhir/tools/1.1.2 Internal Dependency Templates: hl7.fast.template#current -> hl7.fhir.template#current -> hl7.base.template#current -> fhir2.base.template#current
Related IGs:	n/a
Dependent IGs:	no references
Global Profiles:	(none declared)
Terminology Server(s):	http://tx.fhir.org/r4, https://tx.fhir.org/r4 (details)
HTA Analysis:	All OK
R5 Dependencies:	http://hl7.org/fhir/5.0/StructureDefinition/extension-SubscriptionTopic.resourceTrigger http://hl7.org/fhir/5.0/StructureDefinition/extension-SubscriptionTopic.name http://hl7.org/fhir/5.0/StructureDefinition/extension-ActorDefinition.url http://hl7.org/fhir/5.0/StructureDefinition/extension-Consent.controller|0.1.0 http://hl7.org/fhir/5.0/StructureDefinition/extension-Requirements.statement.derivedFrom http://hl7.org/fhir/5.0/StructureDefinition/extension-ActorDefinition.description http://hl7.org/fhir/5.0/StructureDefinition/extension-SubscriptionTopic.publisher http://hl7.org/fhir/5.0/StructureDefinition/extension-Requirements.statement.conformance http://hl7.org/fhir/5.0/StructureDefinition/extension-SubscriptionTopic.title http://hl7.org/fhir/5.0/StructureDefinition/extension-ActorDefinition.title http://hl7.org/fhir/5.0/StructureDefinition/extension-Requirements.statement.requirement http://hl7.org/fhir/5.0/StructureDefinition/extension-Requirements.url http://hl7.org/fhir/5.0/StructureDefinition/extension-Requirements.name http://hl7.org/fhir/5.0/StructureDefinition/extension-Requirements.date http://hl7.org/fhir/5.0/StructureDefinition/extension-ActorDefinition.date http://hl7.org/fhir/5.0/StructureDefinition/extension-Consent.manager http://hl7.org/fhir/5.0/StructureDefinition/extension-ActorDefinition.type http://hl7.org/fhir/5.0/StructureDefinition/extension-SubscriptionTopic.canFilterBy http://hl7.org/fhir/5.0/StructureDefinition/extension-Requirements.actor http://hl7.org/fhir/5.0/StructureDefinition/extension-SubscriptionTopic.date http://hl7.org/fhir/5.0/StructureDefinition/extension-ActorDefinition.status http://hl7.org/fhir/5.0/StructureDefinition/extension-Requirements.publisher http://hl7.org/fhir/5.0/StructureDefinition/extension-SubscriptionTopic.url http://hl7.org/fhir/5.0/StructureDefinition/extension-Requirements.description http://hl7.org/fhir/5.0/StructureDefinition/extension-SubscriptionTopic.contact http://hl7.org/fhir/5.0/StructureDefinition/extension-ActorDefinition.publisher http://hl7.org/fhir/5.0/StructureDefinition/extension-Requirements.title http://hl7.org/fhir/5.0/StructureDefinition/extension-ActorDefinition.version http://hl7.org/fhir/5.0/StructureDefinition/extension-SubscriptionTopic.experimental http://hl7.org/fhir/5.0/StructureDefinition/extension-Requirements.statement.satisfiedBy http://hl7.org/fhir/5.0/StructureDefinition/extension-SubscriptionTopic.jurisdiction http://hl7.org/fhir/5.0/StructureDefinition/extension-SubscriptionTopic.version http://hl7.org/fhir/5.0/StructureDefinition/extension-ActorDefinition.name http://hl7.org/fhir/5.0/StructureDefinition/extension-ActorDefinition.contact http://hl7.org/fhir/5.0/StructureDefinition/extension-Requirements.jurisdiction http://hl7.org/fhir/5.0/StructureDefinition/extension-SubscriptionTopic.description http://hl7.org/fhir/5.0/StructureDefinition/extension-Requirements.statement.label http://hl7.org/fhir/5.0/StructureDefinition/extension-Requirements.status http://hl7.org/fhir/5.0/StructureDefinition/extension-Requirements.experimental http://hl7.org/fhir/5.0/StructureDefinition/extension-SubscriptionTopic.status http://hl7.org/fhir/5.0/StructureDefinition/extension-ActorDefinition.experimental http://hl7.org/fhir/5.0/StructureDefinition/extension-Consent.manager|0.1.0 http://hl7.org/fhir/5.0/StructureDefinition/extension-Requirements.contact http://hl7.org/fhir/5.0/StructureDefinition/extension-ActorDefinition.documentation http://hl7.org/fhir/5.0/StructureDefinition/extension-Requirements.statement http://hl7.org/fhir/5.0/StructureDefinition/extension-ActorDefinition.jurisdiction http://hl7.org/fhir/5.0/StructureDefinition/extension-Requirements.version http://hl7.org/fhir/5.0/StructureDefinition/extension-Requirements.statement.key
Draft Dependencies:	hl7.fhir.r4.core#4.0.1: GuideParameterCode (16 uses), SecurityRoleType (2 uses), AuditEventEntityRole (2 uses), Consent (8 uses), CommonLanguages (7 uses), ConsentState (1 uses), ConsentScopeCodes (2 uses), ConsentScopeCodes (1 uses), ConsentCategoryCodes (1 uses), Organization (7 uses), ConsentPolicyRuleCodes (1 uses), RelatedPerson (4 uses), ConsentProvisionType (2 uses), SecurityRoleType (7 uses), Device (4 uses), Group (2 uses), CareTeam (2 uses), Practitioner (4 uses), PractitionerRole (4 uses), ConsentActionCodes (2 uses), ConsentContentClass (2 uses), ConsentContentCodes (2 uses), ConsentDataMeaning (2 uses), AuditEventAction (1 uses), AuditEventOutcome (1 uses), ParticipationRoleType (5 uses), Location (5 uses), AuditEventAgentNetworkType (5 uses), AuditEvent (4 uses), AuditEventEntityType (4 uses), AuditEventEntityRole (4 uses), ObjectLifecycleEvents (4 uses), AuditEventEntityType (1 uses), DocumentReferenceStatus (1 uses), CompositionStatus (1 uses), DocumentRelationshipType (1 uses), DocumentReference (1 uses), Subscription (1 uses), SubscriptionStatus (1 uses), SubscriptionChannelType (1 uses), ConsentState (1 uses), patient (1 uses), actor (1 uses), status (1 uses), category (1 uses) hl7.fhir.uv.sdc#3.0.0: StructuredDataCapture (1 uses) hl7.fhir.uv.subscriptions-backport.r4#1.1.0: SubscriptionsR5Backport (1 uses)
Modifier Extensions:	(none)
Previous Version Comparison:	Comparison with version 1.0.0-ballot
IPA Comparison:	n/a
IPS Comparison:	n/a
Validation Flags:	On: autoLoad; Off: hintAboutNonMustSupport, anyExtensionsAllowed, checkAggregation, showReferenceMessages, noExperimentalContent, displayWarnings
Summary:	errors = 1, warn = 1, info = 29, broken links = 10, pinned = 10 (when multiples). Show Message Ids

n/a Show Validation Information

input/resources/Requirements-subscriptiontopic-fastconsentsubscriptiontopic-client-consent-ser.json Show Validation Information (1)

Suppressed Messages (Warnings, hints, broken links)

01 -This IG is based on hl7.fhir.us.core#6.1.0 due to CMS regulation stating that systems must conform to 6.1.0

• The ImplementationGuide uses package hl7.fhir.us.core#6.1.0 released on 2023-06-30, but the most recent appropriate version is 8.0.1. This reference is getting old and the more recent version should be considered (1 uses)
• The ImplementationGuide uses package hl7.fhir.uv.sdc#3.0.0 released on 2022-03-08, but the most recent appropriate version is 4.0.0. This reference is getting old and the more recent version should be considered (1 uses)

02 - We don't have narratives on the parameters.

• Constraint failed: dom-6: 'A resource should have narrative for robust management (text.`div`.exists())' (defined in http://hl7.org/fhir/StructureDefinition/DomainResource) (Best Practice Recommendation) (4 uses)

03 - We have checked that the LOINC Consent codes are in the US Core Doc Ref Type value set

• Unable to check if http://hl7.org/fhir/us/consent-management/ValueSet/LOINCConsentDocumentTypes is a proper subset of http://hl7.org/fhir/us/core/ValueSet/us-core-documentreference-type - value set is too large to check (1 uses)

04 - Messages due to definitions from the base spec or US Core or IHE guides

• Reference to deprecated ValueSet http://hl7.org/fhir/5.0/ValueSet/jurisdiction|5.0.0 (20 uses)
• Reference to experimental CodeSystem http://terminology.hl7.org/CodeSystem/extra-security-role-type|1.0.1 (0 uses)
• The discriminator type 'pattern' is deprecated in R5+. For future compatibility, you could consider using type=value with a pattern[x] instead (if this is not an inherited slicing) (1 uses)
• The extension http://hl7.org/fhir/StructureDefinition/elementdefinition-maxValueSet|5.3.0 is deprecated with the note: 'Use additionalBinding extension or element instead' (1 uses)
• The extension http://hl7.org/fhir/StructureDefinition/regex|5.3.0 is deprecated with the note: 'This was deprecated in favor of using a constraint on the element using FHIRPath, since constraints allow for the provision of a human readable message associated with the regex' (1 uses)

05 - An example URL for a Questionnaire for the purposes of this guide's examples

• The questionnaire 'http://example.org/fhir/Questionnaire/Simple-Consent-Form' could not be resolved, so no validation can be performed against the base questionnaire (2 uses)

06 - Core value sets that are pinned to a specific version

• Pinned the version of http://hl7.org/fhir/consent-state-codes to 5.0.0 from choices of 4.0.1 (hl7.fhir.r4.core#4.0.1), 5.0.0 (hl7.fhir.uv.xver-r5.r4#0.1.0) (0 uses)
• Pinned the version of http://terminology.hl7.org/ValueSet/v3-ActCode to 3.0.0 from choices of 2.0.0 (hl7.terminology.r4#5.3.0), 3.0.0 (hl7.terminology.r4#6.5.0) (0 uses)
• Pinned the version of http://terminology.hl7.org/ValueSet/v3-PurposeOfUse to 3.1.0 from choices of 2.0.0 (hl7.terminology.r4#5.3.0), 3.1.0 (hl7.terminology.r4#6.5.0) (0 uses)

07 - US Core has an inconsistent Must Support slice in v6

• The slice 'uscore' on path 'DocumentReference.category' is not marked as 'must-support' which is not consistent with the element that defines the slicing, where 'must-support' is true (1 uses)

08 - We are using the R4 Subscriptions Backport IG which is 4.0.0

• The ImplementationGuide is based on FHIR version 4.0.1 but package hl7.fhir.uv.subscriptions-backport.r4#1.1.0 is based on FHIR version 4.0.0. In general, this version mismatch should be avoided - some tools will try to make this work with variable degrees of success, but others will not even try (1 uses)
• This IG is version 4.0.1, while the IG 'hl7.fhir.uv.subscriptions-backport.r4' is from version 4.0.0 (1 uses)

09a - Conformance Clauses that won't get explicitly called out - explaining what SHALL, SHOULD, and MAY mean

• INFORMATION: en/conformance.html: The html source contains the word 'MAY' but it is not in a text phrase marked as a conformance clause: 'The conformance verbs — SHALL, SHOULD, MAY — used in this guide are defined in FHIR Conformance Rules.' (1 uses)
• INFORMATION: en/conformance.html: The html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: 'The conformance verbs — SHALL, SHOULD, MAY — used in this guide are defined in FHIR Conformance Rules.' (1 uses)
• INFORMATION: en/conformance.html: The html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause: 'The conformance verbs — SHALL, SHOULD, MAY — used in this guide are defined in FHIR Conformance Rules.' (1 uses)

09b - Conformance Clauses that won't get explicitly called out - Requirements object that have verbs in the narrative

• INFORMATION: en/Requirements-capstmt-client.ai.html: The html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: '' (1 uses)
• INFORMATION: en/Requirements-capstmt-client.html: The html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: '' (1 uses)
• INFORMATION: en/Requirements-capstmt-consent-server.ai.html: The html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: '' (1 uses)
• INFORMATION: en/Requirements-capstmt-consent-server.html: The html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: '' (1 uses)
• INFORMATION: en/Requirements-components-client.ai.html: The html source contains the word 'SHOULD NOT' but it is not in a text phrase marked as a conformance clause: '' (1 uses)
• INFORMATION: en/Requirements-components-client.html: The html source contains the word 'SHOULD NOT' but it is not in a text phrase marked as a conformance clause: '' (1 uses)
• INFORMATION: en/Requirements-components-consent-server.ai.html: The html source contains the word 'SHOULD NOT' but it is not in a text phrase marked as a conformance clause: '' (1 uses)
• INFORMATION: en/Requirements-components-consent-server.html: The html source contains the word 'SHOULD NOT' but it is not in a text phrase marked as a conformance clause: '' (1 uses)
• INFORMATION: en/Requirements-conformance-client-consent-server.ai.html: The html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: '' (1 uses)
• INFORMATION: en/Requirements-conformance-client-consent-server.html: The html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: '' (1 uses)
• INFORMATION: en/Requirements-conformance-client.ai.html: The html source contains the word 'SHOULD NOT' but it is not in a text phrase marked as a conformance clause: '' (1 uses)
• INFORMATION: en/Requirements-conformance-client.html: The html source contains the word 'SHOULD NOT' but it is not in a text phrase marked as a conformance clause: '' (1 uses)
• INFORMATION: en/Requirements-conformance-consent-server.ai.html: The html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: '' (1 uses)
• INFORMATION: en/Requirements-conformance-consent-server.html: The html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: '' (1 uses)
• INFORMATION: en/Requirements-extended-operations-client-consent-server.ai.html: The html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: 'Conformance: SHALL' (1 uses)
• INFORMATION: en/Requirements-extended-operations-client-consent-server.html: The html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: 'Conformance: SHALL' (1 uses)
• INFORMATION: en/Requirements-search-parameters-client-consent-server.ai.html: The html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: 'Conformance: SHALL' (1 uses)
• INFORMATION: en/Requirements-search-parameters-client-consent-server.html: The html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: 'Conformance: SHALL' (1 uses)
• INFORMATION: en/Requirements-structure-definitions-client-consent-server.ai.html: The html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: 'Conformance: SHALL' (1 uses)
• INFORMATION: en/Requirements-structure-definitions-client-consent-server.html: The html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: 'Conformance: SHALL' (1 uses)
• INFORMATION: en/Requirements-subscriptiontopic-fastconsentsubscriptiontopic-client-consent-ser.ai.html: The html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: 'Conformance: SHALL' (1 uses)
• INFORMATION: en/Requirements-subscriptiontopic-fastconsentsubscriptiontopic-client-consent-ser.html: The html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: 'Conformance: SHALL' (1 uses)
• INFORMATION: en/Requirements-subscriptiontopic-fastconsentsubscriptiontopic-client.ai.html: The html source contains the word 'MAY' but it is not in a text phrase marked as a conformance clause: '' (1 uses)
• INFORMATION: en/Requirements-subscriptiontopic-fastconsentsubscriptiontopic-client.html: The html source contains the word 'MAY' but it is not in a text phrase marked as a conformance clause: '' (1 uses)
• INFORMATION: en/Requirements-subscriptiontopic-fastconsentsubscriptiontopic-consent-server.ai.html: The html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: '' (1 uses)
• INFORMATION: en/Requirements-subscriptiontopic-fastconsentsubscriptiontopic-consent-server.html: The html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: '' (1 uses)
• INFORMATION: en/Requirements-technical-specification-client.ai.html: The html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: '' (1 uses)
• INFORMATION: en/Requirements-technical-specification-client.html: The html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: '' (1 uses)
• INFORMATION: en/Requirements-technical-specification-consent-server.ai.html: The html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause: '' (1 uses)
• INFORMATION: en/Requirements-technical-specification-consent-server.html: The html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause: '' (1 uses)
• INFORMATION: en/Requirements-workflow-client-consent-server.ai.html: The html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: 'Conformance: SHALL' (1 uses)
• INFORMATION: en/Requirements-workflow-client-consent-server.html: The html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: 'Conformance: SHALL' (1 uses)

10 - The code is 'cbcc', but the publisher wants cbcc in the url but it should be homehealth. (https://chat.fhir.org/#narrow/channel/179252-IG-creation/topic/CBCC.20vs.20Homehealth/with/560287669)

• The nominated WG 'cbcc' means that the contact url should be 'http://www.hl7.org/Special/committees/cbcc' but it was not found (16 uses)

11 - Subscription Topic warnings that have been verified to be correct

• If the parameter 'patient' is an instance of the parameter defined in the base FHIR standard, then the type should be id, but found Reference (0 uses)
• If the parameter 'subscription' is an instance of the parameter defined in the base FHIR standard, then the type should be string, but found Reference (0 uses)
• If the parameter 'topic' is an instance of the parameter defined in the base FHIR standard, then the type should be string, but found canonical (0 uses)
• No definition could be found for URL value 'hipaa-auth' (4 uses)
• ValueSet 'http://hl7.org/fhir/ValueSet/subscription-notification-type' not found (2 uses)

Errors sorted by type

MSG_DRAFT

MSG_EXPERIMENTAL

PARAMETERS_STD_WRONG_TYPE

PIN_VERSION

Resource_RES_ID_Malformed_Length