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

ExampleScenario structure

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Not Persuasive
    • Icon: Medium Medium
    • FHIR Core (FHIR)
    • R6
    • FHIR Infrastructure
    • ExampleScenario
    • Hide

      The use of a string is deliberate as this is something that will be used in diagram links, etc. and should ideally be semi-meaningful.  We believe our naming of elements is consistent with how other resources are handling this same pattern.

      Show
      The use of a string is deliberate as this is something that will be used in diagram links, etc. and should ideally be semi-meaningful.  We believe our naming of elements is consistent with how other resources are handling this same pattern.
    • Jose Costa Teixeira/John Hatem: 4-0-0

    Description

      In ExampleScenario, between instance, process, and actor the resource appears to be building an internal graph using key properties and string-holding "reference" elements (see also FHIR-43903).

      I am worried about using FHIR elements this way. Elements, including backbone elements, already have an id property. Similarly, there are ways of having "contained" resources and "references" - using words like "contained" and "reference" with different expectations than usual causes implementer confusion.

      Attachments

        Activity

          People

            Unassigned Unassigned
            ginocanessa Gino Canessa
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: