== Suppressed Messages == # === CDex needs a contained patient for 3 specific demographic elements US Core variance approved: https://jira.hl7.org/browse/FHIR-46780 === 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 # === 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-46779 === 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 # === 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 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 # === === These examples demonstrate 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) # === === 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 # === === These examples 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 # === 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/task-status|4.0.1 Reference to draft CodeSystem urn:iso-astm:E1762-95:2013|4.0.1 Reference to draft CodeSystem http://hl7.org/fhir/claim-use|4.0.1 Reference to draft CodeSystem http://hl7.org/fhir/uv/sdc/CodeSystem/temp|3.0.0 Reference to draft CodeSystem http://hl7.org/fhir/us/davinci-pas/CodeSystem/PASTempCodes|2.1.0 Reference to draft CodeSystem http://terminology.hl7.org/CodeSystem/condition-category|1.0.0 # === The Da Vinci Team is aware of this plans to move them 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) # === These examples use example.org code system to show fictitious claim to demonstrate the structure and transaction and not the content === A definition for CodeSystem 'http://example.org/fhir/communication-category' could not be found, so the code cannot be validated # ==== FHIR R4 http://hl7.org/fhir/ValueSet/formatcodes is in error which is has been corrected in the FHIR R5. The guide is referencing the "HL7 ValueSet of Format Codes for use with Document Sharing" that is used in R5 === INFORMATION: Bundle/cdex-searchbundle-scenario3-example: Bundle.entry[0].resource/*DocumentReference/cdex-HP-example1*/.content[0].format: The Coding provided (http://terminology.hl7.org/CodeSystem/v3-HL7DocumentFormatCodes#urn:hl7-org:sdwg:ccda-structuredBody:2.1) was not found in the value set 'DocumentReference Format Code Set' (http://hl7.org/fhir/ValueSet/formatcodes|4.0.1), and a code is recommended to come from this value set. (error message = The provided code 'http://terminology.hl7.org/CodeSystem/v3-HL7DocumentFormatCodes#urn:hl7-org:sdwg:ccda-structuredBody:2.1: 'ccda-structuredBody:2.1'' was not found in the value set 'http://hl7.org/fhir/ValueSet/formatcodes|4.0.1') # === X12 Code Systems are referenced in the guide but not freely available due to IP issues === WARNING: ValueSet.where(id = 'cdex-pwk01-attachment-report-type-code'): Error from http://tx.fhir.org/r4: Unable to provide support for code system https://codesystem.x12.org/005010/755 # === This error is inherited from the R4 Subscription Backport IG. This interversion should be fixed in a future release of the Backport IG. See this chat: https://chat.fhir.org/#narrow/channel/179252-IG-creation/topic/validation.20error.20with.20subscription.20backport.20dependency === WARNING: Bundle/cdex-task-inline-scenario1-subscription-notification: Bundle.entry[0].resource/*Parameters/206a4372-a348-41d1-a82e-fc9ebe8825af*/.parameter[3].value.ofType(code): ValueSet 'http://hl7.org/fhir/ValueSet/subscription-notification-type' not found # === The Valueset: https://terminology.hl7.org/5.1.0/ValueSet-usage-context-type.html and code "workflow" are valid and this is a validation issue see chat: https://chat.fhir.org/#narrow/channel/179252-IG-creation/topic/additional.20binding.20usagecontext.20valueset.20error/near/478379307 === The Usage Context http://terminology.hl7.org/ValueSet/usage-context-type#workflow is not recognized so cannot be validated # ==== Since FMG approval for publication, the latest ig-publisher emits a new warning about a deprecation slicing pattern. We will correct it in the next release. See this chat: https://chat.fhir.org/#narrow/channel/179252-IG-creation/topic/deprecated.20pattern.20slicing === # === Da Vinci Project Specific Warning: This Ballot version did not have any Jira trackers associated with it === WARNING: DA VINCI: The Change Log page (changes.html) does not include any Jira tracker items links for the section with title Version = 2.0.0-ballot # === Da Vinci Project Specific Warning: These versions predated change logs in the CDex IG === WARNING: DA VINCI: The Change Log page (changes.html) does not include any Jira tracker items links for the section with title Version = 1.1.0-ballot WARNING: DA VINCI: The Change Log page (changes.html) does not include any Jira tracker items links for the section with title Version = 0.2.0 WARNING: DA VINCI: The Change Log page (changes.html) does not include any Jira tracker items links for the section with title Version = 0.1.0 # === Da Vinci Project Specific Warning: These sections will be added to CDex in the next version === WARNING: DA VINCI: The home page (index.html) must include an h3 section called Content and Organization. WARNING: DA VINCI: The home page (index.html) must include an h3 section called Dependencies. WARNING: DA VINCI: The home page (index.html) must include an h3 section called Intellectual Property Considerations. # === Da Vinci Project Specific Warning: The existing sections will need to be reordered in the next version to meet these requirements === WARNING: DA VINCI: The first menu item under Background should have the label Reading this IG. WARNING: DA VINCI: The second menu item under Background should have the label Use Cases. WARNING: DA VINCI: There must be a menu item under Background called Project and Participants. WARNING: DA VINCI: The third menu item should have the label Specification. WARNING: DA VINCI: There must be a menu item with the label Base Specs. # === Da Vinci Project Specific Warning: This conflicts with the CDex menu navigation style of using submenu for enhanced navigation and cannot be implemented based on it validation rules of a top top level link === WARNING: DA VINCI: The first menu item should have the label IG Home. # === Da Vinci Project Specific Warning: applying this suggested link change causes a build error === WARNING: DA VINCI: The Propose a Change link must start with https://jira.hl7.org/secure/CreateIssueDetails!init.jspa?pid=10405&issuetype=10600&customfield_11302= # === The profile definitions conform to 3 versions of US Core Practitioner via `meta.profile'. This warning means the examples matches all of them, which is the intent. Listing of all US conformant US Core profiles is an alternative to creating a single CDex Profile for Patient and Practitioner (or choosing a single US Core Profile) that conforms to all three US Core versions. We chose this option because it is direct (vs indirection) and thus easier to understand. See related chat: https://chat.fhir.org/#narrow/channel/179252-IG-creation/topic/multiple.20version.20of.20IG.20in.20meta.20profile.20warning === WARNING: Bundle/cdex-electronic-sig-example: Bundle.signature.who: Found multiple matching profiles for urn:uuid:0820c16d-91de-4dfa-a3a6-f140a516a9bc among choices: http://hl7.org/fhir/us/core/StructureDefinition/us-core-practitioner|6.1.0, http://hl7.org/fhir/us/core/StructureDefinition/us-core-practitioner|3.1.1, http://hl7.org/fhir/us/core/StructureDefinition/us-core-practitioner|7.0.0