Telecom doesn't allow for alternate systems

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Medium
    • FHIR Core (FHIR)
    • DSTU1 [deprecated]
    • Modeling & Methodology
    • STU
    • Datatypes
    • Hide

      Document the use of URL more clearly, and the grounds for pulling out phone / fax / email as non-url options. Rename code url to other, and say that if you use other, the value SHOULD be a url. If the value is not a URL, it will require human interpretation

      Create a new task to deal with hearing impaired requirements, and research what would be appropriate.

      Show
      Document the use of URL more clearly, and the grounds for pulling out phone / fax / email as non-url options. Rename code url to other, and say that if you use other, the value SHOULD be a url. If the value is not a URL, it will require human interpretation Create a new task to deal with hearing impaired requirements, and research what would be appropriate.
    • Mark Kramer / Richard Etterna: 4-0-0
    • Enhancement
    • Non-compatible
    • DSTU1 [deprecated]

      There's a constraint that says you must have a system if you have a value. And system is constrained to be one of only 4 codes. There are lots of other possible systems - tty devices, pagers, etc. We either need to add a system of "other" or we need to drop the constraint. As well, it seems to me that adding a custom system would modify the interpretation of the "value"? Is that accurate?

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

              Created:
              Updated:
              Resolved: