Patient-view and risks for inappropriate advice #503

Some key CDS-Hooks use cases include:

1. Show card based on FHIR data
2. Show multiple cards relate to the same FHIR/context data, possibly from different CDS-Services

This makes the following scenario's possible:

• When the CDS-Client decides to update information a CDS Sever depends upon, an update to the resource(s) will be present in the scratch-patch of the CDS-Client/EMR. Other cards are based on the old data and and no longer valid, they might even providing suggestions that can be potentially harm-full to the patient.
• A Card is presented that provides a suggestion that solves an issue. The Suggestion is followed. Later, another change overrides that suggestion causing the original issue to re-appear. The current specification does not state the CDS-Service is recalled. It can also not access the information in the CDS-Client context. As a result, the practitioner cannot rely on the CDS-Service to provide guidance.

These scenario's both introduce significant and potentially dangerous situations. This raises the question of what use of the patient-view hook is justified that does not introduce these risks?
If none, we should not publish the hook.
If some, we should mention those, mention the risks and state that the patient-view SHALL not be used for such advice.

In practice this severely limits the use the patient-view. Addressing these issues might very well requiring new testing. As a result, one could even wonder whether the required changes are compatible with a maturity-level of 4.....