Validation Results for CQLUSCommon

Generated Sun Jul 12 20:21:51 UTC 2026, FHIR version 4.0.1 for hl7.fhir.us.cql#2.0.0-cibuild (canonical = http://hl7.org/fhir/us/cql (history)). See Errors Only & IP

Quality Checks
Publisher Version:IG Publisher Version: v2.2.10
Publication Code:cql . PackageId = hl7.fhir.us.cql, Canonical = http://hl7.org/fhir/us/cql
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 23 (4%) of resources have a language. Population Policy: NONE
Publication Request:
RelatedIgs(None Found)
  • Publication Request is for v'2.0.0-ballot' but package version is v2.0.0-cibuild
  • Publication Request is for version v2.0.0-ballot which is already published
Supressed Messages:237 Suppressed Issues
Dependency Checks:
PackageVersionFHIRCanonicalWeb BaseComment
.. hl7.fhir.us.cql2.0.0-cibuildR4http://hl7.org/fhir/us/cql
... hl7.terminology.r47.2.0 MR4http://terminology.hl7.orghttp://terminology.hl7.org/7.2.0
.... hl7.fhir.uv.extensions.r45.3.0 MR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/5.3.0
..... hl7.terminology.r47.1.0 OR4http://terminology.hl7.orghttp://terminology.hl7.org/7.1.0Latest Release is 7.2.0
...... hl7.fhir.uv.extensions.r45.2.0 OR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/5.2.0Latest Release is 5.3.0
... hl7.fhir.uv.extensions.r45.3.0 MR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/5.3.0 (as above)
... hl7.fhir.uv.cql2.0.0 MR4http://hl7.org/fhir/uv/cqlhttp://hl7.org/fhir/uv/cql/STU2
.... hl7.terminology.r46.5.0 OR4http://terminology.hl7.orghttp://terminology.hl7.org/6.5.0Latest Release is 7.2.0
..... hl7.fhir.uv.extensions.r45.2.0 OR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/5.2.0 (as above). Latest Release is 5.3.0
.... hl7.fhir.uv.extensions.r45.2.0 OR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/5.2.0 (as above). Latest Release is 5.3.0
.... hl7.terminology5.5.0 OR4http://terminology.hl7.orghttp://terminology.hl7.org/5.5.0Latest Release is 7.2.0
..... hl7.fhir.uv.extensions.r41.0.0 OR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/1.0.0Latest Release is 5.3.0
.... hl7.fhir.uv.extensions.r45.1.0 OR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/5.1.0Latest Release is 5.3.0
... hl7.fhir.uv.sdc3.0.0 OR4http://hl7.org/fhir/uv/sdchttp://hl7.org/fhir/uv/sdc/STU3Latest Release is 4.0.0
.... hl7.fhir.r4.examples4.0.1 OR4http://hl7.org/fhirhttp://hl7.org/fhir/R4Latest Release is 5.0.0
... hl7.fhir.us.core7.0.0 OR4http://hl7.org/fhir/us/corehttp://hl7.org/fhir/us/core/STU7Latest Release is 9.0.0
.... hl7.terminology.r45.5.0 OR4http://terminology.hl7.orghttp://terminology.hl7.org/5.5.0Latest Release is 7.2.0
.... hl7.fhir.uv.smart-app-launch2.0.0 OR4http://hl7.org/fhir/smart-app-launchhttp://hl7.org/fhir/smart-app-launch/STU2Latest Release is 2.2.0
.... us.nlm.vsac0.18.0 OR4http://fhir.org/packages/us.nlm.vsachttp://fhir.org/packages/us.nlm.vsacLatest Release is 0.24.0
.... hl7.fhir.uv.sdc3.0.0 OR4http://hl7.org/fhir/uv/sdchttp://hl7.org/fhir/uv/sdc/STU3 (as above). Latest Release is 4.0.0
.... us.cdc.phinvads0.12.0 MR4http://fhir.org/packages/us.cdc.phinvadshttp://fhir.org/packages/us.cdc.phinvads
.... hl7.fhir.uv.extensions5.1.0-snapshot1 OR5http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/5.1.0-snapshot1FHIR Version Mismatch. Latest Release is 5.3.0
..... hl7.terminology.r55.3.0 OR5http://terminology.hl7.orghttp://terminology.hl7.org/5.3.0FHIR Version Mismatch. Latest Release is 7.2.0
... hl7.fhir.uv.tools.r41.1.2 MR4http://hl7.org/fhir/toolshttp://hl7.org/fhir/tools/1.1.2Internal Dependency
Templates: 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, https://tx.hl7chile.cl/r4 (details)
HTA Analysis:no Non-HL7 references found
R5 Dependencies:(none)
Draft Dependencies:
Modifier Extensions:(none)
Previous Version Comparison: Comparison with version 2.0.0-ballot
IPA Comparison: n/a
IPS Comparison: n/a
Validation Flags: On: autoLoad; Off: hintAboutNonMustSupport, anyExtensionsAllowed, checkAggregation, showReferenceMessages, noExperimentalContent, displayWarnings
Summary: errors = 4, warn = 2, info = 105, broken links = 29, pinned = 136 (all) (in manifest Parameters/manifest).
FilenameErrorsWarningsHints
Build Errors2900
/scratch/repo/input/cql-us421
/scratch/repo/input/images000
/scratch/repo/input/images/CDSConnect-Element-BaseElement000
/scratch/repo/input/images/CDSConnect-Element-CustomModifier000
/scratch/repo/input/images/CDSConnect-Element-Modifiers000
/scratch/repo/input/images/CDSConnect-Element-Type000
/scratch/repo/input/images/CDSConnect-Element-ValueSet000
/scratch/repo/input/images/Integration-Test-Scenarios000
/scratch/repo/input/images/LHCFormsBuilder-Questionnaire-GroupQuestion000
/scratch/repo/input/images/LHCFormsBuilder-Questionnaire-SimpleQuestion000
/scratch/repo/input/images/LHCFormsBuilder-QuestionnaireMetadata000
/scratch/repo/input/images/LHCFormsBuilder-QuestionnaireMetadata-Advanced000
/scratch/repo/input/images/LHCFormsBuilder-QuestionnaireMetadata-Basic000
/scratch/repo/input/images/assets000
/scratch/repo/input/images/assets/images000
/scratch/repo/input/images/assets/images/cqf000
/scratch/repo/input/images/assets/images/da-vinci_logo000
/scratch/repo/input/images/cql000
/scratch/repo/input/images/dtr-data-flow000
/scratch/repo/input/includes/fragment-header000
/scratch/repo/input/includes/img000
/scratch/repo/input/includes/menu000
/scratch/repo/input/pagecontent/architectural-guidance000
/scratch/repo/input/pagecontent/authoring000
/scratch/repo/input/pagecontent/background000
/scratch/repo/input/pagecontent/changes000
/scratch/repo/input/pagecontent/downloads000
/scratch/repo/input/pagecontent/examples000
/scratch/repo/input/pagecontent/index000
/scratch/repo/input/pagecontent/license000
/scratch/repo/input/pagecontent/patterns000
/scratch/repo/input/pagecontent/patterns-allergy000
/scratch/repo/input/pagecontent/patterns-claim000
/scratch/repo/input/pagecontent/patterns-condition000
/scratch/repo/input/pagecontent/patterns-coverage000
/scratch/repo/input/pagecontent/patterns-lab000
/scratch/repo/input/pagecontent/patterns-medication000
/scratch/repo/input/pagecontent/patterns-observation000
/scratch/repo/input/pagecontent/patterns-overall000
/scratch/repo/input/pagecontent/patterns-patient000
/scratch/repo/input/pagecontent/patterns-service000
/scratch/repo/input/pagecontent/query-management000
/scratch/repo/input/pagecontent/testing000
/scratch/repo/input/pagecontent/tooling-support000
/scratch/repo/input/pagecontent/usage000
/scratch/repo/input/pagecontent/uscore-modelinfo000
/scratch/repo/input/pagecontent/use-case-cds000
/scratch/repo/input/pagecontent/use-case-cpg000
/scratch/repo/input/pagecontent/use-case-cqm000
/scratch/repo/input/pagecontent/use-case-pa000
/scratch/repo/input/pagecontent/use-case-ph000
/scratch/repo/input/pagecontent/use-cases000
/scratch/repo/input/resources/library/C4BB-ModelInfo001
/scratch/repo/input/resources/library/C4BBCommon001
/scratch/repo/input/resources/library/CumulativeMedicationDuration001
/scratch/repo/input/resources/library/CumulativeMedicationDurationTests001
/scratch/repo/input/resources/library/ExamplePatientAndCoverageInitialExpressions001
/scratch/repo/input/resources/library/GMTPInitialExpressions001
/scratch/repo/input/resources/library/MBODAInitialExpressions002
/scratch/repo/input/resources/library/MNACInitialExpressions001
/scratch/repo/input/resources/library/QICore-ModelInfo001
/scratch/repo/input/resources/library/UPPARFInitialExpressions001
/scratch/repo/input/resources/library/USCore-ModelInfo001
/scratch/repo/input/resources/library/USCoreCommon001
/scratch/repo/input/resources/library/USCoreCommonTests001
/scratch/repo/input/resources/library/USCoreElements0027
/scratch/repo/input/resources/library/USCoreTests001
/scratch/repo/input/resources/parameters/Parameters-manifest000
/scratch/repo/input/resources/parameters/Parameters-uscore-7-0-0-modelinfo-settings0052
/scratch/repo/input/resources/questionnaire/ExamplePatientAndCoverageQuestionnaire002
/scratch/repo/input/resources/questionnaire/GMTPQuestionnaire002
/scratch/repo/input/resources/questionnaire/MBODAQuestionnaire002
/scratch/repo/input/resources/questionnaire/MNACQuestionnaire002
/scratch/repo/input/resources/questionnaire/UPPARFQuestionnaire002
/scratch/repo/temp/pages/_includes/artifacts000
/scratch/repo/template/config000
/scratch/repo/template/config/_config000

n/a Show Validation Information

en​/patterns-allergy​.html​#​/html​/body​/div​/div​/div​/div​/div​/ul​/li​/a at Line 393, column 8errorThe link 'Library-USCoreElements.html#:~:text=core%2Dallergyintolerance%0A*/%0Adefine-,%22All%20Allergies%20and%20Intolerances%22,-%3A%0A%20%20%5BUSCore' for ""All Allergies and Intolerances"" cannot be resolved (valid targets: [toggle-change-display, project-logo, segment-header, project-nav, publish-box, bottom, hl7-logo, showChanges, segment-post-footer, family-logo, family-nav, ig-status, top, root, stripe, segment-footer, hl7-nav, segment-navbar, library-us-core-elements, segment-content, segment-breadcrumb]) HTML_LINK_CHECK_FAILED
en​/patterns-allergy​.html​#​/html​/body​/div​/div​/div​/div​/div​/ul​/li​/a at Line 394, column 8errorThe link 'Library-USCoreElements.html#:~:text=%22Active%20Confirmed%20Allergies%20and%20Intolerances%22' for ""Active Confirmed Allergies and Intolerances"" cannot be resolved (valid targets: [toggle-change-display, project-logo, segment-header, project-nav, publish-box, bottom, hl7-logo, showChanges, segment-post-footer, family-logo, family-nav, ig-status, top, root, stripe, segment-footer, hl7-nav, segment-navbar, library-us-core-elements, segment-content, segment-breadcrumb]) HTML_LINK_CHECK_FAILED
en​/patterns-allergy​.html​#​/html​/body​/div​/div​/div​/div​/div​/ul​/li​/a at Line 395, column 8errorThe link 'Library-USCoreElements.html#:~:text=()%0A%0Adefine-,%22Common%20Allergies%20and%20Intolerances%22,-%3A%0A%20%20%22All%20Allergies' for ""Common Allergies and Intolerances"" cannot be resolved (valid targets: [toggle-change-display, project-logo, segment-header, project-nav, publish-box, bottom, hl7-logo, showChanges, segment-post-footer, family-logo, family-nav, ig-status, top, root, stripe, segment-footer, hl7-nav, segment-navbar, library-us-core-elements, segment-content, segment-breadcrumb]) HTML_LINK_CHECK_FAILED
en​/patterns-allergy​.html​#​/html​/body​/div​/div​/div​/div​/div​/ul​/li​/a at Line 396, column 8errorThe link 'Library-USCoreElements.html#:~:text=%22Active%20Confirmed%20Common%20Allergies%20and%20Intolerances%22' for ""Active Confirmed Common Allergies and Intolerances"" cannot be resolved (valid targets: [toggle-change-display, project-logo, segment-header, project-nav, publish-box, bottom, hl7-logo, showChanges, segment-post-footer, family-logo, family-nav, ig-status, top, root, stripe, segment-footer, hl7-nav, segment-navbar, library-us-core-elements, segment-content, segment-breadcrumb]) HTML_LINK_CHECK_FAILED
en​/patterns-allergy​.html​#​/html​/body​/div​/div​/div​/div​/div​/ul​/li​/a at Line 406, column 8errorThe link 'Library-USCoreElements.html#:~:text=%22No%20Known%20Allergies%20%28Confirmed%29%22' for ""No Known Allergies (Confirmed)"" cannot be resolved (valid targets: [toggle-change-display, project-logo, segment-header, project-nav, publish-box, bottom, hl7-logo, showChanges, segment-post-footer, family-logo, family-nav, ig-status, top, root, stripe, segment-footer, hl7-nav, segment-navbar, library-us-core-elements, segment-content, segment-breadcrumb]) HTML_LINK_CHECK_FAILED
en​/patterns-allergy​.html​#​/html​/body​/div​/div​/div​/div​/div​/ul​/li​/a at Line 407, column 8errorThe link 'Library-USCoreElements.html#:~:text=%22No%20Known%20Allergies%20%28Not%20Asked%29%22' for ""No Known Allergies (Not Asked)"" cannot be resolved (valid targets: [toggle-change-display, project-logo, segment-header, project-nav, publish-box, bottom, hl7-logo, showChanges, segment-post-footer, family-logo, family-nav, ig-status, top, root, stripe, segment-footer, hl7-nav, segment-navbar, library-us-core-elements, segment-content, segment-breadcrumb]) HTML_LINK_CHECK_FAILED
en​/patterns-observation​.html​#​/html​/body​/div​/div​/div​/div​/div​/ul​/li​/a at Line 400, column 8errorThe link 'Library-USCoreCommon.html#:~:text=define%20fluent%20function-,positive,-%28observations%20List' for ".positive()" cannot be resolved (valid targets: [toggle-change-display, project-logo, segment-header, project-nav, publish-box, bottom, hl7-logo, showChanges, segment-post-footer, family-logo, family-nav, ig-status, library-us-core-common, top, root, stripe, segment-footer, hl7-nav, segment-navbar, segment-content, segment-breadcrumb]) HTML_LINK_CHECK_FAILED
en​/patterns-observation​.html​#​/html​/body​/div​/div​/div​/div​/div​/ul​/li​/a at Line 401, column 8errorThe link 'Library-USCoreCommon.html#:~:text=define%20fluent%20function-,negative,-%28observations%20List' for ".negative()" cannot be resolved (valid targets: [toggle-change-display, project-logo, segment-header, project-nav, publish-box, bottom, hl7-logo, showChanges, segment-post-footer, family-logo, family-nav, ig-status, library-us-core-common, top, root, stripe, segment-footer, hl7-nav, segment-navbar, segment-content, segment-breadcrumb]) HTML_LINK_CHECK_FAILED
en​/patterns-observation​.html​#​/html​/body​/div​/div​/div​/div​/div​/ul​/li​/a at Line 407, column 8errorThe link 'Library-USCoreCommon.html#:~:text=define%20fluent%20function-,during,-%28observations%20List' for ".during(Encounter)" cannot be resolved (valid targets: [toggle-change-display, project-logo, segment-header, project-nav, publish-box, bottom, hl7-logo, showChanges, segment-post-footer, family-logo, family-nav, ig-status, library-us-core-common, top, root, stripe, segment-footer, hl7-nav, segment-navbar, segment-content, segment-breadcrumb]) HTML_LINK_CHECK_FAILED
en​/patterns-observation​.html​#​/html​/body​/div​/div​/div​/div​/div​/ul​/li​/a at Line 408, column 8errorThe link 'Library-USCoreCommon.html#:~:text=define%20fluent%20function-,within,-%28observations%20List' for ".within(Quantity)" cannot be resolved (valid targets: [toggle-change-display, project-logo, segment-header, project-nav, publish-box, bottom, hl7-logo, showChanges, segment-post-footer, family-logo, family-nav, ig-status, library-us-core-common, top, root, stripe, segment-footer, hl7-nav, segment-navbar, segment-content, segment-breadcrumb]) HTML_LINK_CHECK_FAILED
en​/patterns-observation​.html​#​/html​/body​/div​/div​/div​/div​/div​/ul​/li​/a at Line 409, column 8errorThe link 'Library-USCoreCommon.html#:~:text=define%20fluent%20function-,consecutively,-%28observations%20List' for ".consecutively()" cannot be resolved (valid targets: [toggle-change-display, project-logo, segment-header, project-nav, publish-box, bottom, hl7-logo, showChanges, segment-post-footer, family-logo, family-nav, ig-status, library-us-core-common, top, root, stripe, segment-footer, hl7-nav, segment-navbar, segment-content, segment-breadcrumb]) HTML_LINK_CHECK_FAILED
en​/patterns-observation​.html​#​/html​/body​/div​/div​/div​/div​/div​/ul​/li​/a at Line 410, column 8errorThe link 'Library-USCoreCommon.html#:~:text=define%20fluent%20function-,consecutivelyFrom,-%28observations%20List' for ".consecutivelyFrom(Observation)" cannot be resolved (valid targets: [toggle-change-display, project-logo, segment-header, project-nav, publish-box, bottom, hl7-logo, showChanges, segment-post-footer, family-logo, family-nav, ig-status, library-us-core-common, top, root, stripe, segment-footer, hl7-nav, segment-navbar, segment-content, segment-breadcrumb]) HTML_LINK_CHECK_FAILED
en​/patterns-observation​.html​#​/html​/body​/div​/div​/div​/div​/div​/ul​/li​/a at Line 418, column 8errorThe link 'Library-USCoreElements.html#:~:text=observation%2Dlab%0A*/%0Adefine-,%22All%20Laboratory%20Results%22,-%3A%0A%20%20%5B%22LaboratoryResultObservationProfile' for ""All Laboratory Results"" cannot be resolved (valid targets: [toggle-change-display, project-logo, segment-header, project-nav, publish-box, bottom, hl7-logo, showChanges, segment-post-footer, family-logo, family-nav, ig-status, top, root, stripe, segment-footer, hl7-nav, segment-navbar, library-us-core-elements, segment-content, segment-breadcrumb]) HTML_LINK_CHECK_FAILED
en​/patterns-observation​.html​#​/html​/body​/div​/div​/div​/div​/div​/ul​/li​/a at Line 419, column 8errorThe link 'Library-USCoreElements.html#:~:text=%22Resulted%20Laboratory%20Results%22' for ""Resulted Laboratory Results"" cannot be resolved (valid targets: [toggle-change-display, project-logo, segment-header, project-nav, publish-box, bottom, hl7-logo, showChanges, segment-post-footer, family-logo, family-nav, ig-status, top, root, stripe, segment-footer, hl7-nav, segment-navbar, library-us-core-elements, segment-content, segment-breadcrumb]) HTML_LINK_CHECK_FAILED
en​/patterns-patient​.html​#​/html​/body​/div​/div​/div​/div​/div​/ul​/li​/a at Line 318, column 8errorThe link 'Library-USCoreElements.html#:~:text=define%20fluent%20function-,name,-%28patient%20Patient' for ".name()" cannot be resolved (valid targets: [toggle-change-display, project-logo, segment-header, project-nav, publish-box, bottom, hl7-logo, showChanges, segment-post-footer, family-logo, family-nav, ig-status, top, root, stripe, segment-footer, hl7-nav, segment-navbar, library-us-core-elements, segment-content, segment-breadcrumb]) HTML_LINK_CHECK_FAILED
en​/patterns-patient​.html​#​/html​/body​/div​/div​/div​/div​/div​/ul​/li​/a at Line 319, column 8errorThe link 'Library-USCoreElements.html#:~:text=define%20fluent%20function-,usualName,-%28patient%20Patient' for ".usualName()" cannot be resolved (valid targets: [toggle-change-display, project-logo, segment-header, project-nav, publish-box, bottom, hl7-logo, showChanges, segment-post-footer, family-logo, family-nav, ig-status, top, root, stripe, segment-footer, hl7-nav, segment-navbar, library-us-core-elements, segment-content, segment-breadcrumb]) HTML_LINK_CHECK_FAILED
en​/patterns-patient​.html​#​/html​/body​/div​/div​/div​/div​/div​/ul​/li​/a at Line 320, column 8errorThe link 'Library-USCoreElements.html#:~:text=define%20fluent%20function-,officialName,-%28patient%20Patient' for ".officialName()" cannot be resolved (valid targets: [toggle-change-display, project-logo, segment-header, project-nav, publish-box, bottom, hl7-logo, showChanges, segment-post-footer, family-logo, family-nav, ig-status, top, root, stripe, segment-footer, hl7-nav, segment-navbar, library-us-core-elements, segment-content, segment-breadcrumb]) HTML_LINK_CHECK_FAILED
en​/patterns-patient​.html​#​/html​/body​/div​/div​/div​/div​/div​/ul​/li​/a at Line 321, column 8errorThe link 'Library-USCoreElements.html#:~:text=define%20fluent%20function-,firstNonOfficialNonUsualName,-%28patient%20Patient' for ".firstNonOfficialNonUsualName()" cannot be resolved (valid targets: [toggle-change-display, project-logo, segment-header, project-nav, publish-box, bottom, hl7-logo, showChanges, segment-post-footer, family-logo, family-nav, ig-status, top, root, stripe, segment-footer, hl7-nav, segment-navbar, library-us-core-elements, segment-content, segment-breadcrumb]) HTML_LINK_CHECK_FAILED
en​/patterns-patient​.html​#​/html​/body​/div​/div​/div​/div​/div​/ul​/li​/a at Line 327, column 8errorThe link 'Library-USCoreElements.html#:~:text=define%20fluent%20function-,firstName,-%28name%20HumanName' for ".firstName()" cannot be resolved (valid targets: [toggle-change-display, project-logo, segment-header, project-nav, publish-box, bottom, hl7-logo, showChanges, segment-post-footer, family-logo, family-nav, ig-status, top, root, stripe, segment-footer, hl7-nav, segment-navbar, library-us-core-elements, segment-content, segment-breadcrumb]) HTML_LINK_CHECK_FAILED
en​/patterns-patient​.html​#​/html​/body​/div​/div​/div​/div​/div​/ul​/li​/a at Line 328, column 8errorThe link 'Library-USCoreElements.html#:~:text=define%20fluent%20function-,middleNames,-%28name%20HumanName' for ".middleNames()" cannot be resolved (valid targets: [toggle-change-display, project-logo, segment-header, project-nav, publish-box, bottom, hl7-logo, showChanges, segment-post-footer, family-logo, family-nav, ig-status, top, root, stripe, segment-footer, hl7-nav, segment-navbar, library-us-core-elements, segment-content, segment-breadcrumb]) HTML_LINK_CHECK_FAILED
en​/patterns-patient​.html​#​/html​/body​/div​/div​/div​/div​/div​/ul​/li​/a at Line 329, column 8errorThe link 'Library-USCoreElements.html#:~:text=define%20fluent%20function-,lastName,-%28name%20HumanName' for ".lastName()" cannot be resolved (valid targets: [toggle-change-display, project-logo, segment-header, project-nav, publish-box, bottom, hl7-logo, showChanges, segment-post-footer, family-logo, family-nav, ig-status, top, root, stripe, segment-footer, hl7-nav, segment-navbar, library-us-core-elements, segment-content, segment-breadcrumb]) HTML_LINK_CHECK_FAILED
en​/patterns-patient​.html​#​/html​/body​/div​/div​/div​/div​/div​/ul​/li​/a at Line 330, column 8errorThe link 'Library-USCoreElements.html#:~:text=define%20fluent%20function-,firstMiddleLast,-%28name%20HumanName' for ".firstMiddleLast()" cannot be resolved (valid targets: [toggle-change-display, project-logo, segment-header, project-nav, publish-box, bottom, hl7-logo, showChanges, segment-post-footer, family-logo, family-nav, ig-status, top, root, stripe, segment-footer, hl7-nav, segment-navbar, library-us-core-elements, segment-content, segment-breadcrumb]) HTML_LINK_CHECK_FAILED
en​/patterns-patient​.html​#​/html​/body​/div​/div​/div​/div​/div​/ul​/li​/a at Line 331, column 8errorThe link 'Library-USCoreElements.html#:~:text=define%20fluent%20function-,lastFirstMiddle,-%28name%20HumanName' for ".lastFirstMiddle()" cannot be resolved (valid targets: [toggle-change-display, project-logo, segment-header, project-nav, publish-box, bottom, hl7-logo, showChanges, segment-post-footer, family-logo, family-nav, ig-status, top, root, stripe, segment-footer, hl7-nav, segment-navbar, library-us-core-elements, segment-content, segment-breadcrumb]) HTML_LINK_CHECK_FAILED
en​/patterns-patient​.html​#​/html​/body​/div​/div​/div​/div​/div​/ul​/li​/a at Line 365, column 8errorThe link 'Library-USCoreElements.html#:~:text=define%20fluent%20function-,ageInDaysAt,-%28patient%20Patient' for ".ageInDaysAt()" cannot be resolved (valid targets: [toggle-change-display, project-logo, segment-header, project-nav, publish-box, bottom, hl7-logo, showChanges, segment-post-footer, family-logo, family-nav, ig-status, top, root, stripe, segment-footer, hl7-nav, segment-navbar, library-us-core-elements, segment-content, segment-breadcrumb]) HTML_LINK_CHECK_FAILED
en​/patterns-patient​.html​#​/html​/body​/div​/div​/div​/div​/div​/ul​/li​/a at Line 366, column 8errorThe link 'Library-USCoreElements.html#:~:text=define%20fluent%20function-,ageInDays,-%28patient%20Patient' for ".ageInDays()" cannot be resolved (valid targets: [toggle-change-display, project-logo, segment-header, project-nav, publish-box, bottom, hl7-logo, showChanges, segment-post-footer, family-logo, family-nav, ig-status, top, root, stripe, segment-footer, hl7-nav, segment-navbar, library-us-core-elements, segment-content, segment-breadcrumb]) HTML_LINK_CHECK_FAILED
en​/patterns-patient​.html​#​/html​/body​/div​/div​/div​/div​/div​/ul​/li​/a at Line 367, column 8errorThe link 'Library-USCoreElements.html#:~:text=define%20fluent%20function-,ageInMonthsAt,-%28patient%20Patient' for ".ageInMonthsAt()" cannot be resolved (valid targets: [toggle-change-display, project-logo, segment-header, project-nav, publish-box, bottom, hl7-logo, showChanges, segment-post-footer, family-logo, family-nav, ig-status, top, root, stripe, segment-footer, hl7-nav, segment-navbar, library-us-core-elements, segment-content, segment-breadcrumb]) HTML_LINK_CHECK_FAILED
en​/patterns-patient​.html​#​/html​/body​/div​/div​/div​/div​/div​/ul​/li​/a at Line 368, column 8errorThe link 'Library-USCoreElements.html#:~:text=define%20fluent%20function-,ageInMonths,-%28patient%20Patient' for ".ageInMonths()" cannot be resolved (valid targets: [toggle-change-display, project-logo, segment-header, project-nav, publish-box, bottom, hl7-logo, showChanges, segment-post-footer, family-logo, family-nav, ig-status, top, root, stripe, segment-footer, hl7-nav, segment-navbar, library-us-core-elements, segment-content, segment-breadcrumb]) HTML_LINK_CHECK_FAILED
en​/patterns-patient​.html​#​/html​/body​/div​/div​/div​/div​/div​/ul​/li​/a at Line 369, column 8errorThe link 'Library-USCoreElements.html#:~:text=define%20fluent%20function-,ageInYearsAt,-%28patient%20Patient' for ".ageInYearsAt()" cannot be resolved (valid targets: [toggle-change-display, project-logo, segment-header, project-nav, publish-box, bottom, hl7-logo, showChanges, segment-post-footer, family-logo, family-nav, ig-status, top, root, stripe, segment-footer, hl7-nav, segment-navbar, library-us-core-elements, segment-content, segment-breadcrumb]) HTML_LINK_CHECK_FAILED
en​/patterns-patient​.html​#​/html​/body​/div​/div​/div​/div​/div​/ul​/li​/a at Line 370, column 8errorThe link 'Library-USCoreElements.html#:~:text=define%20fluent%20function-,ageInYears,-%28patient%20Patient' for ".ageInYears()" cannot be resolved (valid targets: [toggle-change-display, project-logo, segment-header, project-nav, publish-box, bottom, hl7-logo, showChanges, segment-post-footer, family-logo, family-nav, ig-status, top, root, stripe, segment-footer, hl7-nav, segment-navbar, library-us-core-elements, segment-content, segment-breadcrumb]) HTML_LINK_CHECK_FAILED

input/cql-us.xml Show Validation Information (1)

PathSeverityMessageValidating
ImplementationGuide​.definition​.extension[4]​.extension[0]​.value​.ofType(string) (l1​/c5047)errorThe System URI could not be determined for the code 'path-liquid-ig' in the ValueSet 'http://hl7.org/fhir/tools/ValueSet/ig-parameters|1.1.2'

Editor's Comment: 1.0.0:01 - The path-liquid-ig parameter is a temporary workaround for getting the IG to make use of liquid templates in the IG when the fhir template includes liquid templates for the same resources. See https://chat.fhir.org/#narrow/channel/179252-IG-creation/topic/Errors.20in.20rendering.20Measures.20and.20PlanDefinitions/near/534068493 UNABLE_TO_INFER_CODESYSTEM
ImplementationGuide
ImplementationGuide​.definition​.extension[4]​.extension[0]​.value​.ofType(string) (l1​/c5047)errorThe value provided ('path-liquid-ig') was not found in the value set 'ig-parameters Codes ValueSet' (http://hl7.org/fhir/tools/ValueSet/ig-parameters|1.1.2), and a code is required from this value set (error message = The System URI could not be determined for the code 'path-liquid-ig' in the ValueSet 'http://hl7.org/fhir/tools/ValueSet/ig-parameters|1.1.2'; The provided code '#path-liquid-ig' was not found in the value set 'http://hl7.org/fhir/tools/ValueSet/ig-parameters|1.1.2')

Editor's Comment: 1.0.0:01 - The path-liquid-ig parameter is a temporary workaround for getting the IG to make use of liquid templates in the IG when the fhir template includes liquid templates for the same resources. See https://chat.fhir.org/#narrow/channel/179252-IG-creation/topic/Errors.20in.20rendering.20Measures.20and.20PlanDefinitions/near/534068493 Terminology_TX_NoValid_16
ImplementationGuide
ImplementationGuide​.definition​.extension[39]​.extension[0]​.value​.ofType(code) (l1​/c11017)errorThe System URI could not be determined for the code 'path-liquid-ig' in the ValueSet 'http://hl7.org/fhir/tools/ValueSet/ig-parameters|1.1.2'

Editor's Comment: 1.0.0:01 - The path-liquid-ig parameter is a temporary workaround for getting the IG to make use of liquid templates in the IG when the fhir template includes liquid templates for the same resources. See https://chat.fhir.org/#narrow/channel/179252-IG-creation/topic/Errors.20in.20rendering.20Measures.20and.20PlanDefinitions/near/534068493 UNABLE_TO_INFER_CODESYSTEM
ImplementationGuide
ImplementationGuide​.definition​.extension[39]​.extension[0]​.value​.ofType(code) (l1​/c11017)errorThe value provided ('path-liquid-ig') was not found in the value set 'ig-parameters Codes ValueSet' (http://hl7.org/fhir/tools/ValueSet/ig-parameters|1.1.2), and a code is required from this value set (error message = The System URI could not be determined for the code 'path-liquid-ig' in the ValueSet 'http://hl7.org/fhir/tools/ValueSet/ig-parameters|1.1.2'; The provided code '#path-liquid-ig' was not found in the value set 'http://hl7.org/fhir/tools/ValueSet/ig-parameters|1.1.2')

Editor's Comment: 1.0.0:01 - The path-liquid-ig parameter is a temporary workaround for getting the IG to make use of liquid templates in the IG when the fhir template includes liquid templates for the same resources. See https://chat.fhir.org/#narrow/channel/179252-IG-creation/topic/Errors.20in.20rendering.20Measures.20and.20PlanDefinitions/near/534068493 Terminology_TX_NoValid_16
ImplementationGuide
ImplementationGuide​.dependsOn[3] (l1​/c3957)warningThe ImplementationGuide uses package hl7.fhir.uv.crmi#1.0.0 released on 2024-05-31, but the most recent appropriate version is 2.0.0. This reference is getting old and the more recent version should be considered IG_DEPENDENCY_VERSION_WARNING_OLD--
ImplementationGuide​.dependsOn[5] (l1​/c4228)warningThe ImplementationGuide uses package hl7.fhir.us.core#7.0.0 released on 2024-05-08, but the most recent appropriate version is 9.0.0. This reference is getting old and the more recent version should be considered IG_DEPENDENCY_VERSION_WARNING_OLD--
ResourceinformationThe resource ImplementationGuide/hl7.fhir.us.cql could usefully have an OID assigned (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/fhir-tools-ig/CodeSystem-ig-parameters.html#ig-parameters-auto-oid-root) --

input/images Show Validation Information (0)


input/images/CDSConnect-Element-BaseElement.png Show Validation Information (0)


input/images/CDSConnect-Element-CustomModifier.png Show Validation Information (0)


input/images/CDSConnect-Element-Modifiers.png Show Validation Information (0)


input/images/CDSConnect-Element-Type.png Show Validation Information (0)


input/images/CDSConnect-Element-ValueSet.png Show Validation Information (0)


input/images/Integration-Test-Scenarios.png Show Validation Information (0)


input/images/LHCFormsBuilder-Questionnaire-GroupQuestion.png Show Validation Information (0)


input/images/LHCFormsBuilder-Questionnaire-SimpleQuestion.png Show Validation Information (0)


input/images/LHCFormsBuilder-QuestionnaireMetadata.png Show Validation Information (0)


input/images/LHCFormsBuilder-QuestionnaireMetadata-Advanced.png Show Validation Information (0)


input/images/LHCFormsBuilder-QuestionnaireMetadata-Basic.png Show Validation Information (0)


input/images/assets Show Validation Information (0)


input/images/assets/images Show Validation Information (0)


input/images/assets/images/cqf.png Show Validation Information (0)


input/images/assets/images/da-vinci_logo.jpg Show Validation Information (0)


input/images/cql.js Show Validation Information (0)


input/images/dtr-data-flow.svg Show Validation Information (0)


input/includes/fragment-header.html Show Validation Information (0)


input/includes/img.html Show Validation Information (0)


input/includes/menu.xml Show Validation Information (0)


input/pagecontent/architectural-guidance.md Show Validation Information (0)


input/pagecontent/authoring.md Show Validation Information (0)


input/pagecontent/background.md Show Validation Information (0)


input/pagecontent/changes.md Show Validation Information (0)


input/pagecontent/downloads.md Show Validation Information (0)


input/pagecontent/examples.md Show Validation Information (0)


input/pagecontent/index.md Show Validation Information (0)


input/pagecontent/license.md Show Validation Information (0)


input/pagecontent/patterns.md Show Validation Information (0)


input/pagecontent/patterns-allergy.md Show Validation Information (0)


input/pagecontent/patterns-claim.md Show Validation Information (0)


input/pagecontent/patterns-condition.md Show Validation Information (0)


input/pagecontent/patterns-coverage.md Show Validation Information (0)


input/pagecontent/patterns-lab.md Show Validation Information (0)


input/pagecontent/patterns-medication.md Show Validation Information (0)


input/pagecontent/patterns-observation.md Show Validation Information (0)


input/pagecontent/patterns-overall.md Show Validation Information (0)


input/pagecontent/patterns-patient.md Show Validation Information (0)


input/pagecontent/patterns-service.md Show Validation Information (0)


input/pagecontent/query-management.md Show Validation Information (0)


input/pagecontent/testing.md Show Validation Information (0)


input/pagecontent/tooling-support.md Show Validation Information (0)


input/pagecontent/usage.md Show Validation Information (0)


input/pagecontent/uscore-modelinfo.md Show Validation Information (0)


input/pagecontent/use-case-cds.md Show Validation Information (0)


input/pagecontent/use-case-cpg.md Show Validation Information (0)


input/pagecontent/use-case-cqm.md Show Validation Information (0)


input/pagecontent/use-case-pa.md Show Validation Information (0)


input/pagecontent/use-case-ph.md Show Validation Information (0)


input/pagecontent/use-cases.md Show Validation Information (0)


input/resources/library/C4BB-ModelInfo.json Show Validation Information (1)

PathSeverityMessageValidating
ResourceinformationThe resource Library/C4BB-ModelInfo could usefully have an OID assigned (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/fhir-tools-ig/CodeSystem-ig-parameters.html#ig-parameters-auto-oid-root) --

input/resources/library/C4BBCommon.json Show Validation Information (1)

PathSeverityMessageValidating
ResourceinformationThe resource Library/C4BBCommon could usefully have an OID assigned (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/fhir-tools-ig/CodeSystem-ig-parameters.html#ig-parameters-auto-oid-root) --

input/resources/library/CumulativeMedicationDuration.json Show Validation Information (1)

PathSeverityMessageValidating
ResourceinformationThe resource Library/CumulativeMedicationDuration could usefully have an OID assigned (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/fhir-tools-ig/CodeSystem-ig-parameters.html#ig-parameters-auto-oid-root) --

input/resources/library/CumulativeMedicationDurationTests.json Show Validation Information (1)

PathSeverityMessageValidating
ResourceinformationThe resource Library/CumulativeMedicationDurationTests could usefully have an OID assigned (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/fhir-tools-ig/CodeSystem-ig-parameters.html#ig-parameters-auto-oid-root) --

input/resources/library/ExamplePatientAndCoverageInitialExpressions.json Show Validation Information (1)

PathSeverityMessageValidating
ResourceinformationThe resource Library/ExamplePatientAndCoverageInitialExpressions could usefully have an OID assigned (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/fhir-tools-ig/CodeSystem-ig-parameters.html#ig-parameters-auto-oid-root) --

input/resources/library/GMTPInitialExpressions.json Show Validation Information (1)

PathSeverityMessageValidating
ResourceinformationThe resource Library/GMTPInitialExpressions could usefully have an OID assigned (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/fhir-tools-ig/CodeSystem-ig-parameters.html#ig-parameters-auto-oid-root) --

input/resources/library/MBODAInitialExpressions.json Show Validation Information (1)

PathSeverityMessageValidating
Library.relatedArtifact[4].resourceinformationPinned the version of http://hl7.org/fhir/us/cql/Library/CumulativeMedicationDuration to 2.0.0-cibuild PIN_VERSION--
ResourceinformationThe resource Library/MBODAInitialExpressions could usefully have an OID assigned (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/fhir-tools-ig/CodeSystem-ig-parameters.html#ig-parameters-auto-oid-root) --

input/resources/library/MNACInitialExpressions.json Show Validation Information (1)

PathSeverityMessageValidating
ResourceinformationThe resource Library/MNACInitialExpressions could usefully have an OID assigned (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/fhir-tools-ig/CodeSystem-ig-parameters.html#ig-parameters-auto-oid-root) --

input/resources/library/QICore-ModelInfo.json Show Validation Information (1)

PathSeverityMessageValidating
ResourceinformationThe resource Library/QICore-ModelInfo could usefully have an OID assigned (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/fhir-tools-ig/CodeSystem-ig-parameters.html#ig-parameters-auto-oid-root) --

input/resources/library/UPPARFInitialExpressions.json Show Validation Information (1)

PathSeverityMessageValidating
ResourceinformationThe resource Library/UPPARFInitialExpressions could usefully have an OID assigned (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/fhir-tools-ig/CodeSystem-ig-parameters.html#ig-parameters-auto-oid-root) --

input/resources/library/USCore-ModelInfo.json Show Validation Information (1)

PathSeverityMessageValidating
ResourceinformationThe resource Library/USCore-ModelInfo could usefully have an OID assigned (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/fhir-tools-ig/CodeSystem-ig-parameters.html#ig-parameters-auto-oid-root) --

input/resources/library/USCoreCommon.json Show Validation Information (1)

PathSeverityMessageValidating
ResourceinformationThe resource Library/USCoreCommon could usefully have an OID assigned (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/fhir-tools-ig/CodeSystem-ig-parameters.html#ig-parameters-auto-oid-root) --

input/resources/library/USCoreCommonTests.json Show Validation Information (1)

PathSeverityMessageValidating
ResourceinformationThe resource Library/USCoreCommonTests could usefully have an OID assigned (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/fhir-tools-ig/CodeSystem-ig-parameters.html#ig-parameters-auto-oid-root) --

input/resources/library/USCoreElements.json Show Validation Information (1)

PathSeverityMessageValidating
Library.dataRequirement[11].profile[0]informationPinned the version of http://hl7.org/fhir/us/core/StructureDefinition/head-occipital-frontal-circumference-percentile to 7.0.0 PIN_VERSION--
Library.dataRequirement[12].profile[0]informationPinned the version of http://hl7.org/fhir/us/core/StructureDefinition/pediatric-weight-for-height to 7.0.0 PIN_VERSION--
Library.dataRequirement[13].profile[0]informationPinned the version of http://hl7.org/fhir/us/core/StructureDefinition/us-core-procedure to 7.0.0 PIN_VERSION--
Library.dataRequirement[14].profile[0]informationPinned the version of http://hl7.org/fhir/us/core/StructureDefinition/us-core-pulse-oximetry to 7.0.0 PIN_VERSION--
Library.dataRequirement[15].profile[0]informationPinned the version of http://hl7.org/fhir/us/core/StructureDefinition/us-core-smokingstatus to 7.0.0 PIN_VERSION--
Library.dataRequirement[16].profile[0]informationPinned the version of http://hl7.org/fhir/us/core/StructureDefinition/us-core-vital-signs to 7.0.0 PIN_VERSION--
Library.dataRequirement[17].profile[0]informationPinned the version of http://hl7.org/fhir/us/core/StructureDefinition/us-core-respiratory-rate to 7.0.0 PIN_VERSION--
Library.dataRequirement[18].profile[0]informationPinned the version of http://hl7.org/fhir/us/core/StructureDefinition/us-core-heart-rate to 7.0.0 PIN_VERSION--
Library.dataRequirement[19].profile[0]informationPinned the version of http://hl7.org/fhir/us/core/StructureDefinition/us-core-body-temperature to 7.0.0 PIN_VERSION--
Library.dataRequirement[20].profile[0]informationPinned the version of http://hl7.org/fhir/us/core/StructureDefinition/us-core-body-height to 7.0.0 PIN_VERSION--
Library.dataRequirement[21].profile[0]informationPinned the version of http://hl7.org/fhir/us/core/StructureDefinition/us-core-head-circumference to 7.0.0 PIN_VERSION--
Library.dataRequirement[22].profile[0]informationPinned the version of http://hl7.org/fhir/us/core/StructureDefinition/us-core-body-weight to 7.0.0 PIN_VERSION--
Library.dataRequirement[23].profile[0]informationPinned the version of http://hl7.org/fhir/us/core/StructureDefinition/us-core-bmi to 7.0.0 PIN_VERSION--
Library.dataRequirement[24].profile[0]informationPinned the version of http://hl7.org/fhir/us/core/StructureDefinition/us-core-blood-pressure to 7.0.0 PIN_VERSION--
Library.dataRequirement[25].profile[0]informationPinned the version of http://hl7.org/fhir/StructureDefinition/Observation to 4.0.1 PIN_VERSION--
Library.dataRequirement[26].profile[0]informationPinned the version of http://hl7.org/fhir/StructureDefinition/ServiceRequest to 4.0.1 PIN_VERSION--
Library.dataRequirement[27].profile[0]informationPinned the version of http://hl7.org/fhir/us/core/StructureDefinition/us-core-practitioner to 7.0.0 PIN_VERSION--
Library.dataRequirement[28].profile[0]informationPinned the version of http://hl7.org/fhir/us/core/StructureDefinition/us-core-practitioner to 7.0.0 PIN_VERSION--
Library.dataRequirement[29].profile[0]informationPinned the version of http://hl7.org/fhir/us/core/StructureDefinition/us-core-organization to 7.0.0 PIN_VERSION--
Library.dataRequirement[30].profile[0]informationPinned the version of http://hl7.org/fhir/StructureDefinition/Condition to 4.0.1 PIN_VERSION--
Library.dataRequirement[31].profile[0]informationPinned the version of http://hl7.org/fhir/StructureDefinition/ResearchSubject to 4.0.1 PIN_VERSION--
Library.dataRequirement[32].profile[0]informationPinned the version of http://hl7.org/fhir/StructureDefinition/ResearchStudy to 4.0.1 PIN_VERSION--
Library.dataRequirement[33].profile[0]informationPinned the version of http://hl7.org/fhir/us/core/StructureDefinition/us-core-organization to 7.0.0 PIN_VERSION--
Library.dataRequirement[34].profile[0]informationPinned the version of http://hl7.org/fhir/StructureDefinition/Condition to 4.0.1 PIN_VERSION--
Library.dataRequirement[35].profile[0]informationPinned the version of http://hl7.org/fhir/us/core/StructureDefinition/us-core-practitioner to 7.0.0 PIN_VERSION--
Library.dataRequirement[36].profile[0]informationPinned the version of http://hl7.org/fhir/us/core/StructureDefinition/us-core-practitionerrole to 7.0.0 PIN_VERSION--
ResourceinformationThe resource Library/USCoreElements could usefully have an OID assigned (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/fhir-tools-ig/CodeSystem-ig-parameters.html#ig-parameters-auto-oid-root) --

input/resources/library/USCoreTests.json Show Validation Information (1)

PathSeverityMessageValidating
ResourceinformationThe resource Library/USCoreTests could usefully have an OID assigned (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/fhir-tools-ig/CodeSystem-ig-parameters.html#ig-parameters-auto-oid-root) --

input/resources/parameters/Parameters-manifest.json Show Validation Information (1)


input/resources/parameters/Parameters-uscore-7-0-0-modelinfo-settings.json Show Validation Information (1)

PathSeverityMessageValidating
Parameters.parameter[13] (l74/c10)informationThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct PARAMETERS_STD_RES_WRONG_TYPE_MIXED--
Parameters.parameter[14] (l99/c10)informationThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct PARAMETERS_STD_RES_WRONG_TYPE_MIXED--
Parameters.parameter[15] (l124/c10)informationThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct PARAMETERS_STD_RES_WRONG_TYPE_MIXED--
Parameters.parameter[16] (l149/c10)informationThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct PARAMETERS_STD_RES_WRONG_TYPE_MIXED--
Parameters.parameter[17] (l174/c10)informationThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct PARAMETERS_STD_RES_WRONG_TYPE_MIXED--
Parameters.parameter[18] (l199/c10)informationThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct PARAMETERS_STD_RES_WRONG_TYPE_MIXED--
Parameters.parameter[19] (l224/c10)informationThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct PARAMETERS_STD_RES_WRONG_TYPE_MIXED--
Parameters.parameter[20] (l249/c10)informationThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct PARAMETERS_STD_RES_WRONG_TYPE_MIXED--
Parameters.parameter[21] (l274/c10)informationThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct PARAMETERS_STD_RES_WRONG_TYPE_MIXED--
Parameters.parameter[22] (l299/c10)informationThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct PARAMETERS_STD_RES_WRONG_TYPE_MIXED--
Parameters.parameter[23] (l324/c10)informationThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct PARAMETERS_STD_RES_WRONG_TYPE_MIXED--
Parameters.parameter[24] (l349/c10)informationThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct PARAMETERS_STD_RES_WRONG_TYPE_MIXED--
Parameters.parameter[25] (l374/c10)informationThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct PARAMETERS_STD_RES_WRONG_TYPE_MIXED--
Parameters.parameter[26] (l399/c10)informationThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct PARAMETERS_STD_RES_WRONG_TYPE_MIXED--
Parameters.parameter[27] (l424/c10)informationThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct PARAMETERS_STD_RES_WRONG_TYPE_MIXED--
Parameters.parameter[28] (l449/c10)informationThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct PARAMETERS_STD_RES_WRONG_TYPE_MIXED--
Parameters.parameter[29] (l474/c10)informationThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct PARAMETERS_STD_RES_WRONG_TYPE_MIXED--
Parameters.parameter[30] (l499/c10)informationThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct PARAMETERS_STD_RES_WRONG_TYPE_MIXED--
Parameters.parameter[31] (l524/c10)informationThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct PARAMETERS_STD_RES_WRONG_TYPE_MIXED--
Parameters.parameter[32] (l549/c10)informationThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct PARAMETERS_STD_RES_WRONG_TYPE_MIXED--
Parameters.parameter[33] (l574/c10)informationThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct PARAMETERS_STD_RES_WRONG_TYPE_MIXED--
Parameters.parameter[34] (l599/c10)informationThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct PARAMETERS_STD_RES_WRONG_TYPE_MIXED--
Parameters.parameter[35] (l624/c10)informationThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct PARAMETERS_STD_RES_WRONG_TYPE_MIXED--
Parameters.parameter[36] (l649/c10)informationThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct PARAMETERS_STD_RES_WRONG_TYPE_MIXED--
Parameters.parameter[37] (l674/c10)informationThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct PARAMETERS_STD_RES_WRONG_TYPE_MIXED--
Parameters.parameter[38] (l699/c10)informationThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct PARAMETERS_STD_RES_WRONG_TYPE_MIXED--
Parameters.parameter[39] (l724/c10)informationThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct PARAMETERS_STD_RES_WRONG_TYPE_MIXED--
Parameters.parameter[40] (l749/c10)informationThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct PARAMETERS_STD_RES_WRONG_TYPE_MIXED--
Parameters.parameter[41] (l774/c10)informationThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct PARAMETERS_STD_RES_WRONG_TYPE_MIXED--
Parameters.parameter[42] (l799/c10)informationThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct PARAMETERS_STD_RES_WRONG_TYPE_MIXED--
Parameters.parameter[43] (l824/c10)informationThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct PARAMETERS_STD_RES_WRONG_TYPE_MIXED--
Parameters.parameter[44] (l849/c10)informationThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct PARAMETERS_STD_RES_WRONG_TYPE_MIXED--
Parameters.parameter[45] (l874/c10)informationThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct PARAMETERS_STD_RES_WRONG_TYPE_MIXED--
Parameters.parameter[46] (l899/c10)informationThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct PARAMETERS_STD_RES_WRONG_TYPE_MIXED--
Parameters.parameter[47] (l924/c10)informationThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct PARAMETERS_STD_RES_WRONG_TYPE_MIXED--
Parameters.parameter[48] (l949/c10)informationThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct PARAMETERS_STD_RES_WRONG_TYPE_MIXED--
Parameters.parameter[49] (l974/c10)informationThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct PARAMETERS_STD_RES_WRONG_TYPE_MIXED--
Parameters.parameter[50] (l999/c10)informationThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct PARAMETERS_STD_RES_WRONG_TYPE_MIXED--
Parameters.parameter[51] (l1024/c10)informationThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct PARAMETERS_STD_RES_WRONG_TYPE_MIXED--
Parameters.parameter[52] (l1049/c10)informationThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct PARAMETERS_STD_RES_WRONG_TYPE_MIXED--
Parameters.parameter[53] (l1074/c10)informationThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct PARAMETERS_STD_RES_WRONG_TYPE_MIXED--
Parameters.parameter[54] (l1099/c10)informationThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct PARAMETERS_STD_RES_WRONG_TYPE_MIXED--
Parameters.parameter[55] (l1124/c10)informationThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct PARAMETERS_STD_RES_WRONG_TYPE_MIXED--
Parameters.parameter[56] (l1149/c10)informationThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct PARAMETERS_STD_RES_WRONG_TYPE_MIXED--
Parameters.parameter[57] (l1174/c10)informationThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct PARAMETERS_STD_RES_WRONG_TYPE_MIXED--
Parameters.parameter[58] (l1199/c10)informationThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct PARAMETERS_STD_RES_WRONG_TYPE_MIXED--
Parameters.parameter[59] (l1224/c10)informationThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct PARAMETERS_STD_RES_WRONG_TYPE_MIXED--
Parameters.parameter[60] (l1249/c10)informationThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct PARAMETERS_STD_RES_WRONG_TYPE_MIXED--
Parameters.parameter[61] (l1274/c10)informationThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct PARAMETERS_STD_RES_WRONG_TYPE_MIXED--
Parameters.parameter[62] (l1299/c10)informationThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct PARAMETERS_STD_RES_WRONG_TYPE_MIXED--
Parameters.parameter[63] (l1324/c10)informationThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct PARAMETERS_STD_RES_WRONG_TYPE_MIXED--
Parameters.parameter[64] (l1349/c10)informationThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct PARAMETERS_STD_RES_WRONG_TYPE_MIXED--

input/resources/questionnaire/ExamplePatientAndCoverageQuestionnaire.json Show Validation Information (2)

PathSeverityMessageValidating
Questionnaire.extension[0].value[x]informationPinned the version of http://hl7.org/fhir/us/cql/Library/ExamplePatientAndCoverageInitialExpressions to 2.0.0-cibuild PIN_VERSION--
ResourceinformationThe resource Questionnaire/ExamplePatientAndCoverageQuestionnaire could usefully have an OID assigned (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/fhir-tools-ig/CodeSystem-ig-parameters.html#ig-parameters-auto-oid-root) --

input/resources/questionnaire/GMTPQuestionnaire.json Show Validation Information (2)

PathSeverityMessageValidating
Questionnaire.extension[0].value[x]informationPinned the version of http://hl7.org/fhir/us/cql/Library/GMTPInitialExpressions to 2.0.0-cibuild PIN_VERSION--
ResourceinformationThe resource Questionnaire/GMTPQuestionnaire could usefully have an OID assigned (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/fhir-tools-ig/CodeSystem-ig-parameters.html#ig-parameters-auto-oid-root) --

input/resources/questionnaire/MBODAQuestionnaire.json Show Validation Information (2)

PathSeverityMessageValidating
Questionnaire.extension[0].value[x]informationPinned the version of http://hl7.org/fhir/us/cql/Library/MBODAInitialExpressions to 2.0.0-cibuild PIN_VERSION--
ResourceinformationThe resource Questionnaire/MBODAQuestionnaire could usefully have an OID assigned (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/fhir-tools-ig/CodeSystem-ig-parameters.html#ig-parameters-auto-oid-root) --

input/resources/questionnaire/MNACQuestionnaire.json Show Validation Information (2)

PathSeverityMessageValidating
Questionnaire.extension[0].value[x]informationPinned the version of http://hl7.org/fhir/us/cql/Library/MNACInitialExpressions to 2.0.0-cibuild PIN_VERSION--
ResourceinformationThe resource Questionnaire/MNACQuestionnaire could usefully have an OID assigned (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/fhir-tools-ig/CodeSystem-ig-parameters.html#ig-parameters-auto-oid-root) --

input/resources/questionnaire/UPPARFQuestionnaire.json Show Validation Information (2)

PathSeverityMessageValidating
Questionnaire.extension[0].value[x]informationPinned the version of http://hl7.org/fhir/us/cql/Library/UPPARFInitialExpressions to 2.0.0-cibuild PIN_VERSION--
ResourceinformationThe resource Questionnaire/UPPARFQuestionnaire could usefully have an OID assigned (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/fhir-tools-ig/CodeSystem-ig-parameters.html#ig-parameters-auto-oid-root) --

temp/pages/_includes/artifacts.xml Show Validation Information (0)


template/config Show Validation Information (0)


template/config/_config.yml Show Validation Information (0)

Suppressed Messages (Warnings, hints, broken links)

1.0.0-ballot:02 - Accepted warnings about identifier hiding, reviewed and verified correct behavior

1.0.0-ballot:03 - These warnings are because the publisher CQL subsystem isn't accounting for profiled types, correcting in the next round of updates to the CQL subsystem

1.0.0:01 - The path-liquid-ig parameter is a temporary workaround for getting the IG to make use of liquid templates in the IG when the fhir template includes liquid templates for the same resources. See https://chat.fhir.org/#narrow/channel/179252-IG-creation/topic/Errors.20in.20rendering.20Measures.20and.20PlanDefinitions/near/534068493

1.0.0:02 - USCore 7 is intentionally targeted as the content has not yet been developed to include 8. A future version will incorporate changes introduced by 8

1.0.0:03 - These are because the publisher is not considering manifest for potential versions, will be fixed in a future publisher. Discussion in zulip here: https://chat.fhir.org/#narrow/channel/179252-IG-creation/topic/Canonical.20Pinning/near/534497073

1.0.0:04 - Deliberately used the same name in CQL as the extension so that it matches, it would be confusing otherwise

1.0.0:05 - Accepted pinned versions

1.0.0:06 - Accepted references to draft code systems

1.0.0:07 - Defined additional example launch context codes for example questionnaires

2.0.0-ballot:01 - Conformance language in an image

2.0.0-ballot:02 - Known issue with duplicate anchor ids in questionnaires (https://chat.fhir.org/#narrow/channel/179252-IG-creation/topic/Duplicate.20ids.20in.20Questionnaire.20rendering)

2.0.0-ballot:03 - These are using text fragment links (`#:~:text=`), so the publisher does not resolve them (Discussion in Zulip: https://chat.fhir.org/#narrow/channel/179252-IG-creation/topic/Text.20fragment.20links.20are.20marked.20as.20errors/with/578534990)

2.0.0-ballot:04 - Known issues with the expansions parameters settings:

2.0.0-ballot:05 - The publisher is correcting a known issue with dependencies reported from the CQL translator. This will be addressed with a new version of the translator, but until then the publisher will inform editors when this happens

2.0.0-ballot:06 - Will consider this as part of ballot comments

Errors sorted by type


IG_DEPENDENCY_VERSION_WARNING_OLD

input/cql-us.xmlThe ImplementationGuide uses package hl7.fhir.uv.crmi#1.0.0 released on 2024-05-31, but the most recent appropriate version is 2.0.0. This reference is getting old and the more recent version should be considered--
input/cql-us.xmlThe ImplementationGuide uses package hl7.fhir.us.core#7.0.0 released on 2024-05-08, but the most recent appropriate version is 9.0.0. This reference is getting old and the more recent version should be considered--

PARAMETERS_STD_RES_WRONG_TYPE_MIXED

input/resources/parameters/Parameters-uscore-7-0-0-modelinfo-settings.jsonThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct--
input/resources/parameters/Parameters-uscore-7-0-0-modelinfo-settings.jsonThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct--
input/resources/parameters/Parameters-uscore-7-0-0-modelinfo-settings.jsonThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct--
input/resources/parameters/Parameters-uscore-7-0-0-modelinfo-settings.jsonThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct--
input/resources/parameters/Parameters-uscore-7-0-0-modelinfo-settings.jsonThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct--
input/resources/parameters/Parameters-uscore-7-0-0-modelinfo-settings.jsonThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct--
input/resources/parameters/Parameters-uscore-7-0-0-modelinfo-settings.jsonThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct--
input/resources/parameters/Parameters-uscore-7-0-0-modelinfo-settings.jsonThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct--
input/resources/parameters/Parameters-uscore-7-0-0-modelinfo-settings.jsonThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct--
input/resources/parameters/Parameters-uscore-7-0-0-modelinfo-settings.jsonThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct--
input/resources/parameters/Parameters-uscore-7-0-0-modelinfo-settings.jsonThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct--
input/resources/parameters/Parameters-uscore-7-0-0-modelinfo-settings.jsonThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct--
input/resources/parameters/Parameters-uscore-7-0-0-modelinfo-settings.jsonThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct--
input/resources/parameters/Parameters-uscore-7-0-0-modelinfo-settings.jsonThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct--
input/resources/parameters/Parameters-uscore-7-0-0-modelinfo-settings.jsonThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct--
input/resources/parameters/Parameters-uscore-7-0-0-modelinfo-settings.jsonThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct--
input/resources/parameters/Parameters-uscore-7-0-0-modelinfo-settings.jsonThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct--
input/resources/parameters/Parameters-uscore-7-0-0-modelinfo-settings.jsonThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct--
input/resources/parameters/Parameters-uscore-7-0-0-modelinfo-settings.jsonThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct--
input/resources/parameters/Parameters-uscore-7-0-0-modelinfo-settings.jsonThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct--
input/resources/parameters/Parameters-uscore-7-0-0-modelinfo-settings.jsonThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct--
input/resources/parameters/Parameters-uscore-7-0-0-modelinfo-settings.jsonThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct--
input/resources/parameters/Parameters-uscore-7-0-0-modelinfo-settings.jsonThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct--
input/resources/parameters/Parameters-uscore-7-0-0-modelinfo-settings.jsonThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct--
input/resources/parameters/Parameters-uscore-7-0-0-modelinfo-settings.jsonThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct--
input/resources/parameters/Parameters-uscore-7-0-0-modelinfo-settings.jsonThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct--
input/resources/parameters/Parameters-uscore-7-0-0-modelinfo-settings.jsonThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct--
input/resources/parameters/Parameters-uscore-7-0-0-modelinfo-settings.jsonThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct--
input/resources/parameters/Parameters-uscore-7-0-0-modelinfo-settings.jsonThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct--
input/resources/parameters/Parameters-uscore-7-0-0-modelinfo-settings.jsonThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct--
input/resources/parameters/Parameters-uscore-7-0-0-modelinfo-settings.jsonThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct--
input/resources/parameters/Parameters-uscore-7-0-0-modelinfo-settings.jsonThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct--
input/resources/parameters/Parameters-uscore-7-0-0-modelinfo-settings.jsonThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct--
input/resources/parameters/Parameters-uscore-7-0-0-modelinfo-settings.jsonThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct--
input/resources/parameters/Parameters-uscore-7-0-0-modelinfo-settings.jsonThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct--
input/resources/parameters/Parameters-uscore-7-0-0-modelinfo-settings.jsonThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct--
input/resources/parameters/Parameters-uscore-7-0-0-modelinfo-settings.jsonThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct--
input/resources/parameters/Parameters-uscore-7-0-0-modelinfo-settings.jsonThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct--
input/resources/parameters/Parameters-uscore-7-0-0-modelinfo-settings.jsonThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct--
input/resources/parameters/Parameters-uscore-7-0-0-modelinfo-settings.jsonThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct--
input/resources/parameters/Parameters-uscore-7-0-0-modelinfo-settings.jsonThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct--
input/resources/parameters/Parameters-uscore-7-0-0-modelinfo-settings.jsonThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct--
input/resources/parameters/Parameters-uscore-7-0-0-modelinfo-settings.jsonThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct--
input/resources/parameters/Parameters-uscore-7-0-0-modelinfo-settings.jsonThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct--
input/resources/parameters/Parameters-uscore-7-0-0-modelinfo-settings.jsonThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct--
input/resources/parameters/Parameters-uscore-7-0-0-modelinfo-settings.jsonThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct--
input/resources/parameters/Parameters-uscore-7-0-0-modelinfo-settings.jsonThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct--
input/resources/parameters/Parameters-uscore-7-0-0-modelinfo-settings.jsonThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct--
input/resources/parameters/Parameters-uscore-7-0-0-modelinfo-settings.jsonThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct--
input/resources/parameters/Parameters-uscore-7-0-0-modelinfo-settings.jsonThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct--
input/resources/parameters/Parameters-uscore-7-0-0-modelinfo-settings.jsonThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct--
input/resources/parameters/Parameters-uscore-7-0-0-modelinfo-settings.jsonThe parameter 'profile' has the same name as a parameter for at least one operation in the core specification. In the base specification, then the type or resource type should be one of canonical or StructureDefinition, but found null. Check that this is correct--

PIN_VERSION

input/resources/library/MBODAInitialExpressions.jsonPinned the version of http://hl7.org/fhir/us/cql/Library/CumulativeMedicationDuration to 2.0.0-cibuild--
input/resources/library/USCoreElements.jsonPinned the version of http://hl7.org/fhir/us/core/StructureDefinition/head-occipital-frontal-circumference-percentile to 7.0.0--
input/resources/library/USCoreElements.jsonPinned the version of http://hl7.org/fhir/us/core/StructureDefinition/pediatric-weight-for-height to 7.0.0--
input/resources/library/USCoreElements.jsonPinned the version of http://hl7.org/fhir/us/core/StructureDefinition/us-core-procedure to 7.0.0--
input/resources/library/USCoreElements.jsonPinned the version of http://hl7.org/fhir/us/core/StructureDefinition/us-core-pulse-oximetry to 7.0.0--
input/resources/library/USCoreElements.jsonPinned the version of http://hl7.org/fhir/us/core/StructureDefinition/us-core-smokingstatus to 7.0.0--
input/resources/library/USCoreElements.jsonPinned the version of http://hl7.org/fhir/us/core/StructureDefinition/us-core-vital-signs to 7.0.0--
input/resources/library/USCoreElements.jsonPinned the version of http://hl7.org/fhir/us/core/StructureDefinition/us-core-respiratory-rate to 7.0.0--
input/resources/library/USCoreElements.jsonPinned the version of http://hl7.org/fhir/us/core/StructureDefinition/us-core-heart-rate to 7.0.0--
input/resources/library/USCoreElements.jsonPinned the version of http://hl7.org/fhir/us/core/StructureDefinition/us-core-body-temperature to 7.0.0--
input/resources/library/USCoreElements.jsonPinned the version of http://hl7.org/fhir/us/core/StructureDefinition/us-core-body-height to 7.0.0--
input/resources/library/USCoreElements.jsonPinned the version of http://hl7.org/fhir/us/core/StructureDefinition/us-core-head-circumference to 7.0.0--
input/resources/library/USCoreElements.jsonPinned the version of http://hl7.org/fhir/us/core/StructureDefinition/us-core-body-weight to 7.0.0--
input/resources/library/USCoreElements.jsonPinned the version of http://hl7.org/fhir/us/core/StructureDefinition/us-core-bmi to 7.0.0--
input/resources/library/USCoreElements.jsonPinned the version of http://hl7.org/fhir/us/core/StructureDefinition/us-core-blood-pressure to 7.0.0--
input/resources/library/USCoreElements.jsonPinned the version of http://hl7.org/fhir/StructureDefinition/Observation to 4.0.1--
input/resources/library/USCoreElements.jsonPinned the version of http://hl7.org/fhir/StructureDefinition/ServiceRequest to 4.0.1--
input/resources/library/USCoreElements.jsonPinned the version of http://hl7.org/fhir/us/core/StructureDefinition/us-core-practitioner to 7.0.0--
input/resources/library/USCoreElements.jsonPinned the version of http://hl7.org/fhir/us/core/StructureDefinition/us-core-practitioner to 7.0.0--
input/resources/library/USCoreElements.jsonPinned the version of http://hl7.org/fhir/us/core/StructureDefinition/us-core-organization to 7.0.0--
input/resources/library/USCoreElements.jsonPinned the version of http://hl7.org/fhir/StructureDefinition/Condition to 4.0.1--
input/resources/library/USCoreElements.jsonPinned the version of http://hl7.org/fhir/StructureDefinition/ResearchSubject to 4.0.1--
input/resources/library/USCoreElements.jsonPinned the version of http://hl7.org/fhir/StructureDefinition/ResearchStudy to 4.0.1--
input/resources/library/USCoreElements.jsonPinned the version of http://hl7.org/fhir/us/core/StructureDefinition/us-core-organization to 7.0.0--
input/resources/library/USCoreElements.jsonPinned the version of http://hl7.org/fhir/StructureDefinition/Condition to 4.0.1--
input/resources/library/USCoreElements.jsonPinned the version of http://hl7.org/fhir/us/core/StructureDefinition/us-core-practitioner to 7.0.0--
input/resources/library/USCoreElements.jsonPinned the version of http://hl7.org/fhir/us/core/StructureDefinition/us-core-practitionerrole to 7.0.0--
input/resources/questionnaire/ExamplePatientAndCoverageQuestionnaire.jsonPinned the version of http://hl7.org/fhir/us/cql/Library/ExamplePatientAndCoverageInitialExpressions to 2.0.0-cibuild--
input/resources/questionnaire/GMTPQuestionnaire.jsonPinned the version of http://hl7.org/fhir/us/cql/Library/GMTPInitialExpressions to 2.0.0-cibuild--
input/resources/questionnaire/MBODAQuestionnaire.jsonPinned the version of http://hl7.org/fhir/us/cql/Library/MBODAInitialExpressions to 2.0.0-cibuild--
input/resources/questionnaire/MNACQuestionnaire.jsonPinned the version of http://hl7.org/fhir/us/cql/Library/MNACInitialExpressions to 2.0.0-cibuild--
input/resources/questionnaire/UPPARFQuestionnaire.jsonPinned the version of http://hl7.org/fhir/us/cql/Library/UPPARFInitialExpressions to 2.0.0-cibuild--

Terminology_TX_NoValid_16

input/cql-us.xmlThe value provided ('path-liquid-ig') was not found in the value set 'ig-parameters Codes ValueSet' (http://hl7.org/fhir/tools/ValueSet/ig-parameters|1.1.2), and a code is required from this value set (error message = The System URI could not be determined for the code 'path-liquid-ig' in the ValueSet 'http://hl7.org/fhir/tools/ValueSet/ig-parameters|1.1.2'; The provided code '#path-liquid-ig' was not found in the value set 'http://hl7.org/fhir/tools/ValueSet/ig-parameters|1.1.2')ImplementationGuide
input/cql-us.xmlThe value provided ('path-liquid-ig') was not found in the value set 'ig-parameters Codes ValueSet' (http://hl7.org/fhir/tools/ValueSet/ig-parameters|1.1.2), and a code is required from this value set (error message = The System URI could not be determined for the code 'path-liquid-ig' in the ValueSet 'http://hl7.org/fhir/tools/ValueSet/ig-parameters|1.1.2'; The provided code '#path-liquid-ig' was not found in the value set 'http://hl7.org/fhir/tools/ValueSet/ig-parameters|1.1.2')ImplementationGuide

UNABLE_TO_INFER_CODESYSTEM

input/cql-us.xmlThe System URI could not be determined for the code 'path-liquid-ig' in the ValueSet 'http://hl7.org/fhir/tools/ValueSet/ig-parameters|1.1.2'ImplementationGuide
input/cql-us.xmlThe System URI could not be determined for the code 'path-liquid-ig' in the ValueSet 'http://hl7.org/fhir/tools/ValueSet/ig-parameters|1.1.2'ImplementationGuide