OccupationalData.combatZoneWork lacks location

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Not Persuasive
    • Priority: Medium
    • FHIR Core (FHIR)
    • STU3
    • Public Health
    • STU
    • OccupationalData [deprecated]
    • Hide

      Consideration for a Location of the combat has been was considered in the development of the model with multiple stakeholders. The conclusion was that it should not be included in the model. Further consideration may be worth another review with stakeholders from the VA (that previously identified this content as internally managed for benefits), and clinician input (e.g. Thom Kuhn).

      Show
      Consideration for a Location of the combat has been was considered in the development of the model with multiple stakeholders. The conclusion was that it should not be included in the model. Further consideration may be worth another review with stakeholders from the VA (that previously identified this content as internally managed for benefits), and clinician input (e.g. Thom Kuhn).
    • Lori Fourquet/Genny Luensman: 8-0-0
    • Enhancement

      OccupationalData.combatZoneWork lacks the location / region of the combat zone. It feels awkward to convey the dates without conveying some descriptor of the combat zone, itself. In the examples I have seen in real systems, it isn't typically a specific address, per se, but there is some identification of the country, region, or name of war.

            Assignee:
            Unassigned
            Reporter:
            Michelle Miller
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: