General

The vault will validate the incoming Kmehrmessage.

The endusers' software-application should prevent a failing validation as much as possible, by composing the Kmehrmessage correctly.

If however for some reason a validation fails at runtime, the application should try to present the user with a proper and clear error message. This way, the end user can perhaps solve the problem or at least pass this information to the helpdesk of the vendor.

The validation will occur in two steps:

• Kmehr XSD validation
• Additional business validation

Kmehr XSD validation

The medication scheme Kmehrmessage must satisfy version “20161201-kmehr” of the XSD definition, see External Links#kmehrmessage-xschema.

A complete business validation set of rules can be found in the Medicationscheme cookbook under chapter 'xxx - Additional validation'.

Treatment suspension examples

Scheme below shows the limited possibilities that may occur. Registering a treatment suspension at a time there is no treatment is not recommended. The software should enforce that the previous is not possible. 

Updated usecases: