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

ElementDefinition profiles should be able to be GraphDefinitions

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Very High Very High
    • FHIR Core (FHIR)
    • R4
    • FHIR Infrastructure
    • ElementDefinition
    • Hide

      We will define an extension on ElementDefinition - graphDefinition 0..* canonical(GraphDefinition).

      Definition - indicates a GraphDefinition the current element (Resource) or referenced instance (canonical or Reference) must comply with

      Will update the tooling to render and validate if these extensions appear.

      Show
      We will define an extension on ElementDefinition - graphDefinition 0..* canonical(GraphDefinition). Definition - indicates a GraphDefinition the current element (Resource) or referenced instance (canonical or Reference) must comply with Will update the tooling to render and validate if these extensions appear.
    • Grahame Grieve/Richard Ettema: 6-2-2
    • Enhancement
    • Non-substantive
    • R5

    Description

      GraphDefinition allows the assertion of a profile plus additional expectations around related artifacts. For certain types of constraints, it can be a much more efficient way of defining expectations, particularly when dealing with messages, documents and other Bundles. We should allow it in ElementDefinition.type.targetProfile and type.profile. (The latter is needed for things like Parameters or Bundle where the type is actually a resource rather than a reference to one.)

      Attachments

        Activity

          People

            lloyd Lloyd McKenzie
            lloyd Lloyd McKenzie
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: