Skip to:

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

Explanation of terminology in the functional design in English

Description

We have agreed to use Dutch names for our medication building blocks (medicatieafspraak, toedieningsafspraak and the like) even in translations to other languages.

This is done to ensure we truly mean the same exact thing rather then something that may have (slightly) different meaning in that other language itself.

Even though this has been done in the functional design in wiki, is has not been made explicit nor has it been explained.

Suggestion:
Add some explanation into the English version of the design as to the fact that we are doing this and why.

Proposed solution (NL)

None

Proposed solution (EN)

None

Release notes (NL)

In het Engelse FO is in de reading guide (paragraaf 1.2) uitleg toegevoegd over het gebruik van de Nederlandse namen voor de bouwstenen.

Engelse vertaling - Functioneel ontwerp

In the English functional design we've added an explantion in the reading guide (paragraph 1.2) about the use of the Dutch terms for the buildingblocks throughout the design. 

English translation - Functional design. 

Release notes (EN)

None

is related to

Activity

Malou Paiman 
June 1, 2021 at 7:29 AM

Toegevoegd aan par. 1.2 Reading guide:

"In this document, Dutch terminology is used for the medication building blocks: Medicatieafspraak, Verstrekkingsverzoek, Toedieningsafspraak, Medicatieverstrekking, Medicatietoediening, Medicatiegebruik, Medicatieverbruik (see Table 1 for the English translations). Dutch terminology for the medication building blocks is consistently used even in translated documents, as a translation may not refer to exactly the same entity."

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

Details

Assignee

Reporter

Concerns version

Classification

Parties involved

Nictiz Informatie analist

Components

Fix versions

Priority

Better Excel Exporter

Created March 15, 2021 at 1:46 PM
Updated December 6, 2023 at 4:38 PM
Resolved September 29, 2021 at 1:21 PM