Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

MedicationUse StopType found values do not correspond with MedicationUseStopTypeCodeList values.

Description

 In the zib MedicationUse there is the MedicationUseStopType field which can (according to the zib wiki) take on the values “Tijdelijk” and “Definitief”. When parsing the MedicationUse touchstone XML the value “active” was found in the status field (this maps to MedicationUseStopType). Active is not one of the possible values the MedicationUseStopType can have according to the wiki. According to the HAPI parses, status can be one of the following values: active, completed, enteredInError, Intended, Stopped, onHold and Null.

This does not allow for the correct interpretation of found values in the XML.
Is there a mapping from the values that can be found to 'true'and 'false'? Or is this a mistake?

With kind regards,

Yuri Bonanno

Verduidelijking van Impact

Laag.

Proposed solution (NL)

Add a ConceptMap to improve clarity on the relationship between MedicationUseStopType and MedicationStatement.status

Proposed solution (EN)

None

Release notes (NL)

None

Release notes (EN)

None

is related to

Activity

Show:

Ardon Toonstra February 13, 2019 at 3:25 PM

Issue gelinkt aan  voor het maken van de ConceptMaps.

Ardon Toonstra February 13, 2019 at 3:23 PM

Alexanders answer: 

MedicationStatement.status serves the purpose of depicting the status as a whole. The zib MedicationUse, concept MedicationUseStopType serves a partial status purpose. It only serves to support the reason behind stopping use. Temporary or Permanent. 

temporary maps to on-hold 

permanent maps to stopped 

Other statuses bear no relationship to MedicationUseStopType. We could add a ConceptMap or other elaboration to allude to this.

Resolved
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Classification

Patch (Z)

Informatiestandaard onderdelen

FHIR-package

Information standard

BgZ
Medicatieproces

Fix versions

Priority

Better Excel Exporter

Created February 7, 2019 at 11:15 AM
Updated January 12, 2024 at 12:54 PM
Resolved February 10, 2019 at 4:41 PM