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

How are multiple extension properly supported?

    XMLWordPrintableJSON

Details

    • Icon: Question Question
    • Resolution: Considered - Question answered
    • Icon: Medium Medium
    • FHIRCast (FHIR)
    • 2.0.0
    • Infrastructure & Messaging
    • FHIRcast Observation
      FHIRcast extension
    • (NA)
    • 2.8
    • Hide

      There would only ever be a single extension at the same object level. Multiple sets of extended information describing the same FHIRcast object would result in something like – 

      { "key": "extension",

      "data": { "user-timezone": "+1:00", "com.example.goodnamespace.data" :

      { ... }

       }

      When there are multiple elements to be included in the extension. They should be coded as multiple elements in the json in the data field. 

      We will clarify this in the specification.

      We've seen very limited uptake of any extensions thus far, so standardizing them further doesn't yet seem important. 

      Show
      There would only ever be a single extension at the same object level. Multiple sets of extended information describing the same FHIRcast object would result in something like –  { "key": "extension", "data": { "user-timezone": "+1:00", "com.example.goodnamespace.data" : { ... }   } When there are multiple elements to be included in the extension. They should be coded as multiple elements in the json in the data field.  We will clarify this in the specification. We've seen very limited uptake of any extensions thus far, so standardizing them further doesn't yet seem important. 

    Description

      Given that the extension mechanism is to add a key with the value 'extension' how are mulytiple extension supported and how are they differentiated?

      (Comment 2 - imported by: Chris Shawn)

      Attachments

        Activity

          People

            Unassigned Unassigned
            chris Chris Shawn
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: