Validation Results for CQL

Generated Wed Jun 17 06:27:39 UTC 2026, FHIR version 4.0.1 for hl7.fhir.uv.cql#2.1.0-cibuild (canonical = http://hl7.org/fhir/uv/cql (history)). See Full QA Report & IP

Quality Checks
Publisher Version:IG Publisher Version: v2.2.9
Publication Code:cql . PackageId = hl7.fhir.uv.cql, Canonical = http://hl7.org/fhir/uv/cql
Realm Check for UV:
  • n/a
Language Info:Stated Languages: n/a. IG Resource Lang: en. 1 of 49 (2%) of resources have a language. Population Policy: NONE
Publication Request:
RelatedIgs(None Found)
  • Publication Request is for v'2.0.0' but package version is v2.1.0-cibuild
  • Publication Request is for version v2.0.0 which is already published
Supressed Messages:184 Suppressed Issues
Dependency Checks:
PackageVersionFHIRCanonicalWeb BaseComment
.. hl7.fhir.uv.cql2.1.0-cibuildR4http://hl7.org/fhir/uv/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.r4current VR4http://hl7.org/fhir/extensionshttps://build.fhir.org/ig/HL7/fhir-extensions/Cannot be published with a dependency on a current build version
.... hl7.terminology.r47.2.0 MR4http://terminology.hl7.orghttp://terminology.hl7.org/7.2.0 (as above)
... 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-nordics.fhir.org/fhir/r4, https://tx.fhir.org/r4 (details)
HTA Analysis:no Non-HL7 references found
R5 Dependencies:
Draft Dependencies:
Modifier Extensions:(none)
Previous Version Comparison: Comparison with version 2.0.0
IPA Comparison: n/a
IPS Comparison: n/a
Validation Flags: On: autoLoad; Off: hintAboutNonMustSupport, anyExtensionsAllowed, checkAggregation, showReferenceMessages, noExperimentalContent, displayWarnings
Summary: errors = 140, warn = 48, info = 255, broken links = 15, pinned = n/a.
FilenameErrorsWarningsHints
Build Errors2115
/scratch/repo/input/examples/ImplementationGuide-example220
/scratch/repo/input/examples/Library-ANCCohort021
/scratch/repo/input/examples/Library-Example020
/scratch/repo/input/examples/Library-TypeMappingExample0150
/scratch/repo/input/examples/Parameters-cql-typemappingexampleresult133
/scratch/repo/input/examples/Parameters-qicore-modelinfo-settings65065
/scratch/repo/input/examples/Parameters-uscore-modelinfo-settings52052
/scratch/repo/input/examples/ValueSet-publishable-example021
/scratch/repo/input/extensions/StructureDefinition-cql-selectivity911
/scratch/repo/input/profiles/StructureDefinition-cql-evaluationresult020
/scratch/repo/input/profiles/StructureDefinition-cql-groupdefinition440
/scratch/repo/input/resources/Library-FHIR-ModelInfo100
/scratch/repo/input/resources/Library-FHIRCommon0130
/scratch/repo/input/resources/Library-FHIRHelpers010

n/a Show Validation Information

Extension.extension.valueerrorThe reference http://hl7.org/fhir/ValueSet/selectivity-coverage could not be resolved
Extension.extension.valueerrorThe reference http://hl7.org/fhir/ValueSet/selectivity-inclusivity could not be resolved
Extension.extension.valueerrorThe reference http://hl7.org/fhir/ValueSet/selectivity-form could not be resolved
warningThe jira specification file appears to be out of date with the versions, artifacts and pages currently defined in the IG. A proposed revised file to be reviewed and, if appropriate, submitted as a pull request against the XML folder in https://github.com/HL7/JIRA-Spec-Artifacts. To see the differences, perform a file compare on 'template/jira-current.xml' (a normalized view of what is in Github) and 'template/jira-new.xml' (reflects current IG content)
errorIn your menu.xml file, it's no longer allowed to have href='#' on dropdown items. Change them to be href='menu.html' instead. (It won't link, but it needs to be something valid.)
?pkp-1?errorThe reference http://hl7.org/fhir/StructureDefinition/cqf-cqlLibrary could not be resolved
ToCerrorThe ToC contains the page index.html more than once
en​/Library-FHIR-ModelInfo​.html​#​/html​/body​/div​/div​/div​/div​/div​/p​/p​/a at Line 280, column 137errorThe link 'http://hl7.org/fhir/uv/cql/fhir-modelinfo.html' for "FHIR ModelInfo" cannot be resolved HTML_LINK_CHECK_FAILED
en​/Library-FHIR-ModelInfo​.html​#​/html​/body​/div​/div​/div​/div​/div​/div​/table​/tbody​/tr​/td​/div​/p​/a at Line 462, column 172errorThe link 'http://hl7.org/fhir/uv/cql/fhir-modelinfo.html' for "FHIR ModelInfo" cannot be resolved HTML_LINK_CHECK_FAILED
en​/artifacts​.html​#​/html​/body​/div​/div​/div​/div​/div​/div​/table​/tbody​/tr​/td​/p​/a at Line 361, column 137errorThe link 'http://hl7.org/fhir/uv/cql/fhir-modelinfo.html' for "FHIR ModelInfo" cannot be resolved HTML_LINK_CHECK_FAILED
en/changes.htmlinformationThe html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause: 'FHIR-43885: A Conformance Requirement that SHOULD be followed is confusing Applied (here)' CONFORMANCE_STATEMENT_WORD
en/conformance.htmlinformationThe html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: 'Content conforming to this implementation guide SHALL use FHIR Library resources to represent CQL libraries in FHIR.' CONFORMANCE_STATEMENT_WORD
en​/downloads​.html​#​/html​/body​/div​/div​/div​/div​/div​/ul​/li​/a at Line 237, column 8errorThe link 'definitions.xml.zip' for "XML" cannot be resolved HTML_LINK_CHECK_FAILED
en​/downloads​.html​#​/html​/body​/div​/div​/div​/div​/div​/ul​/li​/a at Line 238, column 8errorThe link 'definitions.json.zip' for "JSON" cannot be resolved HTML_LINK_CHECK_FAILED
en​/downloads​.html​#​/html​/body​/div​/div​/div​/div​/div​/ul​/li​/a at Line 239, column 8errorThe link 'definitions.ttl.zip' for "TTL" cannot be resolved HTML_LINK_CHECK_FAILED
en​/downloads​.html​#​/html​/body​/div​/div​/div​/div​/div​/ul​/li​/a at Line 253, column 8errorThe link 'examples.xml.zip' for "XML" cannot be resolved HTML_LINK_CHECK_FAILED
en​/downloads​.html​#​/html​/body​/div​/div​/div​/div​/div​/ul​/li​/a at Line 254, column 8errorThe link 'examples.json.zip' for "JSON" cannot be resolved HTML_LINK_CHECK_FAILED
en​/downloads​.html​#​/html​/body​/div​/div​/div​/div​/div​/ul​/li​/a at Line 255, column 8errorThe link 'examples.ttl.zip' for "TTL" cannot be resolved HTML_LINK_CHECK_FAILED
en/using-cql.htmlinformationThe html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: 'Any CQL library used by a FHIR artifact SHALL contain a library declaration.' CONFORMANCE_STATEMENT_WORD
en​/using-cql​.html​#​/html​/body​/div​/div​/div​/div​/div​/p​/a at Line 378, column 39errorThe link 'Library-Example.html#cql-content' for "Example.cql" cannot be resolved (valid targets: [toggle-change-display, segment-header, library-example -experimental-, publish-box, bottom, hl7-logo, showChanges, segment-post-footer, hl7-search, hl7-search-lnk, family-logo, family-nav, ig-status, top, root, stripe, segment-footer, hl7-nav, segment-navbar, segment-content, segment-breadcrumb]) HTML_LINK_CHECK_FAILED
en​/using-cql​.html​#​/html​/body​/div​/div​/div​/div​/div​/p​/a at Line 398, column 50errorThe link 'Library-Example.html#cql-content' for "Example.cql" cannot be resolved (valid targets: [toggle-change-display, segment-header, library-example -experimental-, publish-box, bottom, hl7-logo, showChanges, segment-post-footer, hl7-search, hl7-search-lnk, family-logo, family-nav, ig-status, top, root, stripe, segment-footer, hl7-nav, segment-navbar, segment-content, segment-breadcrumb]) HTML_LINK_CHECK_FAILED
en​/using-cql​.html​#​/html​/body​/div​/div​/div​/div​/div​/p​/a at Line 445, column 42errorThe link 'Library-Example.html#cql-content' for "Example.cql" cannot be resolved (valid targets: [toggle-change-display, segment-header, library-example -experimental-, publish-box, bottom, hl7-logo, showChanges, segment-post-footer, hl7-search, hl7-search-lnk, family-logo, family-nav, ig-status, top, root, stripe, segment-footer, hl7-nav, segment-navbar, segment-content, segment-breadcrumb]) HTML_LINK_CHECK_FAILED
en​/using-cql​.html​#​/html​/body​/div​/div​/div​/div​/div​/p​/a at Line 495, column 43errorThe link 'Library-Example.html#cql-content' for "Example.cql" cannot be resolved (valid targets: [toggle-change-display, segment-header, library-example -experimental-, publish-box, bottom, hl7-logo, showChanges, segment-post-footer, hl7-search, hl7-search-lnk, family-logo, family-nav, ig-status, top, root, stripe, segment-footer, hl7-nav, segment-navbar, segment-content, segment-breadcrumb]) HTML_LINK_CHECK_FAILED
en​/using-cql​.html​#​/html​/body​/div​/div​/div​/div​/div​/p​/a at Line 577, column 39errorThe link 'Library-Example.html#cql-content' for "Example.cql" cannot be resolved (valid targets: [toggle-change-display, segment-header, library-example -experimental-, publish-box, bottom, hl7-logo, showChanges, segment-post-footer, hl7-search, hl7-search-lnk, family-logo, family-nav, ig-status, top, root, stripe, segment-footer, hl7-nav, segment-navbar, segment-content, segment-breadcrumb]) HTML_LINK_CHECK_FAILED
en​/using-cql​.html​#​/html​/body​/div​/div​/div​/div​/div​/p​/a at Line 750, column 45errorThe link 'Library-Example.html#cql-content' for "Example.cql" cannot be resolved (valid targets: [toggle-change-display, segment-header, library-example -experimental-, publish-box, bottom, hl7-logo, showChanges, segment-post-footer, hl7-search, hl7-search-lnk, family-logo, family-nav, ig-status, top, root, stripe, segment-footer, hl7-nav, segment-navbar, segment-content, segment-breadcrumb]) HTML_LINK_CHECK_FAILED
en/using-elm.htmlinformationThe html source contains the word 'MAY' but it is not in a text phrase marked as a conformance clause: 'Compiled ELM MAY be distributed either independently, or in combination with the source CQL' CONFORMANCE_STATEMENT_WORD
en/using-modelinfo.htmlinformationThe html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: 'Libraries used to package ModelInfo SHALL conform to the CQLModelInfo profile' CONFORMANCE_STATEMENT_WORD

input/examples/ImplementationGuide-example.json Show Validation Information (3)

PathSeverityMessageValidating
ImplementationGuide​.dependsOn[0] (l1​/c2599)warningThe ImplementationGuide uses package hl7.terminology.r4#6.4.0 released on 2025-05-28, but the most recent appropriate version is 7.2.0. This reference is getting old and the more recent version should be considered IG_DEPENDENCY_VERSION_WARNING_OLD--
ImplementationGuide​.dependsOn[1] (l1​/c2961)warningThe ImplementationGuide uses package hl7.fhir.uv.extensions.r4#5.2.0 released on 2025-02-10, but the most recent appropriate version is 5.3.0. This reference is getting old and the more recent version should be considered IG_DEPENDENCY_VERSION_WARNING_OLD--
ImplementationGuide (l1/c23407)errorHL7 Implementation Guides must state their status explicitly using the extension http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status

Editor's Comment: 16: These should not be required for example content. Raised in Zulip here: https://chat.fhir.org/#narrow/channel/179252-IG-creation/topic/Errors.20about.20implementation.20guide.20standards.20status IG_HL7_STANDARDS_STATUS_REQUIRED
--
ImplementationGuide (l1/c23407)errorHL7 Implementation Guides must state their owning workgroup explicitly using the extension http://hl7.org/fhir/StructureDefinition/structuredefinition-wg

Editor's Comment: 16: These should not be required for example content. Raised in Zulip here: https://chat.fhir.org/#narrow/channel/179252-IG-creation/topic/Errors.20about.20implementation.20guide.20standards.20status IG_HL7_WG_REQUIRED
--

input/examples/Library-ANCCohort.json Show Validation Information (2)

PathSeverityMessageValidating
input/cql/ANCCohort.cqlwarningAn operand identifier domainResource is hiding another identifier of the same name. --
input/cql/ANCCohort.cqlwarningAn operand identifier id is hiding another identifier of the same name. --
Library​.dataRequirement[0]​.codeFilter[0]​.code[0] (l1​/c2390)informationReference to experimental CodeSystem http://hl7.org/fhir/uv/cql/CodeSystem/example|2.1.0-cibuild MSG_EXPERIMENTALParameters

input/examples/Library-Example.json Show Validation Information (2)

PathSeverityMessageValidating
Example (l104/c3)warningAn alias identifier race is hiding another identifier of the same name. --
input/cql/Example.cqlwarningAn operand identifier element is hiding another identifier of the same name. --

input/examples/Library-TypeMappingExample.json Show Validation Information (2)

PathSeverityMessageValidating
input/cql/TypeMappingExample.cqlwarningParameter type System.Vocabulary of parameter ExampleVocabulary is not supported; reported as FHIR.Any --
input/cql/TypeMappingExample.cqlwarningResult type System.CodeSystem of definition CQLCodeSystemExample is not supported; implementations may not be able to use the result of this expression --
input/cql/TypeMappingExample.cqlwarningResult type System.Long of definition CQLLongExample is not supported; implementations may not be able to use the result of this expression --
input/cql/TypeMappingExample.cqlwarningResult type System.ValueSet of definition CQLValueSetExample is not supported; implementations may not be able to use the result of this expression --
input/cql/TypeMappingExample.cqlwarningResult type System.Vocabulary of definition CQLVocabularyExample is not supported; implementations may not be able to use the result of this expression --
input/cql/TypeMappingExample.cqlwarningResult type Interval of System.Time of definition CQLTimeIntervalExample is not supported; implementations may not be able to use the result of this expression --
input/cql/TypeMappingExample.cqlwarningResult type Interval of System.Integer of definition CQLIntegerIntervalExample is not supported; implementations may not be able to use the result of this expression --
input/cql/TypeMappingExample.cqlwarningResult type tuple of X: System.Integer, Y: System.Integer of definition CQLTupleExample is not supported; implementations may not be able to use the result of this expression --
input/cql/TypeMappingExample.cqlwarningResult type List of choice<System.Integer,System.Decimal> of definition CQLChoiceListExample is not supported; implementations may not be able to use the result of this expression --
input/cql/TypeMappingExample.cqlwarningResult type List of tuple of X: System.Integer, Y: System.Integer of definition CQLTupleListExample is not supported; implementations may not be able to use the result of this expression --
input/cql/TypeMappingExample.cqlwarningResult type tuple of id: System.Integer, name: System.String, address: List of tuple of street: System.String, city: System.String, state: System.String of definition CQLComplexTupleExample is not supported; implementations may not be able to use the result of this expression --
input/cql/TypeMappingExample.cqlwarningResult type List of tuple of id: System.Integer, name: System.String, address: List of tuple of street: System.String, city: System.String, state: System.String of definition CQLComplexTupleListExample is not supported; implementations may not be able to use the result of this expression --
input/cql/TypeMappingExample.cqlwarningResult type List of tuple of id: System.Integer, name: System.String, address: List of tuple of street: System.String, city: System.String, state: System.String of definition CQLEmptyListExample is not supported; implementations may not be able to use the result of this expression --
input/cql/TypeMappingExample.cqlwarningResult type List of List of System.Integer of definition CQLListListExample is not supported; implementations may not be able to use the result of this expression --
input/cql/TypeMappingExample.cqlwarningResult type tuple of of definition CQLEmptyTupleExample is not supported; implementations may not be able to use the result of this expression --

input/examples/Parameters-cql-typemappingexampleresult.json Show Validation Information (6)

PathSeverityMessageValidating
Parameters​.parameter[0]​.resource​/*Patient​/example*​/ (l10​/c8)warningConstraint 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) http://hl7.org/fhir/StructureDefinition/DomainResource#dom-6Patient
Parameters​.parameter[2]​.value​.ofType(Coding) (l179​/c6)informationReference to experimental CodeSystem http://hl7.org/fhir/uv/cql/CodeSystem/example|2.1.0-cibuild MSG_EXPERIMENTALPatient
Parameters​.parameter[4]​.value​.ofType(CodeableConcept) (l188​/c6)informationReference to experimental CodeSystem http://hl7.org/fhir/uv/cql/CodeSystem/example|2.1.0-cibuild MSG_EXPERIMENTALPatient
Parameters​.parameter[9]​.value​.ofType(decimal)​.extension[0] (l210​/c8)Slicing InformationThis element does not match any known slice defined in the profile http://hl7.org/fhir/uv/cql/StructureDefinition/cql-evaluationresult|2.1.0-cibuild (this may not be a problem, but you should check that it's not intended to match a slice) Show Reasoning Details_for__matching_against_Profile_Patient
Parameters​.parameter[45]​.resource​/*Observation​/blood-glucose*​/ (l540​/c6)warningConstraint 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) http://hl7.org/fhir/StructureDefinition/DomainResource#dom-6Patient
Parameters​.parameter[46]​.resource​/*Observation​/blood-glucose*​/ (l607​/c6)warningConstraint 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) http://hl7.org/fhir/StructureDefinition/DomainResource#dom-6Patient
Parameters​.parameter[52]​.part[0]​.value​.ofType(uri) (l872​/c86)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-ethnicity'

Editor's Comment: 10: These are intentional, we are illustrating an example of a USCore interaction, but do not want to take a dependency on USCore just for the examples. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
Observation Body Mass Index Profile

input/examples/Parameters-qicore-modelinfo-settings.json Show Validation Information (1)

PathSeverityMessageValidating
Parameters​.parameter[13]​.part[0]​.value​.ofType(uri) (l79​/c104)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-adverseevent'

Editor's Comment: 14: These are intentional, we are providing an example of QICore ModelInfo Settings but do not want to take a dependency on QICore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[14]​.part[0]​.value​.ofType(uri) (l104​/c110)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-allergyintolerance'

Editor's Comment: 14: These are intentional, we are providing an example of QICore ModelInfo Settings but do not want to take a dependency on QICore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[15]​.part[0]​.value​.ofType(uri) (l129​/c105)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-bodystructure'

Editor's Comment: 14: These are intentional, we are providing an example of QICore ModelInfo Settings but do not want to take a dependency on QICore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[16]​.part[0]​.value​.ofType(uri) (l154​/c100)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-careplan'

Editor's Comment: 14: These are intentional, we are providing an example of QICore ModelInfo Settings but do not want to take a dependency on QICore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[17]​.part[0]​.value​.ofType(uri) (l179​/c100)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-careteam'

Editor's Comment: 14: These are intentional, we are providing an example of QICore ModelInfo Settings but do not want to take a dependency on QICore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[18]​.part[0]​.value​.ofType(uri) (l204​/c97)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-claim'

Editor's Comment: 14: These are intentional, we are providing an example of QICore ModelInfo Settings but do not want to take a dependency on QICore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[19]​.part[0]​.value​.ofType(uri) (l229​/c105)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-claimresponse'

Editor's Comment: 14: These are intentional, we are providing an example of QICore ModelInfo Settings but do not want to take a dependency on QICore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[20]​.part[0]​.value​.ofType(uri) (l254​/c105)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-communication'

Editor's Comment: 14: These are intentional, we are providing an example of QICore ModelInfo Settings but do not want to take a dependency on QICore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[21]​.part[0]​.value​.ofType(uri) (l279​/c112)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-communicationnotdone'

Editor's Comment: 14: These are intentional, we are providing an example of QICore ModelInfo Settings but do not want to take a dependency on QICore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[22]​.part[0]​.value​.ofType(uri) (l304​/c109)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-communicationdone'

Editor's Comment: 14: These are intentional, we are providing an example of QICore ModelInfo Settings but do not want to take a dependency on QICore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[23]​.part[0]​.value​.ofType(uri) (l329​/c112)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-communicationrequest'

Editor's Comment: 14: These are intentional, we are providing an example of QICore ModelInfo Settings but do not want to take a dependency on QICore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[24]​.part[0]​.value​.ofType(uri) (l354​/c121)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-condition-encounter-diagnosis'

Editor's Comment: 14: These are intentional, we are providing an example of QICore ModelInfo Settings but do not want to take a dependency on QICore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[25]​.part[0]​.value​.ofType(uri) (l379​/c126)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-condition-problems-health-concerns'

Editor's Comment: 14: These are intentional, we are providing an example of QICore ModelInfo Settings but do not want to take a dependency on QICore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[26]​.part[0]​.value​.ofType(uri) (l404​/c100)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-coverage'

Editor's Comment: 14: These are intentional, we are providing an example of QICore ModelInfo Settings but do not want to take a dependency on QICore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[27]​.part[0]​.value​.ofType(uri) (l429​/c98)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-device'

Editor's Comment: 14: These are intentional, we are providing an example of QICore ModelInfo Settings but do not want to take a dependency on QICore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[28]​.part[0]​.value​.ofType(uri) (l454​/c108)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-deviceprohibited'

Editor's Comment: 14: These are intentional, we are providing an example of QICore ModelInfo Settings but do not want to take a dependency on QICore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[29]​.part[0]​.value​.ofType(uri) (l479​/c105)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-devicerequest'

Editor's Comment: 14: These are intentional, we are providing an example of QICore ModelInfo Settings but do not want to take a dependency on QICore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[30]​.part[0]​.value​.ofType(uri) (l504​/c107)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-devicerequested'

Editor's Comment: 14: These are intentional, we are providing an example of QICore ModelInfo Settings but do not want to take a dependency on QICore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[31]​.part[0]​.value​.ofType(uri) (l529​/c110)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-deviceusestatement'

Editor's Comment: 14: These are intentional, we are providing an example of QICore ModelInfo Settings but do not want to take a dependency on QICore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[32]​.part[0]​.value​.ofType(uri) (l554​/c112)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-diagnosticreport-lab'

Editor's Comment: 14: These are intentional, we are providing an example of QICore ModelInfo Settings but do not want to take a dependency on QICore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[33]​.part[0]​.value​.ofType(uri) (l579​/c113)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-diagnosticreport-note'

Editor's Comment: 14: These are intentional, we are providing an example of QICore ModelInfo Settings but do not want to take a dependency on QICore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[34]​.part[0]​.value​.ofType(uri) (l604​/c101)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-encounter'

Editor's Comment: 14: These are intentional, we are providing an example of QICore ModelInfo Settings but do not want to take a dependency on QICore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[35]​.part[0]​.value​.ofType(uri) (l629​/c111)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-familymemberhistory'

Editor's Comment: 14: These are intentional, we are providing an example of QICore ModelInfo Settings but do not want to take a dependency on QICore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[36]​.part[0]​.value​.ofType(uri) (l654​/c96)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-flag'

Editor's Comment: 14: These are intentional, we are providing an example of QICore ModelInfo Settings but do not want to take a dependency on QICore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[37]​.part[0]​.value​.ofType(uri) (l679​/c96)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-goal'

Editor's Comment: 14: These are intentional, we are providing an example of QICore ModelInfo Settings but do not want to take a dependency on QICore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[38]​.part[0]​.value​.ofType(uri) (l704​/c104)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-imagingstudy'

Editor's Comment: 14: These are intentional, we are providing an example of QICore ModelInfo Settings but do not want to take a dependency on QICore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[39]​.part[0]​.value​.ofType(uri) (l729​/c104)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-immunization'

Editor's Comment: 14: These are intentional, we are providing an example of QICore ModelInfo Settings but do not want to take a dependency on QICore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[40]​.part[0]​.value​.ofType(uri) (l754​/c108)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-immunizationdone'

Editor's Comment: 14: These are intentional, we are providing an example of QICore ModelInfo Settings but do not want to take a dependency on QICore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[41]​.part[0]​.value​.ofType(uri) (l779​/c111)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-immunizationnotdone'

Editor's Comment: 14: These are intentional, we are providing an example of QICore ModelInfo Settings but do not want to take a dependency on QICore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[42]​.part[0]​.value​.ofType(uri) (l804​/c114)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-immunizationevaluation'

Editor's Comment: 14: These are intentional, we are providing an example of QICore ModelInfo Settings but do not want to take a dependency on QICore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[43]​.part[0]​.value​.ofType(uri) (l829​/c118)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-immunizationrecommendation'

Editor's Comment: 14: These are intentional, we are providing an example of QICore ModelInfo Settings but do not want to take a dependency on QICore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[44]​.part[0]​.value​.ofType(uri) (l854​/c107)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-observation-lab'

Editor's Comment: 14: These are intentional, we are providing an example of QICore ModelInfo Settings but do not want to take a dependency on QICore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[45]​.part[0]​.value​.ofType(uri) (l879​/c100)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-location'

Editor's Comment: 14: These are intentional, we are providing an example of QICore ModelInfo Settings but do not want to take a dependency on QICore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[46]​.part[0]​.value​.ofType(uri) (l904​/c102)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-medication'

Editor's Comment: 14: These are intentional, we are providing an example of QICore ModelInfo Settings but do not want to take a dependency on QICore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[47]​.part[0]​.value​.ofType(uri) (l929​/c112)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-medicationprohibited'

Editor's Comment: 14: These are intentional, we are providing an example of QICore ModelInfo Settings but do not want to take a dependency on QICore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[48]​.part[0]​.value​.ofType(uri) (l954​/c116)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-medicationadministration'

Editor's Comment: 14: These are intentional, we are providing an example of QICore ModelInfo Settings but do not want to take a dependency on QICore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[49]​.part[0]​.value​.ofType(uri) (l979​/c120)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-medicationadministrationdone'

Editor's Comment: 14: These are intentional, we are providing an example of QICore ModelInfo Settings but do not want to take a dependency on QICore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[50]​.part[0]​.value​.ofType(uri) (l1004​/c123)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-medicationadministrationnotdone'

Editor's Comment: 14: These are intentional, we are providing an example of QICore ModelInfo Settings but do not want to take a dependency on QICore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[51]​.part[0]​.value​.ofType(uri) (l1029​/c110)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-medicationdispense'

Editor's Comment: 14: These are intentional, we are providing an example of QICore ModelInfo Settings but do not want to take a dependency on QICore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[52]​.part[0]​.value​.ofType(uri) (l1054​/c118)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-medicationdispensedeclined'

Editor's Comment: 14: These are intentional, we are providing an example of QICore ModelInfo Settings but do not want to take a dependency on QICore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[53]​.part[0]​.value​.ofType(uri) (l1079​/c114)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-medicationdispensedone'

Editor's Comment: 14: These are intentional, we are providing an example of QICore ModelInfo Settings but do not want to take a dependency on QICore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[54]​.part[0]​.value​.ofType(uri) (l1104​/c109)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-medicationrequest'

Editor's Comment: 14: These are intentional, we are providing an example of QICore ModelInfo Settings but do not want to take a dependency on QICore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[55]​.part[0]​.value​.ofType(uri) (l1129​/c111)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-medicationrequested'

Editor's Comment: 14: These are intentional, we are providing an example of QICore ModelInfo Settings but do not want to take a dependency on QICore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[56]​.part[0]​.value​.ofType(uri) (l1154​/c111)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-medicationstatement'

Editor's Comment: 14: These are intentional, we are providing an example of QICore ModelInfo Settings but do not want to take a dependency on QICore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[57]​.part[0]​.value​.ofType(uri) (l1179​/c114)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-nonpatient-observation'

Editor's Comment: 14: These are intentional, we are providing an example of QICore ModelInfo Settings but do not want to take a dependency on QICore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[58]​.part[0]​.value​.ofType(uri) (l1204​/c106)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-nutritionorder'

Editor's Comment: 14: These are intentional, we are providing an example of QICore ModelInfo Settings but do not want to take a dependency on QICore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[59]​.part[0]​.value​.ofType(uri) (l1229​/c119)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-observation-clinical-result'

Editor's Comment: 14: These are intentional, we are providing an example of QICore ModelInfo Settings but do not want to take a dependency on QICore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[60]​.part[0]​.value​.ofType(uri) (l1254​/c124)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-observation-screening-assessment'

Editor's Comment: 14: These are intentional, we are providing an example of QICore ModelInfo Settings but do not want to take a dependency on QICore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[61]​.part[0]​.value​.ofType(uri) (l1279​/c104)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-organization'

Editor's Comment: 14: These are intentional, we are providing an example of QICore ModelInfo Settings but do not want to take a dependency on QICore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[62]​.part[0]​.value​.ofType(uri) (l1304​/c99)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-patient'

Editor's Comment: 14: These are intentional, we are providing an example of QICore ModelInfo Settings but do not want to take a dependency on QICore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[63]​.part[0]​.value​.ofType(uri) (l1329​/c104)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-practitioner'

Editor's Comment: 14: These are intentional, we are providing an example of QICore ModelInfo Settings but do not want to take a dependency on QICore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[64]​.part[0]​.value​.ofType(uri) (l1354​/c108)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-practitionerrole'

Editor's Comment: 14: These are intentional, we are providing an example of QICore ModelInfo Settings but do not want to take a dependency on QICore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[65]​.part[0]​.value​.ofType(uri) (l1379​/c101)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-procedure'

Editor's Comment: 14: These are intentional, we are providing an example of QICore ModelInfo Settings but do not want to take a dependency on QICore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[66]​.part[0]​.value​.ofType(uri) (l1404​/c105)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-proceduredone'

Editor's Comment: 14: These are intentional, we are providing an example of QICore ModelInfo Settings but do not want to take a dependency on QICore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[67]​.part[0]​.value​.ofType(uri) (l1429​/c108)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-procedurenotdone'

Editor's Comment: 14: These are intentional, we are providing an example of QICore ModelInfo Settings but do not want to take a dependency on QICore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[68]​.part[0]​.value​.ofType(uri) (l1454​/c113)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-questionnaireresponse'

Editor's Comment: 14: These are intentional, we are providing an example of QICore ModelInfo Settings but do not want to take a dependency on QICore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[69]​.part[0]​.value​.ofType(uri) (l1479​/c105)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-relatedperson'

Editor's Comment: 14: These are intentional, we are providing an example of QICore ModelInfo Settings but do not want to take a dependency on QICore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[70]​.part[0]​.value​.ofType(uri) (l1504​/c109)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-serviceprohibited'

Editor's Comment: 14: These are intentional, we are providing an example of QICore ModelInfo Settings but do not want to take a dependency on QICore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[71]​.part[0]​.value​.ofType(uri) (l1529​/c106)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-servicerequest'

Editor's Comment: 14: These are intentional, we are providing an example of QICore ModelInfo Settings but do not want to take a dependency on QICore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[72]​.part[0]​.value​.ofType(uri) (l1554​/c108)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-servicerequested'

Editor's Comment: 14: These are intentional, we are providing an example of QICore ModelInfo Settings but do not want to take a dependency on QICore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[73]​.part[0]​.value​.ofType(uri) (l1579​/c110)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-simple-observation'

Editor's Comment: 14: These are intentional, we are providing an example of QICore ModelInfo Settings but do not want to take a dependency on QICore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[74]​.part[0]​.value​.ofType(uri) (l1604​/c101)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-substance'

Editor's Comment: 14: These are intentional, we are providing an example of QICore ModelInfo Settings but do not want to take a dependency on QICore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[75]​.part[0]​.value​.ofType(uri) (l1629​/c96)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-task'

Editor's Comment: 14: These are intentional, we are providing an example of QICore ModelInfo Settings but do not want to take a dependency on QICore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[76]​.part[0]​.value​.ofType(uri) (l1654​/c100)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-taskdone'

Editor's Comment: 14: These are intentional, we are providing an example of QICore ModelInfo Settings but do not want to take a dependency on QICore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[77]​.part[0]​.value​.ofType(uri) (l1679​/c104)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-taskrejected'

Editor's Comment: 14: These are intentional, we are providing an example of QICore ModelInfo Settings but do not want to take a dependency on QICore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
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--
Parameters.parameter[65] (l1374/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[66] (l1399/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[67] (l1424/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[68] (l1449/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[69] (l1474/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[70] (l1499/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[71] (l1524/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[72] (l1549/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[73] (l1574/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[74] (l1599/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[75] (l1624/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[76] (l1649/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[77] (l1674/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/examples/Parameters-uscore-modelinfo-settings.json Show Validation Information (1)

PathSeverityMessageValidating
Parameters​.parameter[13]​.part[0]​.value​.ofType(uri) (l79​/c109)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-allergyintolerance'

Editor's Comment: 15: These are intentional, we are providing an example of USCore ModelInfo Settings, but do not want to take a dependency on USCore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[14]​.part[0]​.value​.ofType(uri) (l104​/c113)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-average-blood-pressure'

Editor's Comment: 15: These are intentional, we are providing an example of USCore ModelInfo Settings, but do not want to take a dependency on USCore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[15]​.part[0]​.value​.ofType(uri) (l129​/c94)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-bmi'

Editor's Comment: 15: These are intentional, we are providing an example of USCore ModelInfo Settings, but do not want to take a dependency on USCore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[16]​.part[0]​.value​.ofType(uri) (l154​/c105)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-blood-pressure'

Editor's Comment: 15: These are intentional, we are providing an example of USCore ModelInfo Settings, but do not want to take a dependency on USCore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[17]​.part[0]​.value​.ofType(uri) (l179​/c102)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-body-height'

Editor's Comment: 15: These are intentional, we are providing an example of USCore ModelInfo Settings, but do not want to take a dependency on USCore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[18]​.part[0]​.value​.ofType(uri) (l204​/c107)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-body-temperature'

Editor's Comment: 15: These are intentional, we are providing an example of USCore ModelInfo Settings, but do not want to take a dependency on USCore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[19]​.part[0]​.value​.ofType(uri) (l229​/c102)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-body-weight'

Editor's Comment: 15: These are intentional, we are providing an example of USCore ModelInfo Settings, but do not want to take a dependency on USCore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[20]​.part[0]​.value​.ofType(uri) (l254​/c117)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-care-experience-preference'

Editor's Comment: 15: These are intentional, we are providing an example of USCore ModelInfo Settings, but do not want to take a dependency on USCore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[21]​.part[0]​.value​.ofType(uri) (l279​/c99)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-careplan'

Editor's Comment: 15: These are intentional, we are providing an example of USCore ModelInfo Settings, but do not want to take a dependency on USCore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[22]​.part[0]​.value​.ofType(uri) (l304​/c99)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-careteam'

Editor's Comment: 15: These are intentional, we are providing an example of USCore ModelInfo Settings, but do not want to take a dependency on USCore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[23]​.part[0]​.value​.ofType(uri) (l329​/c120)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-condition-encounter-diagnosis'

Editor's Comment: 15: These are intentional, we are providing an example of USCore ModelInfo Settings, but do not want to take a dependency on USCore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[24]​.part[0]​.value​.ofType(uri) (l354​/c125)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-condition-problems-health-concerns'

Editor's Comment: 15: These are intentional, we are providing an example of USCore ModelInfo Settings, but do not want to take a dependency on USCore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[25]​.part[0]​.value​.ofType(uri) (l379​/c99)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-coverage'

Editor's Comment: 15: These are intentional, we are providing an example of USCore ModelInfo Settings, but do not want to take a dependency on USCore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[26]​.part[0]​.value​.ofType(uri) (l404​/c111)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-diagnosticreport-lab'

Editor's Comment: 15: These are intentional, we are providing an example of USCore ModelInfo Settings, but do not want to take a dependency on USCore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[27]​.part[0]​.value​.ofType(uri) (l429​/c112)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-diagnosticreport-note'

Editor's Comment: 15: These are intentional, we are providing an example of USCore ModelInfo Settings, but do not want to take a dependency on USCore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[28]​.part[0]​.value​.ofType(uri) (l454​/c108)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-documentreference'

Editor's Comment: 15: These are intentional, we are providing an example of USCore ModelInfo Settings, but do not want to take a dependency on USCore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[29]​.part[0]​.value​.ofType(uri) (l479​/c100)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-encounter'

Editor's Comment: 15: These are intentional, we are providing an example of USCore ModelInfo Settings, but do not want to take a dependency on USCore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[30]​.part[0]​.value​.ofType(uri) (l504​/c95)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-goal'

Editor's Comment: 15: These are intentional, we are providing an example of USCore ModelInfo Settings, but do not want to take a dependency on USCore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[31]​.part[0]​.value​.ofType(uri) (l529​/c109)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-head-circumference'

Editor's Comment: 15: These are intentional, we are providing an example of USCore ModelInfo Settings, but do not want to take a dependency on USCore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[32]​.part[0]​.value​.ofType(uri) (l554​/c101)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-heart-rate'

Editor's Comment: 15: These are intentional, we are providing an example of USCore ModelInfo Settings, but do not want to take a dependency on USCore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[33]​.part[0]​.value​.ofType(uri) (l579​/c103)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-immunization'

Editor's Comment: 15: These are intentional, we are providing an example of USCore ModelInfo Settings, but do not want to take a dependency on USCore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[34]​.part[0]​.value​.ofType(uri) (l604​/c109)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-implantable-device'

Editor's Comment: 15: These are intentional, we are providing an example of USCore ModelInfo Settings, but do not want to take a dependency on USCore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[35]​.part[0]​.value​.ofType(uri) (l629​/c106)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-lab'

Editor's Comment: 15: These are intentional, we are providing an example of USCore ModelInfo Settings, but do not want to take a dependency on USCore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[36]​.part[0]​.value​.ofType(uri) (l654​/c99)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-location'

Editor's Comment: 15: These are intentional, we are providing an example of USCore ModelInfo Settings, but do not want to take a dependency on USCore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[37]​.part[0]​.value​.ofType(uri) (l679​/c101)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-medication'

Editor's Comment: 15: These are intentional, we are providing an example of USCore ModelInfo Settings, but do not want to take a dependency on USCore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[38]​.part[0]​.value​.ofType(uri) (l704​/c109)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-medicationdispense'

Editor's Comment: 15: These are intentional, we are providing an example of USCore ModelInfo Settings, but do not want to take a dependency on USCore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[39]​.part[0]​.value​.ofType(uri) (l729​/c108)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-medicationrequest'

Editor's Comment: 15: These are intentional, we are providing an example of USCore ModelInfo Settings, but do not want to take a dependency on USCore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[40]​.part[0]​.value​.ofType(uri) (l754​/c118)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-clinical-result'

Editor's Comment: 15: These are intentional, we are providing an example of USCore ModelInfo Settings, but do not want to take a dependency on USCore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[41]​.part[0]​.value​.ofType(uri) (l779​/c113)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-occupation'

Editor's Comment: 15: These are intentional, we are providing an example of USCore ModelInfo Settings, but do not want to take a dependency on USCore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[42]​.part[0]​.value​.ofType(uri) (l804​/c118)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-pregnancyintent'

Editor's Comment: 15: These are intentional, we are providing an example of USCore ModelInfo Settings, but do not want to take a dependency on USCore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[43]​.part[0]​.value​.ofType(uri) (l829​/c118)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-pregnancystatus'

Editor's Comment: 15: These are intentional, we are providing an example of USCore ModelInfo Settings, but do not want to take a dependency on USCore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[44]​.part[0]​.value​.ofType(uri) (l854​/c123)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-screening-assessment'

Editor's Comment: 15: These are intentional, we are providing an example of USCore ModelInfo Settings, but do not want to take a dependency on USCore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[45]​.part[0]​.value​.ofType(uri) (l879​/c121)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-sexual-orientation'

Editor's Comment: 15: These are intentional, we are providing an example of USCore ModelInfo Settings, but do not want to take a dependency on USCore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[46]​.part[0]​.value​.ofType(uri) (l904​/c103)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-organization'

Editor's Comment: 15: These are intentional, we are providing an example of USCore ModelInfo Settings, but do not want to take a dependency on USCore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[47]​.part[0]​.value​.ofType(uri) (l929​/c98)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-patient'

Editor's Comment: 15: These are intentional, we are providing an example of USCore ModelInfo Settings, but do not want to take a dependency on USCore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[48]​.part[0]​.value​.ofType(uri) (l954​/c104)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/pediatric-bmi-for-age'

Editor's Comment: 15: These are intentional, we are providing an example of USCore ModelInfo Settings, but do not want to take a dependency on USCore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[49]​.part[0]​.value​.ofType(uri) (l979​/c130)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/head-occipital-frontal-circumference-percentile'

Editor's Comment: 15: These are intentional, we are providing an example of USCore ModelInfo Settings, but do not want to take a dependency on USCore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[50]​.part[0]​.value​.ofType(uri) (l1004​/c110)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/pediatric-weight-for-height'

Editor's Comment: 15: These are intentional, we are providing an example of USCore ModelInfo Settings, but do not want to take a dependency on USCore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[51]​.part[0]​.value​.ofType(uri) (l1029​/c103)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-practitioner'

Editor's Comment: 15: These are intentional, we are providing an example of USCore ModelInfo Settings, but do not want to take a dependency on USCore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[52]​.part[0]​.value​.ofType(uri) (l1054​/c107)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-practitionerrole'

Editor's Comment: 15: These are intentional, we are providing an example of USCore ModelInfo Settings, but do not want to take a dependency on USCore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[53]​.part[0]​.value​.ofType(uri) (l1079​/c100)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-procedure'

Editor's Comment: 15: These are intentional, we are providing an example of USCore ModelInfo Settings, but do not want to take a dependency on USCore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[54]​.part[0]​.value​.ofType(uri) (l1104​/c101)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-provenance'

Editor's Comment: 15: These are intentional, we are providing an example of USCore ModelInfo Settings, but do not want to take a dependency on USCore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[55]​.part[0]​.value​.ofType(uri) (l1129​/c105)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-pulse-oximetry'

Editor's Comment: 15: These are intentional, we are providing an example of USCore ModelInfo Settings, but do not want to take a dependency on USCore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[56]​.part[0]​.value​.ofType(uri) (l1154​/c112)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-questionnaireresponse'

Editor's Comment: 15: These are intentional, we are providing an example of USCore ModelInfo Settings, but do not want to take a dependency on USCore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[57]​.part[0]​.value​.ofType(uri) (l1179​/c104)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-relatedperson'

Editor's Comment: 15: These are intentional, we are providing an example of USCore ModelInfo Settings, but do not want to take a dependency on USCore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[58]​.part[0]​.value​.ofType(uri) (l1204​/c107)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-respiratory-rate'

Editor's Comment: 15: These are intentional, we are providing an example of USCore ModelInfo Settings, but do not want to take a dependency on USCore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[59]​.part[0]​.value​.ofType(uri) (l1229​/c105)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-servicerequest'

Editor's Comment: 15: These are intentional, we are providing an example of USCore ModelInfo Settings, but do not want to take a dependency on USCore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[60]​.part[0]​.value​.ofType(uri) (l1254​/c109)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-simple-observation'

Editor's Comment: 15: These are intentional, we are providing an example of USCore ModelInfo Settings, but do not want to take a dependency on USCore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[61]​.part[0]​.value​.ofType(uri) (l1279​/c104)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-smokingstatus'

Editor's Comment: 15: These are intentional, we are providing an example of USCore ModelInfo Settings, but do not want to take a dependency on USCore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[62]​.part[0]​.value​.ofType(uri) (l1304​/c99)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-specimen'

Editor's Comment: 15: These are intentional, we are providing an example of USCore ModelInfo Settings, but do not want to take a dependency on USCore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[63]​.part[0]​.value​.ofType(uri) (l1329​/c124)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-treatment-intervention-preference'

Editor's Comment: 15: These are intentional, we are providing an example of USCore ModelInfo Settings, but do not want to take a dependency on USCore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
Parameters​.parameter[64]​.part[0]​.value​.ofType(uri) (l1354​/c102)errorNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-vital-signs'

Editor's Comment: 15: These are intentional, we are providing an example of USCore ModelInfo Settings, but do not want to take a dependency on USCore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies Type_Specific_Checks_DT_URL_Resolve
CQL Model Info Settings
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/examples/ValueSet-publishable-example.json Show Validation Information (1)

PathSeverityMessageValidating
ValueSet.expansion (l1/c8036)warningThis expansion has no parameters; in the absence of the parameters that controlled the expansion, systems may not be able to determine whether it is safe to use this expansion --
ValueSet.expansion (l1/c8036)informationThis expansion has no identifier. Identifiers are recommended to help with audit and traceability VALUESET_EXPANSION_NO_IDENTIFIER--
ValueSet.expansion (l1/c8036)warningBecause the expansion uses system 'http://hl7.org/fhir/uv/cql/CodeSystem/example' without a version, it should list the system using the expansion parameter 'used-codesystem' --

input/extensions/StructureDefinition-cql-selectivity.xml Show Validation Information (1)

PathSeverityMessageValidating
StructureDefinition​.where(url = 'http:​/​/hl7​.org​/fhir​/uv​/cql​/StructureDefinition​/cql-selectivity')errorConformance resource /scratch/repo/input/extensions/StructureDefinition-cql-selectivity.xml - the canonical URL (http://hl7.org/fhir/uv/cql/StructureDefinition/cqf-selectivity) does not match the URL (http://hl7.org/fhir/uv/cql/StructureDefinition/cql-selectivity). Use the special-url parameter if you really mean for it not to match RESOURCE_CANONICAL_MISMATCH--
StructureDefinition.urlerrorResource id/url mismatch: cqf-selectivity/http://hl7.org/fhir/uv/cql/StructureDefinition/cql-selectivity RESOURCE_ID_MISMATCH--
StructureDefinition​.snapshot​.element[12]​.binding​.valueSet (l1​/c73391)errorA definition could not be found for Canonical URL 'http://hl7.org/fhir/ValueSet/selectivity-coverage' TYPE_SPECIFIC_CHECKS_DT_CANONICAL_RESOLVEStructureDefinition
StructureDefinition​.snapshot​.element[17]​.binding​.valueSet (l1​/c77395)errorA definition could not be found for Canonical URL 'http://hl7.org/fhir/ValueSet/selectivity-inclusivity' TYPE_SPECIFIC_CHECKS_DT_CANONICAL_RESOLVEStructureDefinition
StructureDefinition​.snapshot​.element[22]​.binding​.valueSet (l1​/c81339)errorA definition could not be found for Canonical URL 'http://hl7.org/fhir/ValueSet/selectivity-form' TYPE_SPECIFIC_CHECKS_DT_CANONICAL_RESOLVEStructureDefinition
StructureDefinition​.differential​.element[8]​.binding​.valueSet (l1​/c95819)errorA definition could not be found for Canonical URL 'http://hl7.org/fhir/ValueSet/selectivity-coverage' TYPE_SPECIFIC_CHECKS_DT_CANONICAL_RESOLVEStructureDefinition
StructureDefinition​.differential​.element[12]​.binding​.valueSet (l1​/c96521)errorA definition could not be found for Canonical URL 'http://hl7.org/fhir/ValueSet/selectivity-inclusivity' TYPE_SPECIFIC_CHECKS_DT_CANONICAL_RESOLVEStructureDefinition
StructureDefinition​.differential​.element[16]​.binding​.valueSet (l1​/c97170)errorA definition could not be found for Canonical URL 'http://hl7.org/fhir/ValueSet/selectivity-form' TYPE_SPECIFIC_CHECKS_DT_CANONICAL_RESOLVEStructureDefinition
StructureDefinition (l1/c98836)informationThe resource status 'draft' and the standards status 'trial-use' may not be consistent and should be reviewed VALIDATION_VAL_STATUS_INCONSISTENT_HINTStructureDefinition
StructureDefinition​.where(url = 'http:​/​/hl7​.org​/fhir​/uv​/cql​/StructureDefinition​/cql-selectivity')warningThe Implementation Guide contains no examples for this extension --
input​/extensions​/StructureDefinition-cql-selectivityerrorURL Mismatch http://hl7.org/fhir/uv/cql/StructureDefinition/cqf-selectivity vs http://hl7.org/fhir/uv/cql/StructureDefinition/cql-selectivity --

input/profiles/StructureDefinition-cql-evaluationresult.json Show Validation Information (1)

PathSeverityMessageValidating
StructureDefinition​.snapshot​.element[14]​.type[0]​.profile[0] (l1​/c53148)warningThere are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/data-absent-reason'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer, or use the [IG Parameter `pin-canonicals`](https://hl7.org/fhir/tools/CodeSystem-ig-parameters.html). Using version '5.3.0', found versions: 4.0.1 (from hl7.fhir.r4.core#4.0.1), 5.3.0 (from hl7.fhir.uv.extensions.r4#current). Suggested fix: change the canonical reference from 'http://hl7.org/fhir/StructureDefinition/data-absent-reason' to 'http://hl7.org/fhir/StructureDefinition/data-absent-reason|5.3.0' TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONSStructureDefinition
StructureDefinition​.differential​.element[5]​.type[0]​.profile[0] (l1​/c63449)warningThere are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/data-absent-reason'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer, or use the [IG Parameter `pin-canonicals`](https://hl7.org/fhir/tools/CodeSystem-ig-parameters.html). Using version '5.3.0', found versions: 4.0.1 (from hl7.fhir.r4.core#4.0.1), 5.3.0 (from hl7.fhir.uv.extensions.r4#current). Suggested fix: change the canonical reference from 'http://hl7.org/fhir/StructureDefinition/data-absent-reason' to 'http://hl7.org/fhir/StructureDefinition/data-absent-reason|5.3.0' TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONSStructureDefinition

input/profiles/StructureDefinition-cql-groupdefinition.json Show Validation Information (1)

PathSeverityMessageValidating
StructureDefinition​.snapshot​.element[13]warningThe type of profile http://hl7.org/fhir/StructureDefinition/cqf-cqlLibrary cannot be checked as the profile is not known --
StructureDefinition​.snapshot​.element[13]​.type[0]​.profile[0] (l1​/c45256)errorA definition could not be found for Canonical URL 'http://hl7.org/fhir/StructureDefinition/cqf-cqlLibrary' TYPE_SPECIFIC_CHECKS_DT_CANONICAL_RESOLVEStructureDefinition
StructureDefinition​.differential​.element[3]​.type[0]​.profile[0] (l1​/c83677)errorA definition could not be found for Canonical URL 'http://hl7.org/fhir/StructureDefinition/cqf-cqlLibrary' TYPE_SPECIFIC_CHECKS_DT_CANONICAL_RESOLVEStructureDefinition
StructureDefinition​.differential​.element[3]​.type[0]​.profile[0]warningUnable to resolve profile http://hl7.org/fhir/StructureDefinition/cqf-cqlLibrary SD_ED_TYPE_PROFILE_UNKNOWN--
StructureDefinition​.snapshot​.element[13]​.type[0]​.profile[0]warningUnable to resolve profile http://hl7.org/fhir/StructureDefinition/cqf-cqlLibrary SD_ED_TYPE_PROFILE_UNKNOWN--
cql-groupdefinitionerrorUnable to find Extension 'http://hl7.org/fhir/StructureDefinition/cqf-cqlLibrary' referenced at http://hl7.org/fhir/uv/cql/StructureDefinition/cql-groupdefinition differential Group.extension (cqlLibrary) Unable to find Extension 'http://hl7.org/fhir/StructureDefinition/cqf-cqlLibrary' referenced at http://hl7.org/fhir/uv/cql/StructureDefinition/cql-groupdefinition differential Group.extension (cqlLibrary)--
cql-groupdefinitionerrorUnable to find Extension 'http://hl7.org/fhir/StructureDefinition/cqf-cqlLibrary' referenced at http://hl7.org/fhir/uv/cql/StructureDefinition/cql-groupdefinition snapshot Group.extension (cqlLibrary) Unable to find Extension 'http://hl7.org/fhir/StructureDefinition/cqf-cqlLibrary' referenced at http://hl7.org/fhir/uv/cql/StructureDefinition/cql-groupdefinition snapshot Group.extension (cqlLibrary)--
StructureDefinition​.where(url = 'http:​/​/hl7​.org​/fhir​/uv​/cql​/StructureDefinition​/cql-groupdefinition')warningThe Implementation Guide contains no examples for this profile --

input/resources/Library-FHIR-ModelInfo.json Show Validation Information (1)

PathSeverityMessageValidating
Library.text.diverrorHyperlink 'http://hl7.org/fhir/uv/cql/fhir-modelinfo.html' at 'div/table/tbody/tr/td/div/p/a' for 'FHIR ModelInfo' does not resolve --

input/resources/Library-FHIRCommon.json Show Validation Information (2)

PathSeverityMessageValidating
input/cql/FHIRCommon.cqlwarningAn operand identifier references is hiding another identifier of the same name. --
input/cql/FHIRCommon.cqlwarningAn operand identifier element is hiding another identifier of the same name. --
input/cql/FHIRCommon.cqlwarningAn operand identifier url is hiding another identifier of the same name. --
FHIRCommon (l418/c24)warningAn expression identifier active is hiding another identifier of the same name. --
FHIRCommon (l456/c24)warningAn expression identifier unconfirmed is hiding another identifier of the same name. --
FHIRCommon (l469/c24)warningAn expression identifier provisional is hiding another identifier of the same name. --
FHIRCommon (l482/c24)warningAn expression identifier differential is hiding another identifier of the same name. --
FHIRCommon (l495/c24)warningAn expression identifier confirmed is hiding another identifier of the same name. --
FHIRCommon (l508/c24)warningAn expression identifier refuted is hiding another identifier of the same name. --
FHIRCommon (l543/c7)warningA let identifier abatement is hiding another identifier of the same name. --
FHIRCommon (l544/c7)warningA let identifier resolutionAge is hiding another identifier of the same name. --
FHIRCommon (l604/c24)warningAn expression identifier inactive is hiding another identifier of the same name. --
FHIRCommon (l617/c24)warningAn expression identifier resolved is hiding another identifier of the same name. --

input/resources/Library-FHIRHelpers.json Show Validation Information (2)

PathSeverityMessageValidating
input/cql/FHIRHelpers.cqlwarningAn operand identifier reference is hiding another identifier of the same name. --

Suppressed Messages (Warnings, hints, broken links)

01: This is an example CodeSystem and labeled according to TSMG guidance, so does not require an exemption

02: Accepted references to draft published content

03: Accepted references to experimental content, these are examples, so intentionally marked experimental

04: This structure definition is not a conformance artifact in this ig, it is an example

05: This structure definition is not a conformance artifact in this ig, it is an example

06: This is inherited from the base definition

07: This example is illustrating how to return a result, so narrative is not relevant to this example

08: These examples are illustrating how to return resources generally, so the performer element is not relevant to this example

09: This is coming from the snapshot, outside of the control of this example

10: These are intentional, we are illustrating an example of a USCore interaction, but do not want to take a dependency on USCore just for the examples. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies

11: This is intentional, because we want the link to the fhir-modelinfo page in the published IG, this will resolve once published, but I can't use jekyll parameterization to get the correct url. See https://chat.fhir.org/#narrow/channel/179252-IG-creation/topic/Links.20in.20resources.20in.20the.20IG

12: Accepted warnings from CQL about identifier hiding

13: These are valid external value set URLs that are referenced by this example

14: These are intentional, we are providing an example of QICore ModelInfo Settings but do not want to take a dependency on QICore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies

15: These are intentional, we are providing an example of USCore ModelInfo Settings, but do not want to take a dependency on USCore. See https://chat.fhir.org/#narrow/channel/179239-tooling/topic/Dev.20Dependencies

16: These should not be required for example content. Raised in Zulip here: https://chat.fhir.org/#narrow/channel/179252-IG-creation/topic/Errors.20about.20implementation.20guide.20standards.20status

17: Discussion on canonical pinning, we would use `|*` but this isn't yet supported by tooling. See discussion in Zulip here: https://chat.fhir.org/#narrow/channel/179252-IG-creation/topic/Canonical.20Pinning/with/527471341

Errors sorted by type


Details_for__matching_against_Profile_

input/examples/Parameters-cql-typemappingexampleresult.jsonThis element does not match any known slice defined in the profile http://hl7.org/fhir/uv/cql/StructureDefinition/cql-evaluationresult|2.1.0-cibuild (this may not be a problem, but you should check that it's not intended to match a slice)Patient

IG_DEPENDENCY_VERSION_WARNING_OLD

input/examples/ImplementationGuide-example.jsonThe ImplementationGuide uses package hl7.terminology.r4#6.4.0 released on 2025-05-28, but the most recent appropriate version is 7.2.0. This reference is getting old and the more recent version should be considered--
input/examples/ImplementationGuide-example.jsonThe ImplementationGuide uses package hl7.fhir.uv.extensions.r4#5.2.0 released on 2025-02-10, but the most recent appropriate version is 5.3.0. This reference is getting old and the more recent version should be considered--

IG_HL7_STANDARDS_STATUS_REQUIRED

input/examples/ImplementationGuide-example.jsonHL7 Implementation Guides must state their status explicitly using the extension http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status--

IG_HL7_WG_REQUIRED

input/examples/ImplementationGuide-example.jsonHL7 Implementation Guides must state their owning workgroup explicitly using the extension http://hl7.org/fhir/StructureDefinition/structuredefinition-wg--

MSG_DEPENDS_ON_DEPRECATED_NOTE

input/examples/StructureDefinition-cql-dangersigns-profile-example.jsonThe extension http://hl7.org/fhir/StructureDefinition/elementdefinition-maxValueSet|5.3.0 is deprecated with the note: 'Use additionalBinding extension or element instead'CQL StructureDefinition

MSG_EXPERIMENTAL

input/examples/Library-ANCCohort.jsonReference to experimental CodeSystem http://hl7.org/fhir/uv/cql/CodeSystem/example|2.1.0-cibuildParameters
input/examples/Parameters-cql-typemappingexampleresult.jsonReference to experimental CodeSystem http://hl7.org/fhir/uv/cql/CodeSystem/example|2.1.0-cibuildPatient
input/examples/Parameters-cql-typemappingexampleresult.jsonReference to experimental CodeSystem http://hl7.org/fhir/uv/cql/CodeSystem/example|2.1.0-cibuildPatient
input/examples/StructureDefinition-cql-dangersigns-profile-example.jsonReference to experimental CodeSystem http://hl7.org/fhir/uv/cql/CodeSystem/example|2.1.0-cibuildCQL StructureDefinition
input/examples/StructureDefinition-cql-dangersigns-profile-example.jsonReference to experimental CodeSystem http://hl7.org/fhir/uv/cql/CodeSystem/example|2.1.0-cibuildCQL StructureDefinition
input/examples/StructureDefinition-cql-dangersigns-profile-example.jsonReference to experimental CodeSystem http://hl7.org/fhir/uv/cql/CodeSystem/example|2.1.0-cibuildCQL StructureDefinition
input/examples/StructureDefinition-cql-specifichealthconcerns-profile-example.jsonReference to experimental CodeSystem http://hl7.org/fhir/uv/cql/CodeSystem/example|2.1.0-cibuildCQL StructureDefinition
input/examples/StructureDefinition-cql-specifichealthconcerns-profile-example.jsonReference to experimental CodeSystem http://hl7.org/fhir/uv/cql/CodeSystem/example|2.1.0-cibuildCQL StructureDefinition
input/examples/ValueSet-shareable-example.jsonReference to experimental CodeSystem http://hl7.org/fhir/uv/cql/CodeSystem/example|2.1.0-cibuild--
input/examples/ValueSet-shareable-example.jsonReference to experimental CodeSystem http://hl7.org/fhir/uv/cql/CodeSystem/example|2.1.0-cibuild--
input/examples/ValueSet-shareable-example.jsonReference to experimental CodeSystem http://hl7.org/fhir/uv/cql/CodeSystem/example|2.1.0-cibuild--
input/examples/ValueSet-shareable-example.jsonReference to experimental CodeSystem http://hl7.org/fhir/uv/cql/CodeSystem/example|2.1.0-cibuild--
input/examples/ValueSet-shareable-example.jsonReference to experimental CodeSystem http://hl7.org/fhir/uv/cql/CodeSystem/example|2.1.0-cibuild--
input/examples/ValueSet-shareable-example.jsonReference to experimental CodeSystem http://hl7.org/fhir/uv/cql/CodeSystem/example|2.1.0-cibuild--
input/examples/ValueSet-shareable-example.jsonReference to experimental CodeSystem http://hl7.org/fhir/uv/cql/CodeSystem/example|2.1.0-cibuild--
input/examples/ValueSet-shareable-example.jsonReference to experimental CodeSystem http://hl7.org/fhir/uv/cql/CodeSystem/example|2.1.0-cibuild--
input/examples/ValueSet-shareable-example.jsonReference to experimental CodeSystem http://hl7.org/fhir/uv/cql/CodeSystem/example|2.1.0-cibuild--
input/examples/ValueSet-shareable-example.jsonReference to experimental CodeSystem http://hl7.org/fhir/uv/cql/CodeSystem/example|2.1.0-cibuild--
input/examples/ValueSet-shareable-example.jsonReference to experimental CodeSystem http://hl7.org/fhir/uv/cql/CodeSystem/example|2.1.0-cibuild--
input/examples/ValueSet-shareable-example.jsonReference to experimental CodeSystem http://hl7.org/fhir/uv/cql/CodeSystem/example|2.1.0-cibuild--
input/examples/ValueSet-shareable-example.jsonReference to experimental CodeSystem http://hl7.org/fhir/uv/cql/CodeSystem/example|2.1.0-cibuild--
input/examples/ValueSet-shareable-example.jsonReference to experimental CodeSystem http://hl7.org/fhir/uv/cql/CodeSystem/example|2.1.0-cibuild--
input/examples/ValueSet-shareable-example.jsonReference to experimental CodeSystem http://hl7.org/fhir/uv/cql/CodeSystem/example|2.1.0-cibuild--
input/examples/ValueSet-shareable-example.jsonReference to experimental CodeSystem http://hl7.org/fhir/uv/cql/CodeSystem/example|2.1.0-cibuild--
input/examples/ValueSet-shareable-example.jsonReference to experimental CodeSystem http://hl7.org/fhir/uv/cql/CodeSystem/example|2.1.0-cibuild--
input/examples/ValueSet-shareable-example.jsonReference to experimental CodeSystem http://hl7.org/fhir/uv/cql/CodeSystem/example|2.1.0-cibuild--
input/examples/ValueSet-shareable-example.jsonReference to experimental CodeSystem http://hl7.org/fhir/uv/cql/CodeSystem/example|2.1.0-cibuild--
input/examples/ValueSet-shareable-example.jsonReference to experimental CodeSystem http://hl7.org/fhir/uv/cql/CodeSystem/example|2.1.0-cibuild--
input/examples/ValueSet-shareable-example.jsonReference to experimental CodeSystem http://hl7.org/fhir/uv/cql/CodeSystem/example|2.1.0-cibuild--
input/examples/ValueSet-shareable-example.jsonReference to experimental CodeSystem http://hl7.org/fhir/uv/cql/CodeSystem/example|2.1.0-cibuild--
input/examples/ValueSet-shareable-example.jsonReference to experimental CodeSystem http://hl7.org/fhir/uv/cql/CodeSystem/example|2.1.0-cibuild--
input/examples/ValueSet-shareable-example.jsonReference to experimental CodeSystem http://hl7.org/fhir/uv/cql/CodeSystem/example|2.1.0-cibuild--
input/examples/ValueSet-shareable-example.jsonReference to experimental CodeSystem http://hl7.org/fhir/uv/cql/CodeSystem/example|2.1.0-cibuild--
input/examples/ValueSet-shareable-example.jsonReference to experimental CodeSystem http://hl7.org/fhir/uv/cql/CodeSystem/example|2.1.0-cibuild--
input/examples/ValueSet-shareable-example.jsonReference to experimental CodeSystem http://hl7.org/fhir/uv/cql/CodeSystem/example|2.1.0-cibuild--
input/examples/ValueSet-shareable-example.jsonReference to experimental CodeSystem http://hl7.org/fhir/uv/cql/CodeSystem/example|2.1.0-cibuild--
input/examples/ValueSet-shareable-example.jsonReference to experimental CodeSystem http://hl7.org/fhir/uv/cql/CodeSystem/example|2.1.0-cibuild--
input/examples/ValueSet-shareable-example.jsonReference to experimental CodeSystem http://hl7.org/fhir/uv/cql/CodeSystem/example|2.1.0-cibuild--
input/examples/ValueSet-shareable-example.jsonReference to experimental CodeSystem http://hl7.org/fhir/uv/cql/CodeSystem/example|2.1.0-cibuild--
input/examples/ValueSet-shareable-example.jsonReference to experimental CodeSystem http://hl7.org/fhir/uv/cql/CodeSystem/example|2.1.0-cibuild--
input/examples/ValueSet-shareable-example.jsonReference to experimental CodeSystem http://hl7.org/fhir/uv/cql/CodeSystem/example|2.1.0-cibuild--
input/examples/ValueSet-shareable-example.jsonReference to experimental CodeSystem http://hl7.org/fhir/uv/cql/CodeSystem/example|2.1.0-cibuild--
input/examples/ValueSet-shareable-example.jsonReference to experimental CodeSystem http://hl7.org/fhir/uv/cql/CodeSystem/example|2.1.0-cibuild--
input/examples/ValueSet-shareable-example.jsonReference to experimental CodeSystem http://hl7.org/fhir/uv/cql/CodeSystem/example|2.1.0-cibuild--
input/examples/ValueSet-shareable-example.jsonReference to experimental CodeSystem http://hl7.org/fhir/uv/cql/CodeSystem/example|2.1.0-cibuild--
input/examples/ValueSet-shareable-example.jsonReference to experimental CodeSystem http://hl7.org/fhir/uv/cql/CodeSystem/example|2.1.0-cibuild--
input/examples/ValueSet-shareable-example.jsonReference to experimental CodeSystem http://hl7.org/fhir/uv/cql/CodeSystem/example|2.1.0-cibuild--
input/examples/ValueSet-shareable-example.jsonReference to experimental CodeSystem http://hl7.org/fhir/uv/cql/CodeSystem/example|2.1.0-cibuild--
input/examples/ValueSet-shareable-example.jsonReference to experimental CodeSystem http://hl7.org/fhir/uv/cql/CodeSystem/example|2.1.0-cibuild--
input/examples/ValueSet-shareable-example.jsonReference to experimental CodeSystem http://hl7.org/fhir/uv/cql/CodeSystem/example|2.1.0-cibuild--
input/examples/valueset-anc-b5-de49.jsonReference to experimental CodeSystem http://hl7.org/fhir/uv/cql/CodeSystem/example|2.1.0-cibuild--
input/examples/valueset-anc-b5-de50.jsonReference to experimental CodeSystem http://hl7.org/fhir/uv/cql/CodeSystem/example|2.1.0-cibuild--
input/examples/valueset-anc-b5-de50.jsonReference to experimental CodeSystem http://hl7.org/fhir/uv/cql/CodeSystem/example|2.1.0-cibuild--
input/examples/valueset-anc-b5-de50.jsonReference to experimental CodeSystem http://hl7.org/fhir/uv/cql/CodeSystem/example|2.1.0-cibuild--
input/examples/valueset-anc-b5-de50.jsonReference to experimental CodeSystem http://hl7.org/fhir/uv/cql/CodeSystem/example|2.1.0-cibuild--
input/examples/valueset-anc-b5-de50.jsonReference to experimental CodeSystem http://hl7.org/fhir/uv/cql/CodeSystem/example|2.1.0-cibuild--
input/examples/valueset-anc-b5-de50.jsonReference to experimental CodeSystem http://hl7.org/fhir/uv/cql/CodeSystem/example|2.1.0-cibuild--
input/examples/valueset-anc-b5-de50.jsonReference to experimental CodeSystem http://hl7.org/fhir/uv/cql/CodeSystem/example|2.1.0-cibuild--
input/examples/valueset-anc-b5-de50.jsonReference to experimental CodeSystem http://hl7.org/fhir/uv/cql/CodeSystem/example|2.1.0-cibuild--
input/examples/valueset-anc-b5-de50.jsonReference to experimental CodeSystem http://hl7.org/fhir/uv/cql/CodeSystem/example|2.1.0-cibuild--
input/examples/valueset-anc-b5-de50.jsonReference to experimental CodeSystem http://hl7.org/fhir/uv/cql/CodeSystem/example|2.1.0-cibuild--
input/examples/valueset-anc-b5-de50.jsonReference to experimental CodeSystem http://hl7.org/fhir/uv/cql/CodeSystem/example|2.1.0-cibuild--
input/examples/valueset-anc-b5-de50.jsonReference to experimental CodeSystem http://hl7.org/fhir/uv/cql/CodeSystem/example|2.1.0-cibuild--
input/examples/valueset-anc-b5-de51.jsonReference to experimental CodeSystem http://hl7.org/fhir/uv/cql/CodeSystem/example|2.1.0-cibuild--

PARAMETERS_STD_RES_WRONG_TYPE_MIXED

input/examples/Parameters-qicore-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/examples/Parameters-qicore-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/examples/Parameters-qicore-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/examples/Parameters-qicore-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/examples/Parameters-qicore-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/examples/Parameters-qicore-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/examples/Parameters-qicore-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/examples/Parameters-qicore-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/examples/Parameters-qicore-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/examples/Parameters-qicore-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/examples/Parameters-qicore-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/examples/Parameters-qicore-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/examples/Parameters-qicore-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/examples/Parameters-qicore-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/examples/Parameters-qicore-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/examples/Parameters-qicore-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/examples/Parameters-qicore-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/examples/Parameters-qicore-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/examples/Parameters-qicore-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/examples/Parameters-qicore-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/examples/Parameters-qicore-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/examples/Parameters-qicore-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/examples/Parameters-qicore-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/examples/Parameters-qicore-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/examples/Parameters-qicore-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/examples/Parameters-qicore-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/examples/Parameters-qicore-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/examples/Parameters-qicore-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/examples/Parameters-qicore-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/examples/Parameters-qicore-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/examples/Parameters-qicore-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/examples/Parameters-qicore-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/examples/Parameters-qicore-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/examples/Parameters-qicore-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/examples/Parameters-qicore-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/examples/Parameters-qicore-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/examples/Parameters-qicore-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/examples/Parameters-qicore-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/examples/Parameters-qicore-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/examples/Parameters-qicore-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/examples/Parameters-qicore-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/examples/Parameters-qicore-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/examples/Parameters-qicore-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/examples/Parameters-qicore-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/examples/Parameters-qicore-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/examples/Parameters-qicore-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/examples/Parameters-qicore-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/examples/Parameters-qicore-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/examples/Parameters-qicore-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/examples/Parameters-qicore-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/examples/Parameters-qicore-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/examples/Parameters-qicore-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/examples/Parameters-qicore-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/examples/Parameters-qicore-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/examples/Parameters-qicore-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/examples/Parameters-qicore-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/examples/Parameters-qicore-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/examples/Parameters-qicore-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/examples/Parameters-qicore-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/examples/Parameters-qicore-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/examples/Parameters-qicore-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/examples/Parameters-qicore-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/examples/Parameters-qicore-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/examples/Parameters-qicore-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/examples/Parameters-qicore-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/examples/Parameters-uscore-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/examples/Parameters-uscore-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/examples/Parameters-uscore-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/examples/Parameters-uscore-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/examples/Parameters-uscore-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/examples/Parameters-uscore-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/examples/Parameters-uscore-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/examples/Parameters-uscore-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/examples/Parameters-uscore-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/examples/Parameters-uscore-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/examples/Parameters-uscore-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/examples/Parameters-uscore-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/examples/Parameters-uscore-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/examples/Parameters-uscore-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/examples/Parameters-uscore-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/examples/Parameters-uscore-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/examples/Parameters-uscore-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/examples/Parameters-uscore-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/examples/Parameters-uscore-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/examples/Parameters-uscore-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/examples/Parameters-uscore-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/examples/Parameters-uscore-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/examples/Parameters-uscore-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/examples/Parameters-uscore-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/examples/Parameters-uscore-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/examples/Parameters-uscore-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/examples/Parameters-uscore-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/examples/Parameters-uscore-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/examples/Parameters-uscore-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/examples/Parameters-uscore-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/examples/Parameters-uscore-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/examples/Parameters-uscore-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/examples/Parameters-uscore-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/examples/Parameters-uscore-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/examples/Parameters-uscore-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/examples/Parameters-uscore-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/examples/Parameters-uscore-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/examples/Parameters-uscore-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/examples/Parameters-uscore-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/examples/Parameters-uscore-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/examples/Parameters-uscore-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/examples/Parameters-uscore-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/examples/Parameters-uscore-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/examples/Parameters-uscore-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/examples/Parameters-uscore-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/examples/Parameters-uscore-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/examples/Parameters-uscore-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/examples/Parameters-uscore-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/examples/Parameters-uscore-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/examples/Parameters-uscore-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/examples/Parameters-uscore-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/examples/Parameters-uscore-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-fhir-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-fhir-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-fhir-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-fhir-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-fhir-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-fhir-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-fhir-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-fhir-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-fhir-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-fhir-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-fhir-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-fhir-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-fhir-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-fhir-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-fhir-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-fhir-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-fhir-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-fhir-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-fhir-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-fhir-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-fhir-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-fhir-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-fhir-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-fhir-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-fhir-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-fhir-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-fhir-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-fhir-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-fhir-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-fhir-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-fhir-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-fhir-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-fhir-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-fhir-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-fhir-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-fhir-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-fhir-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-fhir-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-fhir-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-fhir-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-fhir-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-fhir-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-fhir-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-fhir-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-fhir-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-fhir-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-fhir-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-fhir-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-fhir-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-fhir-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-fhir-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-fhir-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-fhir-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-fhir-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-fhir-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-fhir-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-fhir-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-fhir-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-fhir-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-fhir-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-fhir-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-fhir-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-fhir-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-fhir-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-fhir-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--

RESOURCE_CANONICAL_MISMATCH

input/extensions/StructureDefinition-cql-selectivity.xmlConformance resource /scratch/repo/input/extensions/StructureDefinition-cql-selectivity.xml - the canonical URL (http://hl7.org/fhir/uv/cql/StructureDefinition/cqf-selectivity) does not match the URL (http://hl7.org/fhir/uv/cql/StructureDefinition/cql-selectivity). Use the special-url parameter if you really mean for it not to match--

RESOURCE_ID_MISMATCH

input/extensions/StructureDefinition-cql-selectivity.xmlResource id/url mismatch: cqf-selectivity/http://hl7.org/fhir/uv/cql/StructureDefinition/cql-selectivity--

SD_ED_TYPE_PROFILE_UNKNOWN

input/profiles/StructureDefinition-cql-groupdefinition.jsonUnable to resolve profile http://hl7.org/fhir/StructureDefinition/cqf-cqlLibrary--
input/profiles/StructureDefinition-cql-groupdefinition.jsonUnable to resolve profile http://hl7.org/fhir/StructureDefinition/cqf-cqlLibrary--

TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS

input/profiles/StructureDefinition-cql-evaluationresult.jsonThere are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/data-absent-reason'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer, or use the [IG Parameter `pin-canonicals`](https://hl7.org/fhir/tools/CodeSystem-ig-parameters.html). Using version '5.3.0', found versions: 4.0.1 (from hl7.fhir.r4.core#4.0.1), 5.3.0 (from hl7.fhir.uv.extensions.r4#current). Suggested fix: change the canonical reference from 'http://hl7.org/fhir/StructureDefinition/data-absent-reason' to 'http://hl7.org/fhir/StructureDefinition/data-absent-reason|5.3.0'StructureDefinition
input/profiles/StructureDefinition-cql-evaluationresult.jsonThere are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/data-absent-reason'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer, or use the [IG Parameter `pin-canonicals`](https://hl7.org/fhir/tools/CodeSystem-ig-parameters.html). Using version '5.3.0', found versions: 4.0.1 (from hl7.fhir.r4.core#4.0.1), 5.3.0 (from hl7.fhir.uv.extensions.r4#current). Suggested fix: change the canonical reference from 'http://hl7.org/fhir/StructureDefinition/data-absent-reason' to 'http://hl7.org/fhir/StructureDefinition/data-absent-reason|5.3.0'StructureDefinition

TYPE_SPECIFIC_CHECKS_DT_CANONICAL_RESOLVE

input/extensions/StructureDefinition-cql-selectivity.xmlA definition could not be found for Canonical URL 'http://hl7.org/fhir/ValueSet/selectivity-coverage'StructureDefinition
input/extensions/StructureDefinition-cql-selectivity.xmlA definition could not be found for Canonical URL 'http://hl7.org/fhir/ValueSet/selectivity-inclusivity'StructureDefinition
input/extensions/StructureDefinition-cql-selectivity.xmlA definition could not be found for Canonical URL 'http://hl7.org/fhir/ValueSet/selectivity-form'StructureDefinition
input/extensions/StructureDefinition-cql-selectivity.xmlA definition could not be found for Canonical URL 'http://hl7.org/fhir/ValueSet/selectivity-coverage'StructureDefinition
input/extensions/StructureDefinition-cql-selectivity.xmlA definition could not be found for Canonical URL 'http://hl7.org/fhir/ValueSet/selectivity-inclusivity'StructureDefinition
input/extensions/StructureDefinition-cql-selectivity.xmlA definition could not be found for Canonical URL 'http://hl7.org/fhir/ValueSet/selectivity-form'StructureDefinition
input/profiles/StructureDefinition-cql-groupdefinition.jsonA definition could not be found for Canonical URL 'http://hl7.org/fhir/StructureDefinition/cqf-cqlLibrary'StructureDefinition
input/profiles/StructureDefinition-cql-groupdefinition.jsonA definition could not be found for Canonical URL 'http://hl7.org/fhir/StructureDefinition/cqf-cqlLibrary'StructureDefinition

Type_Specific_Checks_DT_URL_Resolve

input/examples/Parameters-cql-typemappingexampleresult.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-ethnicity'Observation Body Mass Index Profile
input/examples/Parameters-qicore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-adverseevent'CQL Model Info Settings
input/examples/Parameters-qicore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-allergyintolerance'CQL Model Info Settings
input/examples/Parameters-qicore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-bodystructure'CQL Model Info Settings
input/examples/Parameters-qicore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-careplan'CQL Model Info Settings
input/examples/Parameters-qicore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-careteam'CQL Model Info Settings
input/examples/Parameters-qicore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-claim'CQL Model Info Settings
input/examples/Parameters-qicore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-claimresponse'CQL Model Info Settings
input/examples/Parameters-qicore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-communication'CQL Model Info Settings
input/examples/Parameters-qicore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-communicationnotdone'CQL Model Info Settings
input/examples/Parameters-qicore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-communicationdone'CQL Model Info Settings
input/examples/Parameters-qicore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-communicationrequest'CQL Model Info Settings
input/examples/Parameters-qicore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-condition-encounter-diagnosis'CQL Model Info Settings
input/examples/Parameters-qicore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-condition-problems-health-concerns'CQL Model Info Settings
input/examples/Parameters-qicore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-coverage'CQL Model Info Settings
input/examples/Parameters-qicore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-device'CQL Model Info Settings
input/examples/Parameters-qicore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-deviceprohibited'CQL Model Info Settings
input/examples/Parameters-qicore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-devicerequest'CQL Model Info Settings
input/examples/Parameters-qicore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-devicerequested'CQL Model Info Settings
input/examples/Parameters-qicore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-deviceusestatement'CQL Model Info Settings
input/examples/Parameters-qicore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-diagnosticreport-lab'CQL Model Info Settings
input/examples/Parameters-qicore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-diagnosticreport-note'CQL Model Info Settings
input/examples/Parameters-qicore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-encounter'CQL Model Info Settings
input/examples/Parameters-qicore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-familymemberhistory'CQL Model Info Settings
input/examples/Parameters-qicore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-flag'CQL Model Info Settings
input/examples/Parameters-qicore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-goal'CQL Model Info Settings
input/examples/Parameters-qicore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-imagingstudy'CQL Model Info Settings
input/examples/Parameters-qicore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-immunization'CQL Model Info Settings
input/examples/Parameters-qicore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-immunizationdone'CQL Model Info Settings
input/examples/Parameters-qicore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-immunizationnotdone'CQL Model Info Settings
input/examples/Parameters-qicore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-immunizationevaluation'CQL Model Info Settings
input/examples/Parameters-qicore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-immunizationrecommendation'CQL Model Info Settings
input/examples/Parameters-qicore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-observation-lab'CQL Model Info Settings
input/examples/Parameters-qicore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-location'CQL Model Info Settings
input/examples/Parameters-qicore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-medication'CQL Model Info Settings
input/examples/Parameters-qicore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-medicationprohibited'CQL Model Info Settings
input/examples/Parameters-qicore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-medicationadministration'CQL Model Info Settings
input/examples/Parameters-qicore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-medicationadministrationdone'CQL Model Info Settings
input/examples/Parameters-qicore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-medicationadministrationnotdone'CQL Model Info Settings
input/examples/Parameters-qicore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-medicationdispense'CQL Model Info Settings
input/examples/Parameters-qicore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-medicationdispensedeclined'CQL Model Info Settings
input/examples/Parameters-qicore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-medicationdispensedone'CQL Model Info Settings
input/examples/Parameters-qicore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-medicationrequest'CQL Model Info Settings
input/examples/Parameters-qicore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-medicationrequested'CQL Model Info Settings
input/examples/Parameters-qicore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-medicationstatement'CQL Model Info Settings
input/examples/Parameters-qicore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-nonpatient-observation'CQL Model Info Settings
input/examples/Parameters-qicore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-nutritionorder'CQL Model Info Settings
input/examples/Parameters-qicore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-observation-clinical-result'CQL Model Info Settings
input/examples/Parameters-qicore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-observation-screening-assessment'CQL Model Info Settings
input/examples/Parameters-qicore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-organization'CQL Model Info Settings
input/examples/Parameters-qicore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-patient'CQL Model Info Settings
input/examples/Parameters-qicore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-practitioner'CQL Model Info Settings
input/examples/Parameters-qicore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-practitionerrole'CQL Model Info Settings
input/examples/Parameters-qicore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-procedure'CQL Model Info Settings
input/examples/Parameters-qicore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-proceduredone'CQL Model Info Settings
input/examples/Parameters-qicore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-procedurenotdone'CQL Model Info Settings
input/examples/Parameters-qicore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-questionnaireresponse'CQL Model Info Settings
input/examples/Parameters-qicore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-relatedperson'CQL Model Info Settings
input/examples/Parameters-qicore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-serviceprohibited'CQL Model Info Settings
input/examples/Parameters-qicore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-servicerequest'CQL Model Info Settings
input/examples/Parameters-qicore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-servicerequested'CQL Model Info Settings
input/examples/Parameters-qicore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-simple-observation'CQL Model Info Settings
input/examples/Parameters-qicore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-substance'CQL Model Info Settings
input/examples/Parameters-qicore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-task'CQL Model Info Settings
input/examples/Parameters-qicore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-taskdone'CQL Model Info Settings
input/examples/Parameters-qicore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-taskrejected'CQL Model Info Settings
input/examples/Parameters-uscore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-allergyintolerance'CQL Model Info Settings
input/examples/Parameters-uscore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-average-blood-pressure'CQL Model Info Settings
input/examples/Parameters-uscore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-bmi'CQL Model Info Settings
input/examples/Parameters-uscore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-blood-pressure'CQL Model Info Settings
input/examples/Parameters-uscore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-body-height'CQL Model Info Settings
input/examples/Parameters-uscore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-body-temperature'CQL Model Info Settings
input/examples/Parameters-uscore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-body-weight'CQL Model Info Settings
input/examples/Parameters-uscore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-care-experience-preference'CQL Model Info Settings
input/examples/Parameters-uscore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-careplan'CQL Model Info Settings
input/examples/Parameters-uscore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-careteam'CQL Model Info Settings
input/examples/Parameters-uscore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-condition-encounter-diagnosis'CQL Model Info Settings
input/examples/Parameters-uscore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-condition-problems-health-concerns'CQL Model Info Settings
input/examples/Parameters-uscore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-coverage'CQL Model Info Settings
input/examples/Parameters-uscore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-diagnosticreport-lab'CQL Model Info Settings
input/examples/Parameters-uscore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-diagnosticreport-note'CQL Model Info Settings
input/examples/Parameters-uscore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-documentreference'CQL Model Info Settings
input/examples/Parameters-uscore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-encounter'CQL Model Info Settings
input/examples/Parameters-uscore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-goal'CQL Model Info Settings
input/examples/Parameters-uscore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-head-circumference'CQL Model Info Settings
input/examples/Parameters-uscore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-heart-rate'CQL Model Info Settings
input/examples/Parameters-uscore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-immunization'CQL Model Info Settings
input/examples/Parameters-uscore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-implantable-device'CQL Model Info Settings
input/examples/Parameters-uscore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-lab'CQL Model Info Settings
input/examples/Parameters-uscore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-location'CQL Model Info Settings
input/examples/Parameters-uscore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-medication'CQL Model Info Settings
input/examples/Parameters-uscore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-medicationdispense'CQL Model Info Settings
input/examples/Parameters-uscore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-medicationrequest'CQL Model Info Settings
input/examples/Parameters-uscore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-clinical-result'CQL Model Info Settings
input/examples/Parameters-uscore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-occupation'CQL Model Info Settings
input/examples/Parameters-uscore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-pregnancyintent'CQL Model Info Settings
input/examples/Parameters-uscore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-pregnancystatus'CQL Model Info Settings
input/examples/Parameters-uscore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-screening-assessment'CQL Model Info Settings
input/examples/Parameters-uscore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-sexual-orientation'CQL Model Info Settings
input/examples/Parameters-uscore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-organization'CQL Model Info Settings
input/examples/Parameters-uscore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-patient'CQL Model Info Settings
input/examples/Parameters-uscore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/pediatric-bmi-for-age'CQL Model Info Settings
input/examples/Parameters-uscore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/head-occipital-frontal-circumference-percentile'CQL Model Info Settings
input/examples/Parameters-uscore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/pediatric-weight-for-height'CQL Model Info Settings
input/examples/Parameters-uscore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-practitioner'CQL Model Info Settings
input/examples/Parameters-uscore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-practitionerrole'CQL Model Info Settings
input/examples/Parameters-uscore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-procedure'CQL Model Info Settings
input/examples/Parameters-uscore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-provenance'CQL Model Info Settings
input/examples/Parameters-uscore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-pulse-oximetry'CQL Model Info Settings
input/examples/Parameters-uscore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-questionnaireresponse'CQL Model Info Settings
input/examples/Parameters-uscore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-relatedperson'CQL Model Info Settings
input/examples/Parameters-uscore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-respiratory-rate'CQL Model Info Settings
input/examples/Parameters-uscore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-servicerequest'CQL Model Info Settings
input/examples/Parameters-uscore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-simple-observation'CQL Model Info Settings
input/examples/Parameters-uscore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-smokingstatus'CQL Model Info Settings
input/examples/Parameters-uscore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-specimen'CQL Model Info Settings
input/examples/Parameters-uscore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-treatment-intervention-preference'CQL Model Info Settings
input/examples/Parameters-uscore-modelinfo-settings.jsonNo definition could be found for URL value 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-vital-signs'CQL Model Info Settings

VALIDATION_VAL_STATUS_INCONSISTENT_HINT

input/extensions/StructureDefinition-cql-selectivity.xmlThe resource status 'draft' and the standards status 'trial-use' may not be consistent and should be reviewedStructureDefinition

VALUESET_EXPANSION_NO_IDENTIFIER

input/examples/ValueSet-publishable-example.jsonThis expansion has no identifier. Identifiers are recommended to help with audit and traceability--