2015May core #779 - Clarify Data Element Boundaries and Relationships

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive
    • Priority: Medium
    • FHIR Core (FHIR)
    • DSTU1 [deprecated]
    • FHIR Infrastructure
    • DataElement (see StructureDefinition) [deprecated]
    • 6.20.2
    • Hide

      Revise language to say "When defining elements inside a StructureDefinition, authors may take their definitions and other constraints from existing DataElement instances and include an extension that identifies that a particular StructureDefinition.*.element corresponds to a referenced DataElement.

      Show
      Revise language to say "When defining elements inside a StructureDefinition, authors may take their definitions and other constraints from existing DataElement instances and include an extension that identifies that a particular StructureDefinition.*.element corresponds to a referenced DataElement.
    • Grahame Grieve / Ewout Kramer : 7-0-1
    • Clarification
    • Non-substantive
    • DSTU1 [deprecated]

      Existing Wording: Authors of Profiles may leverage (and reference) DataElements when defining the data elements with the Profile. (For implementability reasons, the data constraints should still be explicitly exposed within the Profile rather than being included "by reference" to the DataElement.)

      Comment:

      This is difficult to understand. What does "leverage" mean? What does "when defining the data elements with the Profile" mean? Is "defining the data elements with the Profile" talking about creating new extensions to be used in a Profile? Perhaps an example or two is in order.

            Assignee:
            Unassigned
            Reporter:
            toniki
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: