Observation status value typically always fixed to "final"

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive
    • Priority: Medium
    • US Bidirectional Services eReferrals (BSeR) (FHIR)
    • STU3
    • Public Health
    • (profiles) [deprecated]
    • Hide

      Requirements traceability mappings and instance examples will be added to all profile defintions. Any existing gaps in fulfillment of identified requirements we be resolved during the process.

      Show
      Requirements traceability mappings and instance examples will be added to all profile defintions. Any existing gaps in fulfillment of identified requirements we be resolved during the process.
    • AMS/Mead: 14-0-0
    • Clarification
    • Non-substantive

      Most of the profiles on Observation constrain the status to "final". Does this mean that once an observation is sent that it can't be updated? As well, not all profiles actually constrain the status to final (for example the Childhood Nutrition Request Obs profile), is there functional difference or is this just an oversight in some profiles?

      Please clarify if the contstraint of .status has any workflow implications.

            Assignee:
            Unassigned
            Reporter:
            Craig Newman
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: