2015May core #904 - How is encounter diagnosis handled?

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive
    • Priority: Medium
    • FHIR Core (FHIR)
    • DSTU1 [deprecated]
    • Patient Administration
    • Encounter
    • Hide

      The reason and indication properties are actually the one thing, so will collapse into the 1 property called reason which can be either: Procedure, Condition or codeableConcept. This property will be changed to permit multiple values (cardinality 0..*)

      (Technical correction, can't do the above, so remains 2 properties - reason and indication - that are multi-cardinality)

      A standard extension (positive int) can be used to indicate the sequence of diagnosis (1 = primary).

      We will include a note that we would like to get implementer feedback on this issue to see if a more detailed aproach is required.

      Show
      The reason and indication properties are actually the one thing, so will collapse into the 1 property called reason which can be either: Procedure, Condition or codeableConcept. This property will be changed to permit multiple values (cardinality 0..*) (Technical correction, can't do the above, so remains 2 properties - reason and indication - that are multi-cardinality) A standard extension (positive int) can be used to indicate the sequence of diagnosis (1 = primary). We will include a note that we would like to get implementer feedback on this issue to see if a more detailed aproach is required.
    • Brian/Alexandra: 5-0-0
    • Clarification
    • Non-compatible
    • DSTU1 [deprecated]

      Existing Wording: Encounter.reason

      Comment:

      Many exisitng qualtiy measures require the ability to specify that an encounter diagnosis (asssumed to be "reason" in this case) was a primary or secondary diagnosis. Also, sometimes it is required to differentiate between facility billing and professional billing codes. Support for this is needed to meet current-day use cases. How are these attributes supported?

            Assignee:
            Unassigned
            Reporter:
            Claude Nanjo (Inactive)
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: