Dosages: clarify use of text and patientInstruction

[qligier]

We should clarify the use of text and patientInstruction, as discussed in the last telco, and in light of #214. additionalInstruction could also be improved at the same time.

My proposition would be the following:

1. text may (shall?) contain the narrative representation of what is provided in structured form;
2. patientInstruction shall contain additional information that is not provided in structured form;
3. "Strong" implementations should use structured data and patientInstruction to present the information, and may optionally display the text for safety reasons.
4. "Weak" implementations should display the text and patientInstruction fields.

On additionalInstruction: I suggest making .text required inside additionalInstruction. Weak implementations could add all descriptions to the displayed narrative, strong implementations could either try to understand the coding or fallback to the description too. The content of additionalInstruction.text should not be duplicated to text or patientInstruction.

What do you think about this?

[oliveregger]

Telco: clarify 15.3 additionalInstruction would stay optional

[ziegm]

23.03.2023: PJ/QL/MZ

1. all structured: patientInstruction + all other elements (timing etc.)
2. all narrative (e.g. complex dosage): only patientInstruction
3. structured & narrative: some structured elements + patientInstruction + some unstructured information (complex dosage)

Procedere: make a proposal for the different types and lets have a look again. try without text element.

[ziegm]

Updates:

• Dosage guidance: text and examples
• Examples using Dosage.text before: AsNeededWithMaxDose, ComplexDosage
• Profile CH EMED Dosage: remove Dosage.text from Differential and update definition of Dosage.patientInstruction
• Change log

[qligier]

Seems good to me, thanks!

[ziegm]

06.04.2023 PJ/QL/OE/MZ:
everyone agrees on the changes