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

Clarify FHIR Type Mapping

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive
    • Icon: Medium Medium
    • Using CQL With FHIR (FHIR)
    • 1.0.0-ballot
    • Clinical Decision Support
    • Using CQL
    • 2.14.2
    • Hide

      Agreed, we will change the language of both to say:

      List and Tuple types SHALL have elements of types that can be mapped to FHIR according to this mapping.

      In addition, we will provide example mappings of List and Tuple types that include Lists and Tuples.

      Show
      Agreed, we will change the language of both to say: List and Tuple types SHALL have elements of types that can be mapped to FHIR according to this mapping. In addition, we will provide example mappings of List and Tuple types that include Lists and Tuples.
    • Chris Moesel/Jen Seeman: 21-0-0
    • Clarification
    • Non-substantive

    Description

      Conformance Requirement 2.19 says that:

      List types SHALL be lists of element types that map to FHIR

      The phrase "types that map to FHIR" is not clearly defined. In the context of this section, which contains a table of CQL to FHIR mappings, one could infer that the table is the complete representation of "types that map to FHIR" – but this would disallow things like List<Condition>, which I don't think is the intent.

      Similarly the verbiage for Tuples might be misinterpreted to mean that a tuple element can't have a value that is another tuple (or a type from a ModelInfo).

      (And, as an aside, the list numbering is wrong in this section, as it has two number 1s).

      Attachments

        Activity

          People

            bryn.rhodes Bryn Rhodes
            cmoesel Chris Moesel
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: