Your browser does not appear to support JavaScript. You may want to try one of the following:
You may want to try one of the following:
If the above does not work, try reloading the page yourself. Note that you will lose any unsaved changes:
shift
control
Show details
Hide details
This form has to be reloaded. This most likely happened because your session has expired, which might take to the login page. (If you think that you shouldn't see this message and that the problem persists, please contact support.)
Medications in reserve are often used in the Swiss prescription workflow and it seems important to properly support them.
The flag is supported by CHMED16A and will be added to CHMED21A and CH-EMED.
Consequences of status quo are poor usability and context-fit for integrated applications, which may lead to patient safety issues. Thus, the adoption by patients and professionals depends on this change.
Propositions:
1. Templates Medication Treatment Plan Item Entry Content Module , Prescription Item Entry Content Module , Dispense Item Entry Content Module : add an entryRelationship element with cardinality 0..1 that contains the new “in reserve” flag. If absent, the medication is a regular one. A new Swiss template ID is assigned.
2. These changes are definitive.
< entryRelationship typeCode =" COMP "> <act classCode =" ACT " moodCode =" DEF "> <templateId root ="TO BE DEFINED"/>
<code code ="TO BE DEFINED" codeSystem ="" displayName ="" codeSystemName =""/>
<statusCode code =" completed "/>
</act>
</ entryRelationship >
By example:
· Regular
· In reserve
Or we only define a single value to make it “in reserve” (but a code system is still needed), the absence of the entryRelationship makes it regular.
Drafted by HUG and CARA.