Add medication-followup-protocol plugin

[milosdjakovic-vicert]

A practice defines a medication class as a list of timed steps. A provider enrols a patient onto one from the note, and a daily scheduled walk runs whatever is due.

What it adds

• A configuration page in the left sidebar, where a practice builds its medication classes and the steps inside them.
• A control in the note header that enrols a patient onto a class in one action, shown only when a committed prescription on that note matches a configured class.
• An all programs control on the patient chart opening a read only pane, one section per enrolment, showing every step, its due date and its status.
• A questionnaire offered in the patient portal when a questionnaire step is live.
• A text only chart banner while an enrolment is running.

Coverage

Coverage is a classification path from the FDB catalogue rather than a product identifier. Picking a medication group stores the whole path, so one entry covers every strength and form of a drug without anybody picking them one at a time.

Steps

A step is a day offset, one of three kinds, its content, and optionally a condition. The kinds are a message to the patient, a questionnaire in the portal, and a task for a team or a named person. The one condition is whether the recheck appointment is still unbooked, and it is evaluated on the morning the step is due rather than remembered from when the programme started.

Tests

269 tests pass. Every one carries, verbatim, the acceptance criterion identifier or the scenario title it covers, so one grep over tests/ produces the whole mapping between the behaviour contract and the code.

Custom data namespace is vicert__medication_followup_protocol, matching the convention already used by salesforce-to-canvas-integration.