Mapping language should have a way of explicitly declaring unknowns - 2018-May Core Norm Infrastructure #200

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Medium
    • FHIR Core (FHIR)
    • STU3
    • FHIR Infrastructure
    • Binary
    • (many)
    • Hide

      Add a log "xxx" as part of the source statement, and make it optional to have a make part if you have a log part

      Show
      Add a log "xxx" as part of the source statement, and make it optional to have a make part if you have a log part
    • Grahame Grieve/Rick Geimer: 9-0-0
    • Enhancement
    • Compatible, substantive
    • STU3

      Comment:

      Neither of these mappings explicitly declare that Binary.securityContext gets thrown away when downgrading to R2 and is unknown when converting to R3. (In most places, we'd be able to use an extension to convey those elements, but not in Binary.) The mapping language should have a way of explicitly declaring if something is unknown or will be lost in a conversion.

      Summary:

      Mapping language should have a way of explicitly declaring unknowns

            Assignee:
            Unassigned
            Reporter:
            Lloyd McKenzie
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: