Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

NoDescriptionComment
1.1Header
1.1.1

Unambiguous identification of the patient

Name, first name & NISS number

1.1.2

Date and hour of last change + identification of the care provider who changes the medication scheme

Date format = dd/mm/yyyy
Hour format = HH:MM

1.1.3

Date and hour of print + identification of the care provider who prints the medication scheme (details of the pharmacy + owner)

Date format = dd/mm/yyyy
Hour format = HH:MM

1.2

Sorting of medication lines within groups per CD-TEMPORALITY

Obsolete medication (see M. Concept: Obsolete medication) is not displayed.

Sorting:

  1. CD-TEMPORALITY = chronic
  2. CD-TEMPORALITY = acute
  3. CD-TEMPORALITY = oneshot

Translation of the codes, see M. Specific translation of supported Kmehr table codes.

1.2.1

Within the column the medication lines are sorted according to periodicity.

The sorting is defined in M. Specific translation of supported Kmehr table codes.

The effect will be for example like this:

Daily

  • daily
  • per x hour

Non-daily

  • No frequency
  • 2-daily, …
  • weekly, …
  • monthly, …
1.2.1

Columns (see 1.2) and periodic subdivisions (see 1.2.1) that are not entered in the medication scheme are not printed.


1.3Display of columns
1.3.1Fixed pattern of 16 columns

Column / description of the product: – Frequency – Start – End – Ingestion / unit – Morning – Breakfast (before, during and after) – Lunch (before, during and after) – Dinner (before, during and after) – Sleep. Refer to example.

1.3.2

Dynamic display of columns for specific times: ingestion times at specific hours are only displayed if they are filled in.

If more than 5 specific hours are used in a medication scheme, the 6th and following are printed as text in a line without columns. E.g. “3 om 16:00”.
Specific times are displayed to the minute: format HH:MM.

1.3.3Ingestion times (Code table CD DAYPERIOD) that cannot be assigned to a column, are displayed as text in a line without columns .See M. Specific translation of supported Kmehr table codes
1.4The complete description of the product: (content / medicinalproduct / intendedname or deliveredname) displayed in the “medication” column including dose and galenic form. The dose is not provided as separate attribute in KMEHR. Information about brand name, galenic form, dose and packaging size is available via the CNK (National Code Number), but not all care providers have a database of CNKs available.
1.5Unit uniformly displayed We take the first CD-ADMINISTRATIONUNIT element from regimen as the unit. There is 1 column ingestion /unit entered for the ingestion pattern. We provide the same patient oriented translation for form/unit in all software packages. See M. Specific translation of supported Kmehr table codes.
1.6Ingestion uniformly displayed from table CD-DRUG-ROUTE. There is 1 column Ingestion/unit entered for the ingestion pattern. We provide the same patient oriented translation for ingestion between all software suppliers. See M. Specific translation of supported Kmehr table codes
1.7Indication and instructions for use are displayed in the “remark” column.

Indication = Healthcareelement "medicationuse"

Instructions = Medication element <instructionforpatient>

1.8Medication lines with the validation status “to be validated” are always printed. There is no mention of this status in the print for the patient.
1.9Information message in footnote text“This medication scheme is managed by your care team and shared via Vitalink. If you have questions about it or in doubt, it is advised to contact your general practicioner. More information can be found at www.vitalink.be/toelichtingms/.”

...

NoDescriptionComment
2.1Sorting of medication lines in a uniform manner

Sorting by:

  1. CD-TEMPORALITY group
  2. Periodic subdivision (described below, refer also to M. Concept: Combined use of frequency and day)
  3. Day in period (with weekly, monthly, once only or no frequency)
  4. Alphabetically
  5. Start date
2.1.1

Periodic subdivision 1:

show daily (frequency = "D") medication together.

Periodicity D = daily
2.1.2

Periodic subdivision 2:

show 'N+1'-daily (multiple of weeks) medication medication together. The frequency column contains frequency and the daynumber, e.g. "every 2 days, day 1 & 2 ".


Sorting as defined in M. Specific translation of supported Kmehr table codes.

Periodicity DT = 2-daily

Ditto for 3-daily, etc.

2.1.3

Periodic subdivision 3:

show weekly (multiple of weeks) medication together. For medication with ingestions on several days per week, the days are displayed on different lines. The frequency column contains the frequency and the daynumber or weekday, e.g. "every 2 weeks, day 3 ".


Sorting by:

  1. Frequency (as defined in M. Specific translation of supported Kmehr table codes.)
  2. Daynumber or weekday: day of the week
  3. Alphabetically
  4. Start date
2.1.4

Periodic subdivision 4:

show monthly (multiple of months) medication together. For medication with ingestions on several days per month, the days are displayed on different lines. The frequency column contains the frequency and the daynumber, e.g. "every 2 months, the 3rd".

Sorting by:

  1. Frequency (as defined in M. Specific translation of supported Kmehr table codes.)
  2. Day: day of the month
  3. Alphabetically
  4. Start date
2.1.5

Periodic subdivision 5:

show yearly (multiple of years) medication together. For medication with ingestions on several dates per year, the dates are displayed on different lines. The frequency column contains the frequency and the DD/MM part of the date, e.g. "every 2 years, 15/3".

Sorting by:

  1. Frequency (as defined in M. Specific translation of supported Kmehr table codes.)
  2. DD/MM of date
  3. Alphabetically
  4. Start date
2.2Empty horizontal bar between different columns and periodic subdivisions
2.3Start date or condition / End date or condition displayedAt the front in the table Date format = dd/mm/yyyy
2.4Subsequent medication: indicate with the help of start & end condition in start/end columnGM 1: end condition “OP = STOP” GM 2: begin condition “With stop GM 1”
2.5Treatment suspension
2.5.1

Permanent suspension: medication line is only displayed for the patient if the suspension lies in the future.

Jira
serverimec Validation Lab
serverIdac11aa92-3976-3161-9ddb-5020cc76f1c7
keyVAZG-147


2.5.2

Temporary suspension: the treatment suspension is only displayed if the suspension lies in the future.

Jira
serverimec Validation Lab
serverIdac11aa92-3976-3161-9ddb-5020cc76f1c7
keyVAZG-147


2.5.3A treatment suspension is displayed as a line under the medication line to which it is applicable, with red background and provided with the text “!STOP! Due to: …”
2.6Specific times are added as column on the right of the scheme, visually explicitly separated from the fixed pattern.
2.7

Convert decimal numbers in “quantity” to fractions.

  • 0.25 = ¼
  • 0.50 = ½
  • 0.75 = ¾
  • 1.25 = 1 + ¼
  • 1.50 = 1 + ½
  • 1.75 = 1 + ¾
  • ...

As you see, numbers and fractions > 1 also have to be provided.


2.8Free text <posology> is displayed as a nonstructured text field in a line without columns instead of the ingestion times.
2.9Medication lines for which the frequency is not entered, are considered as non-recurring.
2.10Standard formatA uniform format of the overview scheme with regards to font and style is aimed at. There is only one logo displayed: the Vitalink logo.

...