You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »


General

The Vitalink Gateway will validate the incoming Kmehrmessage.

The end users 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 its user with a proper 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.

To be revised

Along with the XSD scheme validation the kmehr message will also be subjected to a general structure validation. This structure validation will on the one hand produce errors and on the other hand warnings. In the event that errors occur during the validation, the action will be suspended and the error reported. In the event that there are only warnings, the request will be dealt with. The final response will however be enhanced with the warnings, to construct a correct request.

Additional business validation

The Vitalink business project uses an extended Kmehrmessage, by defining its own transactions. The Vitalink Gateway requires extra requirements, on top of the standard Kmehr validation. This results in the next extra business validation rules:



  • No labels