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

Update the "Reason for Revision" extension and specifications

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive
    • Icon: Medium Medium

    Description

      1. Change the name of the extension from “reason for revision” to “reason for revision or adaptation”
      2. Provide clear explanation of how revisions/adaptations of Plan/Phase Prescriptions/Plans should be recorded with an example in the IG. (use of revision code, link to previous instance using 'replaces')
      3. The goal of restrictions in the profiles would be that ‘replaces’ always points to the same kind or resource, i.e. ‘Planned Phase’ can only replace a ‘Planned Phase’, ‘Plan Prescription’ can only replace a ‘Plan Prescription’ etc. for our model to make sense. This is relevant to 'Phase Prescription', 'Plan Prescription', 'Planned Phase', and 'Treatment Plan'

             4. Change the name of the “Reason for Revision” value set to “Reason for Revision or Adaptation” value set

              5. Adjust values in the “Reason for Revision or Adaptation” value set.

      • Note: the values are in discussion with the CodeX RT SMEs. They will be added to this ticket as a comment in the next two weeks.

      Attachments

        Activity

          People

            Unassigned Unassigned
            ssebastian Sharon Sebastian
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: