Validation Results for DaVinciCDex

Generated Tue Apr 30 04:19:07 UTC 2024, FHIR version 4.0.1 for hl7.fhir.us.davinci-cdex#2.1.0-preview (canonical = http://hl7.org/fhir/us/davinci-cdex (history)). See Errors Only

Quality Checks

Publisher Version: IG Publisher Version: v1.6.6

Publication Code: davinci-cdex . PackageId = hl7.fhir.us.davinci-cdex, Canonical = http://hl7.org/fhir/us/davinci-cdex

Realm Check for US:

Snomed: The IG specifies the US edition of SNOMED CT ✓

2 Profiles not based on US Core

Publication Request:

package-id

hl7.fhir.us.davinci-cdex

version

2.1.0-preview

path

http://hl7.org/fhir/us/davinci-cdex/STU2.1-preview

Pub-Mode

working release

status

update

Release-Label

CI Build

sequence

STU2

desc

The changes in this STU update to Da Vinci CDEX include updates with US Core 6.1.0 compatible and change requests submitted by the Da Vinci and HL7 community. The HL7 International Payer/Provider Information Exchange (PIE) work group members have agreed to and voted on the resolution of the community comments. For a detailed list of the changes for this version, see the Change Notes: http://hl7.org/fhir/us/core/STU7/changes.html.

descmd

The changes in this STU update to Da Vinci CDEX include updates to be US Core 6.1.0 compatible and change requests submitted by the Da Vinci and HL7 community. The HL7 International Payer/Provider Information Exchange (PIE) work group members have agreed to and voted on the resolution of the community comments. For a detailed list of the changes for this version, see the Change Notes.

changes

changes.html

Proposed path for this publication should usually be the canonical with the version or sequence appended and then some kind of label (typically '-snapshot')

Supressed Messages: 26 Suppressed Issues

Dependency Checks:

Package	Version	FHIR	Canonical	Web Base	Comment
hl7.fhir.us.davinci-cdex	2.1.0-preview	R4	http://hl7.org/fhir/us/davinci-cdex
hl7.terminology.r4	5.5.0 M	R4	http://terminology.hl7.org	http://terminology.hl7.org/5.5.0
hl7.fhir.us.core.3.1.1	3.1.1 U	R4	http://hl7.org/fhir/us/core/3.1.1	http://hl7.org/fhir/us/core/STU3.1.1
hl7.fhir.us.core	3.1.1 O	R4	http://hl7.org/fhir/us/core	http://hl7.org/fhir/us/core/STU3.1.1	Latest Release is 6.1.0
hl7.fhir.us.core	6.1.0 M	R4	http://hl7.org/fhir/us/core	http://hl7.org/fhir/us/core/STU6.1
hl7.terminology.r4	5.0.0 O	R4	http://terminology.hl7.org	http://terminology.hl7.org/5.0.0	Latest Release is 5.5.0
hl7.fhir.uv.extensions.r4	1.0.0 O	R4	http://hl7.org/fhir/extensions	http://hl7.org/fhir/extensions/1.0.0	Latest Release is 5.1.0
hl7.fhir.uv.bulkdata	2.0.0 M	R4	http://hl7.org/fhir/uv/bulkdata	http://hl7.org/fhir/uv/bulkdata/STU2
hl7.fhir.uv.smart-app-launch	2.1.0 M	R4	http://hl7.org/fhir/smart-app-launch	http://hl7.org/fhir/smart-app-launch/STU2.1
hl7.terminology.r4	5.0.0 O	R4	http://terminology.hl7.org	http://terminology.hl7.org/5.0.0	see above. Latest Release is 5.5.0
us.nlm.vsac	0.11.0 O	R4	http://fhir.org/packages/us.nlm.vsac	http://fhir.org/packages/us.nlm.vsac	Latest Release is 0.18.0
hl7.fhir.uv.sdc	3.0.0 M	R4	http://hl7.org/fhir/uv/sdc	http://hl7.org/fhir/uv/sdc/STU3
hl7.fhir.r4.examples	4.0.1 O	R4	http://hl7.org/fhir	http://hl7.org/fhir/R4	Latest Release is 5.0.0
us.cdc.phinvads	0.12.0 M	R4	http://fhir.org/packages/us.cdc.phinvads	http://fhir.org/packages/us.cdc.phinvads
ihe.formatcode.fhir	1.1.0 O	R4	https://profiles.ihe.net/fhir/ihe.formatcode.fhir	https://profiles.ihe.net/fhir/ihe.formatcode.fhir/1.1.0	Latest Release is 1.2.0
hl7.fhir.us.davinci-hrex	1.0.0 M	R4	http://hl7.org/fhir/us/davinci-hrex	http://hl7.org/fhir/us/davinci-hrex/STU1
hl7.fhir.us.core	3.1.1 O	R4	http://hl7.org/fhir/us/core	http://hl7.org/fhir/us/core/STU3.1.1	see above. Latest Release is 6.1.0
hl7.fhir.us.udap-security	0.1.0 O	R4	http://hl7.org/fhir/us/udap-security	http://hl7.org/fhir/us/udap-security/2021Sep	Latest Release is 1.0.0
hl7.fhir.us.core	3.1.1 O	R4	http://hl7.org/fhir/us/core	http://hl7.org/fhir/us/core/STU3.1.1	see above. Latest Release is 6.1.0
hl7.fhir.us.davinci-pas	2.0.1 M	R4	http://hl7.org/fhir/us/davinci-pas	http://hl7.org/fhir/us/davinci-pas/STU2
hl7.terminology.r4	5.3.0 O	R4	http://terminology.hl7.org	http://terminology.hl7.org/5.3.0	Latest Release is 5.5.0
hl7.fhir.uv.extensions.r4	1.0.0 O	R4	http://hl7.org/fhir/extensions	http://hl7.org/fhir/extensions/1.0.0	see above. Latest Release is 5.1.0
hl7.fhir.us.core	3.1.1 O	R4	http://hl7.org/fhir/us/core	http://hl7.org/fhir/us/core/STU3.1.1	see above. Latest Release is 6.1.0
hl7.fhir.us.davinci-crd	2.0.0 V	R4	http://hl7.org/fhir/us/davinci-crd	http://hl7.org/fhir/us/davinci-crd/STU2
hl7.terminology.r4	5.3.0 O	R4	http://terminology.hl7.org	http://terminology.hl7.org/5.3.0	see above. Latest Release is 5.5.0
hl7.fhir.uv.extensions.r4	1.0.0 O	R4	http://hl7.org/fhir/extensions	http://hl7.org/fhir/extensions/1.0.0	see above. Latest Release is 5.1.0
hl7.fhir.us.core	3.1.1 O	R4	http://hl7.org/fhir/us/core	http://hl7.org/fhir/us/core/STU3.1.1	see above. Latest Release is 6.1.0
hl7.fhir.uv.sdc	3.0.0 M	R4	http://hl7.org/fhir/uv/sdc	http://hl7.org/fhir/uv/sdc/STU3	see above
hl7.fhir.us.davinci-hrex	1.0.0 M	R4	http://hl7.org/fhir/us/davinci-hrex	http://hl7.org/fhir/us/davinci-hrex/STU1	see above
us.nlm.vsac	0.11.0 O	R4	http://fhir.org/packages/us.nlm.vsac	http://fhir.org/packages/us.nlm.vsac	see above. Latest Release is 0.18.0
hl7.fhir.uv.subscriptions-backport.r4	1.1.0 M	R4	http://hl7.org/fhir/uv/subscriptions-backport	http://hl7.org/fhir/uv/subscriptions-backport/STU1.1
hl7.terminology.r4	5.0.0 O	R4	http://terminology.hl7.org	http://terminology.hl7.org/5.0.0	see above. Latest Release is 5.5.0
hl7.fhir.us.carin-bb	2.0.0 M	R4	http://hl7.org/fhir/us/carin-bb	http://hl7.org/fhir/us/carin-bb/STU2
hl7.terminology.r4	5.0.0 O	R4	http://terminology.hl7.org	http://terminology.hl7.org/5.0.0	see above. Latest Release is 5.5.0
hl7.fhir.us.core	3.1.1 O	R4	http://hl7.org/fhir/us/core	http://hl7.org/fhir/us/core/STU3.1.1	see above. Latest Release is 6.1.0
us.nlm.vsac	0.7.0 O	R4	http://fhir.org/packages/us.nlm.vsac	http://fhir.org/packages/us.nlm.vsac	Latest Release is 0.18.0
hl7.fhir.us.davinci-dtr	2.0.1 M	R4	http://hl7.org/fhir/us/davinci-dtr	http://hl7.org/fhir/us/davinci-dtr/STU2
hl7.terminology.r4	5.3.0 O	R4	http://terminology.hl7.org	http://terminology.hl7.org/5.3.0	see above. Latest Release is 5.5.0
hl7.fhir.uv.extensions.r4	1.0.0 O	R4	http://hl7.org/fhir/extensions	http://hl7.org/fhir/extensions/1.0.0	see above. Latest Release is 5.1.0
hl7.fhir.us.core	3.1.1 O	R4	http://hl7.org/fhir/us/core	http://hl7.org/fhir/us/core/STU3.1.1	see above. Latest Release is 6.1.0
hl7.fhir.uv.sdc	3.0.0 M	R4	http://hl7.org/fhir/uv/sdc	http://hl7.org/fhir/uv/sdc/STU3	see above
hl7.fhir.us.davinci-hrex	1.0.0 M	R4	http://hl7.org/fhir/us/davinci-hrex	http://hl7.org/fhir/us/davinci-hrex/STU1	see above
hl7.fhir.us.davinci-crd	current V	R4	http://hl7.org/fhir/us/davinci-crd	https://build.fhir.org/ig/HL7/davinci-crd/	Cannot be published with a dependency on a current build version
hl7.terminology.r4	5.3.0 O	R4	http://terminology.hl7.org	http://terminology.hl7.org/5.3.0	see above. Latest Release is 5.5.0
hl7.fhir.uv.extensions.r4	1.0.0 O	R4	http://hl7.org/fhir/extensions	http://hl7.org/fhir/extensions/1.0.0	see above. Latest Release is 5.1.0
hl7.fhir.us.core.3.1.1	3.1.1 U	R4	http://hl7.org/fhir/us/core/3.1.1	http://hl7.org/fhir/us/core/STU3.1.1	see above
hl7.fhir.us.core	6.1.0 M	R4	http://hl7.org/fhir/us/core	http://hl7.org/fhir/us/core/STU6.1	see above
hl7.fhir.uv.sdc	3.0.0 M	R4	http://hl7.org/fhir/uv/sdc	http://hl7.org/fhir/uv/sdc/STU3	see above
hl7.fhir.us.davinci-hrex	current V	R4	http://hl7.org/fhir/us/davinci-hrex	https://build.fhir.org/ig/HL7/davinci-ehrx/	Cannot be published with a dependency on a current build version
hl7.terminology.r4	5.3.0 O	R4	http://terminology.hl7.org	http://terminology.hl7.org/5.3.0	see above. Latest Release is 5.5.0
hl7.fhir.us.core.3.1.1	3.1.1 U	R4	http://hl7.org/fhir/us/core/3.1.1	http://hl7.org/fhir/us/core/STU3.1.1	see above
hl7.fhir.us.core	6.1.0 M	R4	http://hl7.org/fhir/us/core	http://hl7.org/fhir/us/core/STU6.1	see above
hl7.fhir.uv.extensions	5.1.0 M	R5	http://hl7.org/fhir/extensions	http://hl7.org/fhir/extensions/5.1.0	FHIR Version Mismatch
hl7.terminology.r5	5.5.0 M	R5	http://terminology.hl7.org	http://terminology.hl7.org/5.5.0	FHIR Version Mismatch
us.nlm.vsac	0.12.0 O	R4	http://fhir.org/packages/us.nlm.vsac	http://fhir.org/packages/us.nlm.vsac	Latest Release is 0.18.0
us.nlm.vsac	0.11.0 O	R4	http://fhir.org/packages/us.nlm.vsac	http://fhir.org/packages/us.nlm.vsac	see above. Latest Release is 0.18.0
hl7.fhir.uv.sdc	3.0.0 M	R4	http://hl7.org/fhir/uv/sdc	http://hl7.org/fhir/uv/sdc/STU3	see above
hl7.fhir.uv.extensions	5.1.0-cibuild V	R5	http://hl7.org/fhir/extensions	http://hl7.org/fhir/extensions/5.1.0-snapshot1	FHIR Version Mismatch
hl7.terminology.r5	5.3.0 O	R5	http://terminology.hl7.org	http://terminology.hl7.org/5.3.0	FHIR Version Mismatch. Latest Release is 5.5.0

Templates: hl7.davinci.template#current -> hl7.fhir.template#current -> hl7.base.template#current -> fhir.base.template#current. Tools: 0.1.0

Dependent IGs: 1 guide

Global Profiles: (none declared)

Terminology Server(s): http://tx.fhir.org/r4 (details)

HTA Analysis: no Non-HL7 references found

R5 Dependencies: (none)

Draft Dependencies:

hl7.fhir.r4.core#4.0.1: GuideParameterCode (17 uses), CompositionAttestationMode (3 uses), SignatureTypeCodes (9 uses), Use (9 uses), Find patient matches using MPI based logic (1 uses), CommonLanguages (8 uses), Organization (9 uses), Practitioner (5 uses), PractitionerRole (7 uses), RelatedPerson (5 uses), PractitionerRole (1 uses), Location (3 uses), HealthcareService (1 uses), Endpoint (1 uses), CarePlan (1 uses), ServiceRequest (1 uses), Procedure (1 uses), regex (3 uses), QuestionnaireResponseStatus (1 uses), Encounter (3 uses), Device (2 uses), QuestionnaireResponse (3 uses), Ordinal Value (1 uses), QuestionnaireAnswerCodes (1 uses), Signature (1 uses), SignatureTypeCodes (2 uses), Task (6 uses), ActivityDefinition (2 uses), TaskIntent (2 uses), RequestPriority (2 uses), ProcedurePerformerRoleCodes (2 uses), Coverage (2 uses), ClaimResponse (2 uses), Provenance (2 uses), Group (2 uses), CommonTags (1 uses), Claim (2 uses)
hl7.fhir.uv.extensions#5.1.0-cibuild: SDStatusDerivation (32 uses), TypeMustSupport (15 uses)
hl7.fhir.uv.sdc#3.0.0: StructuredDataCapture (1 uses), SDCQuestionnaireResponseAdapt (6 uses), SDCQuestionnaireAdapt (1 uses), QuestionnaireAdaptiveExtension (1 uses), TemporaryCodes (23 uses), SDCQuestionnaireResponse (6 uses), SDCBaseQuestionnaire (1 uses), ItemMedia (1 uses), ItemAnswerMedia (1 uses)
hl7.fhir.uv.tools#0.1.0: ResourceSortExt (65 uses)
hl7.terminology.r5#5.5.0: ConditionCategoryCodes (5 uses), ProvenanceParticipantType (4 uses), ObservationCategoryCodes (3 uses), ConditionVerificationStatus (1 uses)

Modifier Extensions: (none)

Previous Version Comparison: Comparison with version 1.0.0
Comparison with version 1.1.0
Comparison with version 2.0.0

IPA Comparison: n/a

IPS Comparison: n/a

Summary: errors = 2, warn = 2, info = 3, broken links = 0

Filename	Errors	Warnings	Hints
Build Errors	0	1	0
/scratch/repo/fsh-generated/resources/ImplementationGuide-hl7.fhir.us.davinci-cdex	2	0	0
/scratch/repo/input/examples/cdex-document-digital-sig-example	0	0	0
/scratch/repo/input/examples/cdex-electronic-sig-example	0	0	0
/scratch/repo/input/examples/cdex-parameters-example1	0	0	0
/scratch/repo/input/examples/cdex-parameters-example2	0	0	0
/scratch/repo/input/examples/cdex-parameters-example3	0	0	0
/scratch/repo/input/examples/cdex-parameters-example4	0	0	0
/scratch/repo/input/examples/cdex-parameters-example5	0	0	0
/scratch/repo/input/examples/cdex-questionnaire-example1	0	0	0
/scratch/repo/input/examples/cdex-questionnaire-example2	0	0	0
/scratch/repo/input/examples/cdex-questionnaireresponse-example1	0	0	0
/scratch/repo/input/examples/cdex-questionnaireresponse-example2	0	0	0
/scratch/repo/input/examples/cdex-questionnaireresponse-example3	0	0	0
/scratch/repo/input/examples/cdex-questionnaireresponse-example4	0	0	0
/scratch/repo/input/examples/cdex-searchset-digital-sig-example	0	0	0
/scratch/repo/input/examples/cdex-task-example1	0	0	0
/scratch/repo/input/examples/cdex-task-example10	0	0	0
/scratch/repo/input/examples/cdex-task-example11	0	0	0
/scratch/repo/input/examples/cdex-task-example12	0	0	0
/scratch/repo/input/examples/cdex-task-example13	0	0	0
/scratch/repo/input/examples/cdex-task-example14	0	0	0
/scratch/repo/input/examples/cdex-task-example15	0	0	0
/scratch/repo/input/examples/cdex-task-example16	0	0	0
/scratch/repo/input/examples/cdex-task-example17	0	0	0
/scratch/repo/input/examples/cdex-task-example18	0	0	0
/scratch/repo/input/examples/cdex-task-example19	0	0	0
/scratch/repo/input/examples/cdex-task-example2	0	0	0
/scratch/repo/input/examples/cdex-task-example20	0	0	0
/scratch/repo/input/examples/cdex-task-example21	0	0	0
/scratch/repo/input/examples/cdex-task-example22	0	0	0
/scratch/repo/input/examples/cdex-task-example23	0	0	0
/scratch/repo/input/examples/cdex-task-example24	0	0	0
/scratch/repo/input/examples/cdex-task-example25	0	0	0
/scratch/repo/input/examples/cdex-task-example26	0	0	0
/scratch/repo/input/examples/cdex-task-example27	0	0	0
/scratch/repo/input/examples/cdex-task-example28	0	0	0
/scratch/repo/input/examples/cdex-task-example29	0	0	0
/scratch/repo/input/examples/cdex-task-example3	0	0	0
/scratch/repo/input/examples/cdex-task-example30	0	0	0
/scratch/repo/input/examples/cdex-task-example31	0	0	0
/scratch/repo/input/examples/cdex-task-example4	0	0	0
/scratch/repo/input/examples/cdex-task-example5	0	0	0
/scratch/repo/input/examples/cdex-task-example6	0	0	0
/scratch/repo/input/examples/cdex-task-example7	0	0	0
/scratch/repo/input/examples/cdex-task-example8	0	0	0
/scratch/repo/input/examples/cdex-task-example9	0	0	0
/scratch/repo/input/resources/OperationDefinition-submit-attachment	0	0	0
/scratch/repo/input/resources/capabilitystatement-data-consumer-client	0	0	0
/scratch/repo/input/resources/capabilitystatement-data-consumer-server	0	0	0
/scratch/repo/input/resources/capabilitystatement-data-source-client	0	0	0
/scratch/repo/input/resources/capabilitystatement-data-source-server	0	0	0
/scratch/repo/input/resources/codesystem-cdex-temp	0	0	0
/scratch/repo/input/resources/structuredefinition-cdex-parameters-submit-attachment	0	0	0
/scratch/repo/input/resources/structuredefinition-cdex-patient-demographics	0	0	1
/scratch/repo/input/resources/structuredefinition-cdex-practitionerrole	0	0	0
/scratch/repo/input/resources/structuredefinition-cdex-sdc-questionnaireresponse	0	0	0
/scratch/repo/input/resources/structuredefinition-cdex-signature	0	0	0
/scratch/repo/input/resources/structuredefinition-cdex-signature-bundle	0	0	0
/scratch/repo/input/resources/structuredefinition-cdex-task-attachment-request	0	0	1
/scratch/repo/input/resources/structuredefinition-cdex-task-data-request	0	0	0
/scratch/repo/input/resources/valueset-cdex-POU	0	1	0
/scratch/repo/input/resources/valueset-cdex-attachment-task-code	0	0	0
/scratch/repo/input/resources/valueset-cdex-claim-use	0	0	1
/scratch/repo/input/resources/valueset-cdex-data-request-task-code	0	0	0
/scratch/repo/input/resources/valueset-cdex-identifier-types	0	0	0
/scratch/repo/input/resources/valueset-cdex-work-queue	0	0	0

n/a Show Validation Information

warning

The 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)

fsh-generated/resources/ImplementationGuide-hl7.fhir.us.davinci-cdex.json Show Validation Information (1)

Path

Severity

Message

ImplementationGuide.definition.extension[24].extension[0].value.ofType(string) (l1/c7252)

error

The value provided ('auto-oid-root') was not found in the value set 'ig-parameters Codes ValueSet' (http://hl7.org/fhir/tools/ValueSet/ig-parameters|0.1.0), and a code is required from this value set (error message = The System URI could not be determined for the code 'auto-oid-root' in the ValueSet 'http://hl7.org/fhir/tools/ValueSet/ig-parameters|0.1.0'; The provided code '#auto-oid-root' was not found in the value set 'http://hl7.org/fhir/tools/ValueSet/ig-parameters|0.1.0')

ImplementationGuide.definition.extension[61].extension[0].value.ofType(code) (l1/c13546)

error

input/examples/cdex-document-digital-sig-example.json Show Validation Information (19)

✓

input/examples/cdex-electronic-sig-example.json Show Validation Information (20)

✓

input/examples/cdex-parameters-example1.json Show Validation Information (5)

✓

input/examples/cdex-parameters-example2.json Show Validation Information (21)

✓

input/examples/cdex-parameters-example3.json Show Validation Information (5)

✓

input/examples/cdex-parameters-example4.json Show Validation Information (11)

✓

input/examples/cdex-parameters-example5.json Show Validation Information (3)

✓

input/examples/cdex-questionnaire-example1.json Show Validation Information (1)

✓

input/examples/cdex-questionnaire-example2.json Show Validation Information (1)

✓

input/examples/cdex-questionnaireresponse-example1.json Show Validation Information (2)

✓

input/examples/cdex-questionnaireresponse-example2.json Show Validation Information (3)

✓

input/examples/cdex-questionnaireresponse-example3.json Show Validation Information (2)

✓

input/examples/cdex-questionnaireresponse-example4.json Show Validation Information (2)

✓

input/examples/cdex-searchset-digital-sig-example.json Show Validation Information (5)

✓

input/examples/cdex-task-example1.json Show Validation Information (2)

✓

input/examples/cdex-task-example10.json Show Validation Information (2)

✓

input/examples/cdex-task-example11.json Show Validation Information (2)

✓

input/examples/cdex-task-example12.json Show Validation Information (2)

✓

input/examples/cdex-task-example13.json Show Validation Information (2)

✓

input/examples/cdex-task-example14.json Show Validation Information (2)

✓

input/examples/cdex-task-example15.json Show Validation Information (2)

✓

input/examples/cdex-task-example16.json Show Validation Information (2)

✓

input/examples/cdex-task-example17.json Show Validation Information (2)

✓

input/examples/cdex-task-example18.json Show Validation Information (2)

✓

input/examples/cdex-task-example19.json Show Validation Information (8)

✓

input/examples/cdex-task-example2.json Show Validation Information (2)

✓

input/examples/cdex-task-example20.json Show Validation Information (8)

✓

input/examples/cdex-task-example21.json Show Validation Information (2)

✓

input/examples/cdex-task-example22.json Show Validation Information (8)

✓

input/examples/cdex-task-example23.json Show Validation Information (8)

✓

input/examples/cdex-task-example24.json Show Validation Information (8)

✓

input/examples/cdex-task-example25.json Show Validation Information (8)

✓

input/examples/cdex-task-example26.json Show Validation Information (2)

✓

input/examples/cdex-task-example27.json Show Validation Information (2)

✓

input/examples/cdex-task-example28.json Show Validation Information (8)

✓

input/examples/cdex-task-example29.json Show Validation Information (8)

✓

input/examples/cdex-task-example3.json Show Validation Information (6)

✓

input/examples/cdex-task-example30.json Show Validation Information (2)

✓

input/examples/cdex-task-example31.json Show Validation Information (2)

✓

input/examples/cdex-task-example4.json Show Validation Information (2)

✓

input/examples/cdex-task-example5.json Show Validation Information (2)

✓

input/examples/cdex-task-example6.json Show Validation Information (2)

✓

input/examples/cdex-task-example7.json Show Validation Information (9)

✓

input/examples/cdex-task-example8.json Show Validation Information (6)

✓

input/examples/cdex-task-example9.json Show Validation Information (2)

✓

input/resources/OperationDefinition-submit-attachment.json Show Validation Information (1)

✓

input/resources/capabilitystatement-data-consumer-client.json Show Validation Information (1)

✓

input/resources/capabilitystatement-data-consumer-server.json Show Validation Information (1)

✓

input/resources/capabilitystatement-data-source-client.json Show Validation Information (1)

✓

input/resources/capabilitystatement-data-source-server.json Show Validation Information (1)

✓

input/resources/codesystem-cdex-temp.json Show Validation Information (1)

✓

input/resources/structuredefinition-cdex-parameters-submit-attachment.json Show Validation Information (1)

✓

input/resources/structuredefinition-cdex-patient-demographics.json Show Validation Information (1)

Path

Severity

Message

StructureDefinition (l1/c113887)

information

The resource status 'draft' and the standards status 'trial-use' may not be consistent and should be reviewed

input/resources/structuredefinition-cdex-practitionerrole.json Show Validation Information (1)

✓

input/resources/structuredefinition-cdex-sdc-questionnaireresponse.json Show Validation Information (1)

✓

input/resources/structuredefinition-cdex-signature.json Show Validation Information (1)

✓

input/resources/structuredefinition-cdex-signature-bundle.json Show Validation Information (1)

✓

input/resources/structuredefinition-cdex-task-attachment-request.json Show Validation Information (1)

Path

Severity

Message

StructureDefinition (l1/c467814)

information

The resource status 'draft' and the standards status 'trial-use' may not be consistent and should be reviewed

input/resources/structuredefinition-cdex-task-data-request.json Show Validation Information (1)

✓

input/resources/valueset-cdex-POU.json Show Validation Information (1)

Path

Severity

Message

ValueSet (l1/c10046)

warning

The resource status 'active' and the standards status 'draft' are not consistent

input/resources/valueset-cdex-attachment-task-code.json Show Validation Information (1)

✓

input/resources/valueset-cdex-claim-use.json Show Validation Information (1)

Path

Severity

Message

ValueSet (l1/c2738)

information

The resource status 'draft' and the standards status 'trial-use' may not be consistent and should be reviewed

input/resources/valueset-cdex-data-request-task-code.json Show Validation Information (1)

✓

input/resources/valueset-cdex-identifier-types.json Show Validation Information (1)

✓

input/resources/valueset-cdex-work-queue.json Show Validation Information (1)

✓

Suppressed Messages (Warnings, hints, broken links)

=== Thes example demonstrates DocumentReference Payloads for an operation. The actual content is inline base64 encoded data. Since the narrative would be the human-readable metadata about the document which is easily parsed, we think it add little value for the cost of adding it. ===

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

=== These examples use example.org code system to show fictitious condition to demonstrate the structure and transaction and not the content ===

A definition for CodeSystem 'http://example.org/terminology' could not be found, so the code cannot be validated (2 uses)

=== These examples use example.org code system to show how translations ( i.e. local codes) could be used in addition to standard code systems. ===

A definition for CodeSystem 'http://example.org/lab-results' could not be found, so the code cannot be validated (6 uses)

=== This example uses example.org to reference a base questionnaire URI from which it is derived to code system to demonstrate the structure not the content ===

The questionnaire 'http://example.org/base_adaptive_questionnaire' referred to in the derivation could not be found (1 uses)

=== these CodeSystems and ValueSets are in FHIR Core/THO and not under the direct control of Da Vinci editors ===

Reference to draft CodeSystem http://hl7.org/fhir/claim-use|4.0.1 (8 uses)
Reference to draft CodeSystem http://hl7.org/fhir/narrative-status|4.0.1 (0 uses)
Reference to draft CodeSystem http://hl7.org/fhir/task-status|4.0.1 (31 uses)
Reference to draft CodeSystem http://hl7.org/fhir/uv/sdc/CodeSystem/temp|3.0.0 (23 uses)
Reference to draft CodeSystem http://terminology.hl7.org/CodeSystem/condition-category|1.0.0 (5 uses)
Reference to draft CodeSystem http://terminology.hl7.org/CodeSystem/condition-category|1.0.0 (0 uses)
Reference to draft CodeSystem http://terminology.hl7.org/CodeSystem/coverage-class|1.0.0 (0 uses)
Reference to draft CodeSystem http://terminology.hl7.org/CodeSystem/observation-category|1.0.0 (0 uses)
Reference to draft CodeSystem http://terminology.hl7.org/CodeSystem/organization-type|2.0.0 (0 uses)
Reference to draft CodeSystem http://terminology.hl7.org/CodeSystem/provenance-participant-type|1.0.0 (0 uses)
Reference to draft CodeSystem urn:iso-astm:E1762-95:2013|4.0.1 (3 uses)
Reference to draft CodeSystem urn:iso:std:iso:11073:10101|2023-04-26 (0 uses)

=== this CodeSystems is intended to be temporary and based on user experience and testing will migrate these codes to HTO or another standard code system ===

Reference to draft CodeSystem http://hl7.org/fhir/us/davinci-cdex/CodeSystem/cdex-temp|2.1.0-preview (97 uses)

==== The Da Vinci Team is aware of this and will budget accordingly in a future publication cycle ===

Most code systems defined in HL7 IGs will need to move to THO later during the process. Consider giving this code system a THO URL now (See https://confluence.hl7.org/display/TSMG/Terminology+Play+Book, and/or talk to TSMG) (1 uses)

CDex needs a contained PractitionerRole to communicate the identifiers for both the provider practitioner and organization using Task.owner which is limited to max=1 reference. A Jira ticket has been lodged for Task to allow for >1 task.for element to address this issue. This is the appropriate use of contained because the content referred to in the contained resource does not have an independent existence apart from the resource that contains it. Furthermore, US Core does not require but recommends that contained resource conform to US Core. US Core variance approved: https://jira.hl7.org/browse/FHIR-39618

WARNING: StructureDefinition.where(url = 'http://hl7.org/fhir/us/davinci-cdex/StructureDefinition/cdex-practitionerrole').baseDefinition: US FHIR Usage rules require that all profiles on PractitionerRole derive from the core US profile. See https://confluence.hl7.org/display/CGP/US+Core+Variance+Request+Process (1 uses)

CDex needs a contained patient for 3 specific demographic elements- US Core variance approved: http://jira.hl7.org/browse/FHIR-37738

== input/resources/structuredefinition-cdex-practitionerrole.json == (0 uses)
WARNING: StructureDefinition.where(url = 'http://hl7.org/fhir/us/davinci-cdex/StructureDefinition/cdex-patient-demographics').baseDefinition: US FHIR Usage rules require that all profiles on Patient derive from the core US profile. See https://confluence.hl7.org/display/CGP/US+Core+Variance+Request+Process (1 uses)

The referenced ValueSet is not published as a package file (to the best of my knowledge). It is available from LOINC's FHIR terminology server (service base https://fhir.loinc.org). Supporting value sets provided on a tx server, and not distributed in a package is on the publisher todo list. See this Chat: https://chat.fhir.org/#narrow/stream/179252-IG-creation/topic/LOINC.20valuesets.20out.20of.20the.20box.3F

ValueSet 'http://loinc.org/vs/valid-hl7-attachment-requests' not found (6 uses)

The use CPT codes can used as additional codings which, because of IP issues, are not validated by the terminology server

Code System URI 'http://www.ama-assn.org/go/cpt' is unknown so the code cannot be validated (0 uses)

the example demonstrate the legitimate use case for using free text instead of codes for requesting information using a Task-based Query

No code provided, and a code should be provided from the value set 'US Core DocumentReference Type' (http://hl7.org/fhir/us/core/ValueSet/us-core-documentreference-type|6.1.0) (4 uses)

these Profiles are used in the attachment requests examples Cdex Task Example 19, CDex Task Example 20 as a contained resources.

INFORMATION: StructureDefinition.where(url = 'http://hl7.org/fhir/us/davinci-cdex/StructureDefinition/cdex-patient-demographics'): The Implementation Guide contains no explicitly linked examples for this profile (1 uses)
INFORMATION: StructureDefinition.where(url = 'http://hl7.org/fhir/us/davinci-cdex/StructureDefinition/cdex-practitionerrole'): The Implementation Guide contains no explicitly linked examples for this profile (1 uses)

Errors sorted by type

Terminology_TX_NoValid_16

fsh-generated/resources/ImplementationGuide-hl7.fhir.us.davinci-cdex.json

VALIDATION_VAL_STATUS_INCONSISTENT

input/resources/valueset-cdex-POU.json

The resource status 'active' and the standards status 'draft' are not consistent

VALIDATION_VAL_STATUS_INCONSISTENT_HINT

input/resources/structuredefinition-cdex-patient-demographics.json

The resource status 'draft' and the standards status 'trial-use' may not be consistent and should be reviewed

input/resources/structuredefinition-cdex-task-attachment-request.json

The resource status 'draft' and the standards status 'trial-use' may not be consistent and should be reviewed

input/resources/valueset-cdex-claim-use.json

The resource status 'draft' and the standards status 'trial-use' may not be consistent and should be reviewed