clarify or simplify med order priority distinctions

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Not Persuasive
    • Priority: Medium
    • FHIR Core (FHIR)
    • R4
    • FHIR Infrastructure
    • MedicationRequest
    • Hide

      The specific criteria around these codes are going to be driven by organizational rules and circumstances and isn't really something we can standardize.  If you only have 3 concepts, then you can either pick 'urgent' or 'asap' and would need to make that decision based on context or just pick one arbitrarily.  We don't think there's any further guidance that can be provided at the 'international', domain-independent level.

      In many cases, the timing information of the request (e.g. occurrencePeriod) may be as or more helpful than priority because it indicates when the event needs to occur.

      Show
      The specific criteria around these codes are going to be driven by organizational rules and circumstances and isn't really something we can standardize.  If you only have 3 concepts, then you can either pick 'urgent' or 'asap' and would need to make that decision based on context or just pick one arbitrarily.  We don't think there's any further guidance that can be provided at the 'international', domain-independent level. In many cases, the timing information of the request (e.g. occurrencePeriod) may be as or more helpful than priority because it indicates when the event needs to occur.
    • Vassil Peytchev/Jose Costa Teixeira: 8-0-0

      Routine and Stat are clear.

      Urgent and ASAP are both somewhere in between. The definitions specify that ASAP is higher priority than urgent, but we don't know what the criterion is. We have three values, and we don't know which one of those two to map our intermediate one to. (It's "emergency," so "urgent" seems correct, but then "asap" makes a hole in our semantic continuum.)

            Assignee:
            Unassigned
            Reporter:
            Jay Lyle
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: