Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

glossary.md review and additions #21

Open
wants to merge 4 commits into
base: master
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
58 changes: 46 additions & 12 deletions input/pagecontent/glossary.md
Original file line number Diff line number Diff line change
@@ -1,34 +1,68 @@
# Glossary

In this specification, the following terms and concepts are used:

Do we have an explicit info on "status" like the treatment intended, actually being taken, etc.

If we look at 2 treatments that contain the same medication, will we see duplicate lines?
WE REALLY NEED TO MAKE THIS CLEAR IN THE DOCUMENTATION - WHEN THE SOFTWARE SEES 2 MEDICATION TREATEMENTS THAT CONTAIN THE SAME LINES, IT SHOULD NEVER SHOW THOSE LINES AS DIFFERENT.


Data objects

**Medication Record**: a collection of all past, future and current medication treatments for a patient. This does not necessarily incorporate adjacent information like allergies, lab results, etc.
## Medication Record

A collection of all past, future and current medication treatments for a patient. This does not necessarily incorporate adjacent information like allergies, lab results, etc.

## Medication Treatment

**Medication Treatment**: a set of medications used in a given context - for example one disease, or one episode.
A set of medications used in a given context - for example one disease, or one episode.

**Medication Treatment line**: One medication product that is used (or planned) for a patient, including the details on how the medication is or should be used (for example posology).
## Medication Treatment line

One medication product that is used (or planned) for a patient, including the details on how the medication is or should be used (for example posology). In short: a **medication treatment line** represents a single line of a treatment.
The same medication (line) can be associated with 2 treatments.
A medication treatment line always is associated with a treatment, even if that treatment is not a prescription or even planned (for example self-reported OTC medication usage).
A medication treatment line always is associated with a treatment, even if that treatment is not a prescription or even planned (for example self-reported OTC medication usage).

## Medication View

A purpose-specific collection of medication lines (medication view lines) representing a distinct view on the data that is relevant for that purpose, for example a patient-friendly schedule view, or a physician's aggregated view,...
This differs from the Medication Treatment in that the medication treatment is the "original" information - what is known at a given time to be the medication treatments of the patient - whereas the view can be transversal to several treatments, or detailed as needed.

**Medication View**: a purpose-specific collection of medication lines (medication view lines) representing a distinct view on the data that is relevant for that purpose, for example a patient-friendly schedule view, or a physician's aggregated view,...
This differs from the Medication Treatment in that the medication treatment is the "original" information - what is known at a given time to be the medication treatments of the patient - whereas the view can be transversal to several treatments, or detailed as needed.
There are two different subsets of medicationviews that will be named:

**Medication View line**: one entry in the medication view, representing a purpose-specific perspective on one or several medication treatment lines - for example a single line in a patient's schedule for the week.
1. **Core medication views** are views that are composed from the base **medication treatment lines**. This data is not manipulated or translated to another version of itself.
2. **Synthetic medication views** are views that are generated from the core medicationview. For example: the core medicationview can have some lines with the medication as a package, while others may contain a substance. A synthetic medication view could make the decision to translate the core view so all treatment lines are named by substance, and can use this as a different view.

## Medication View line

One entry in the medication view, representing a purpose-specific perspective on one or several medication treatment lines - for example a single line in a patient's schedule for the week.
Because the medication view line (and medication view) are purpose-specific, there may be different medication view lines for the same medication treatment line.

Note that structure of the Medication View line is similar to that of the Medication Treatment line, but they are used differently. One to capture the original data, the other to represent the derived data.

## Medication Statement

The [base FHIR profile](https://hl7.org/fhir/medicationstatement.html) for the medication. The medication statement (or medication usage in [FHIR Release 4](http://hl7.org/fhir/R4)).

## Medication Reconciliation

The act of improving the overall **medication record**. This by reviewing the current **medication treatment lines**, or by merging different **medication treatments** into a new, updated and more complete or more correct medication treatment.

Reconcilliations should happen in transitions of the care, for example when a patient goes on an intake in a hospital, or when a GP prescribes new medication.

**note that structure of the Medication View line is similar to that of the Medication Treatment line -but they are used differently - one to capture the original data, the other to represent the derived data*
The process of reconciliation commonly has following steps[^1]:

**Medication statement**:
1. Develop the list of current medications for the patient
2. Develop a list of medication that needs to be prescribed
3. Compare these two lists
4. Make clinical decisions based on the comparison
5. Upload the medication record

**Medication Reconciliation**:
## Medication data collection

**Medication data collection**
## Other references

* [functional description](functional-description.html)
* [medicationrecord fhir resources](medicationrecord-fhir-resources.md)

[^1]: https://www.ncbi.nlm.nih.gov/books/NBK2648/: Medication reconcilliation source
2 changes: 1 addition & 1 deletion input/pagecontent/medicationrecord-fhir-resources.md
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,7 @@ Whether as a document or as a collection, the Medication Record can contain any
* Medication Treatment Line can be associated with information from different origins:
* **Prescriptions**, or any known change to a treatment, with the [MedicationRequest](http://hl7.org/fhir/medicationrequest.html) resource
* **Dispenses**, with the [MedicationDispense](http://hl7.org/fhir/medicationdispense.html) resource
* **Administrations**, ttypically informed by the patient or by a nurse or other care giver, with the [MedicationAdministration](http://hl7.org/fhir/medicationadministration.html) resource
* **Administrations**, typically informed by the patient or by a nurse or other care giver, with the [MedicationAdministration](http://hl7.org/fhir/medicationadministration.html) resource
* In some cases, a medication information can be obtained by a statement given by a patient (or related person) about the usage of the medication. This is done with the [MedicationStatement](http://hl7.org/fhir/medicationstatement.html) resource

* A set of examples is provided in this document to show the combinations of these elements in realistic scenarios.
Expand Down