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

Combine the task type code systems into one code system

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Highest Highest
    • US Specialty Rx (FHIR)
    • 2.0.0-ballot
    • Pharmacy
    • STU
    • Specialty Rx CodeSystem - Task Output Type [deprecated]
    • Hide

      Combine codes from the following code systems into a single one named specialty-rx-task-characteristic. Include non-selectable grouping property to be used in value set definitions.

      • specialty-rx-task-input-type (which contains codes representing specific types of information inputs that may be provided in a Task, in Task.input, to be used during the Task's processing)
      • specialty-rx-task-output-type (which contains codes enumerating types of outputs that can be populated after processing the Task, in Task.output)
      • specialty-rx-task-type (which represents a different kind of concept than the others:  defining the nature of the Task itself as a request for consent vs request to launch a SMART app questionnaire)
      • specialty-rx-task-identifier-type (which defines identifier types specific to application launching based on a submitted task)

      Adjust associated value set resources to define members based on the code system grouper values.

      Show
      Combine codes from the following code systems into a single one named specialty-rx-task-characteristic. Include non-selectable grouping property to be used in value set definitions. specialty-rx-task-input-type (which contains codes representing specific types of information inputs that may be provided in a Task, in Task.input, to be used during the Task's processing) specialty-rx-task-output-type (which contains codes enumerating types of outputs that can be populated after processing the Task, in Task.output) specialty-rx-task-type (which represents a different kind of concept than the others:  defining the nature of the Task itself as a request for consent vs request to launch a SMART app questionnaire) specialty-rx-task-identifier-type (which defines identifier types specific to application launching based on a submitted task) Adjust associated value set resources to define members based on the code system grouper values.
    • Frank McKinney / John Hatem : 6-0-0
    • Correction
    • Compatible, substantive

    Description

      There is no clear need or value to separating the task type into three code systems. You can keep the concepts and then make them all members of one combined code system. I suggest making that the "task type" code system. Then each value set will be subsets of that code system (so those CLDs will change.) You can even use the current name of the current code systems as "groupers" in the over all code system. Those can be marked as "non-selectable" so that the grouper codes are not eligible for use in exchange and can be used as the header code for the "intensional" CLD for your value sets. That means you can continue to add to the code system in the future and the value sets would pick up the new codes, and only the ones you want, automatically. Talk to the vocabulary wg if you need help

      Attachments

        Activity

          People

            Unassigned Unassigned
            Rob_McClure Rob McClure
            Rob McClure
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: