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

Clarify requirement for StructureDefinition.type to be a url for logical models

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Medium Medium
    • FHIR Core (FHIR)
    • R4
    • FHIR Infrastructure
    • StructureDefinition
    • Hide

      Will change the wording to:

      "For logical models, where the type SHALL be a fully specified URL, the type name SHOULD start with the final path segment of the type URL where required.  E.g. If the type was "http://somewhere.org/foo/bar", the type name should start wit 'bar'."

      Show
      Will change the wording to: "For logical models, where the type SHALL be a fully specified URL, the type name SHOULD start with the final path segment of the type URL where required.  E.g. If the type was "http://somewhere.org/foo/bar", the type name should start wit 'bar'."
    • Alexander Zautke/Grahame Grieve: 16-0-1
    • Clarification
    • Non-substantive
    • R5

    Description

      See https://chat.fhir.org/#narrow/stream/179177-conformance/topic/StructureDefinition.2Etype.20for.20Logical.20Models.2FCustom.20Resources/near/240493555

      In Zulip, the question if the description of StructureDefinition.type implies that there is a SHALL requirement for logical models to have a url as their type was raised multiple times.

      Proposal: Change the sentence "For logical models, where the type is a URL, the type name SHOULD start with the tail of the type URL where required." to "For logical models, where the type SHALL be a URL, the type name SHOULD start with the tail of the type URL where required."

      Attachments

        Activity

          People

            alexanderzautke Alexander Zautke
            alexanderzautke Alexander Zautke
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: