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

Add ImplementationGuide.dependency.reason

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive
    • Icon: Medium Medium
    • FHIR Core (FHIR)
    • R4
    • FHIR Infrastructure
    • ImplementationGuide
    • Hide

      Will update spec to add ImplementationGuide.dependsOn.reason as type markdown. The cardinality would be 0..1, and would not be a summary element. 

      Show
      Will update spec to add ImplementationGuide.dependsOn.reason as type markdown. The cardinality would be 0..1, and would not be a summary element. 
    • Yunwei Wang/Josh Mandel: 14-0-1
    • Enhancement
    • Compatible, substantive
    • R5

    Description

      When we display the set of dependencies for an IG manually, we generally provide some text that explains the reason for the dependency and how the referenced IG is used.  We're contemplating being able to generate this portion of the specification automatically (to ensure it's a) present; b) complete and c) rendered consistently.  To do that, we need a standard place to put the text.  Could be extension or core element, but my leaning is that it makes sense as 0..1 in core.

      Attachments

        Activity

          People

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

            Dates

              Created:
              Updated:
              Resolved: