Uploaded image for project: 'FHIR Specification Feedback'
  1. FHIR Specification Feedback
  2. FHIR-42579

Explain consistency of artifacts

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive
    • Icon: Highest Highest
    • Canonical Resource Management Infrastructure (FHIR)
    • 1.0.0-ballot [deprecated]
    • Clinical Decision Support
    • Naming Conventions
    • 11.1
    • Hide

      What it means is that all references to canonicals from artifacts in the package to other artifacts in the package are version-consistent, i.e. if the references are version-specific and the referenced artifact is included in the package, the referenced artifact is the version referenced (and no other unreferenced versions of that artifact are included)

      Show
      What it means is that all references to canonicals from artifacts in the package to other artifacts in the package are version-consistent, i.e. if the references are version-specific and the referenced artifact is included in the package, the referenced artifact is the version referenced (and no other unreferenced versions of that artifact are included)
    • Floyd Eisenberg/Greg White: 13-0-0
    • Clarification
    • Non-substantive

    Description

      "The versions of all artifacts are consistend across the package." - what does this mean? All artifacts in a package are expected to have the same version? This isn't true for THO, for example. Not clear if this is guidance, a rule or what. Please clarify.

      (Comment 39 - imported by: Lloyd McKenzie)

      Attachments

        Activity

          People

            Unassigned Unassigned
            lloyd Lloyd McKenzie
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: