...
- Errors from "Errors" section of the specification. This mainly concerns the protocol specification.
- Errors after reception of faulty artefacts from another implementation.
- Errors when processing correct artefacts by your implementation.
- Errors during generation of faulty artefacts by your implementation.
Erroneous data mapping
There is always a possibility that incoming central data can not be imported in the data model of your application.
The cause can be e.g.:
- wrong input from the end-user of the sending application
- a bug in the sending application
- a design error in the sending application
- an unexpected dialect of the specification used by the sending application
- ...
In this case, When participating in data exchange E.g. in the Vitalink Medication Scheme, you can import data into your application that are not what you expected (e.g. the sending application made a mistak xxx). In that case, your application should always consult the user when incoming data from the central source can not be processed, your application should always consult the user. Show as much machine-readible or plain text information as you can to the user so the least possible information is lost. as posibble the information of the incoming data to your user. This should allow your user to correct the error manually up to a maximal level, or to gather enough information for later analysis.
Input validation
Typically, an application validates the data a user manually enters to see whether it is in the expected format and is within the range of allowed values for that input. Verify that this validation of user input is also applied for incoming data from the central source. If the validation fails, the data should be handled as erroneous data.
...