Actions
User Story #992
openEPIC #990: Clinical Assistance
Clinical Assistance Master / Protocol Content > frontend and backend
Status:
To Do
Priority:
low
Assignee:
-
Target version:
-
Start date:
Due date:
% Done:
0%
Estimated time:
Description
Clinical Assistance Master / Protocol Content¶
This feature is necessary if the fixed-list approach is selected.
The walkthrough explicitly says the first version requires the clinic's protocols to be written down, including what is checked for common findings.
US-002-02-02-01 — Manage Clinical Assistance Content¶
US-002-02-02-01-FE¶
User Story
As an authorized clinical administrator, I want to maintain predefined assistance content against examination findings so that doctors receive only clinic-approved information.
Frontend Requirements¶
Admin should be able to:
- View finding.
- Add associated assistance.
- Edit content.
- Activate/deactivate content.
- Preview content.
- Associate content with an examination finding.
Acceptance Criteria¶
- Content cannot be displayed unless associated with a valid finding.
- Inactive content is not shown to doctors.
- Changes to content are controlled.
- Historical consultations are not rewritten because master content changes.
Out of Scope¶
- AI-generated medical content.
- Automatic creation of clinical protocols.
US-002-02-02-01-BE¶
Backend shall maintain:
Clinical Finding
↓
Protocol / Assistance Content
↓
Version
↓
Active / Inactive
Acceptance Criteria¶
- Content is versionable.
- Only active content is returned.
- Content can be associated with a specific finding.
- Historical consultation records remain unchanged.
No data to display
Actions