Content Comparison

...

Care Programs Landing page:

• All programs patient has ever been enrolled in is displayed
• For a patient program, workflow and state are shown for all active states
•  For a patient program any outcome is displayed
• default sorting by reverse chronological order of date enrolled
• data can be sorted by column headers

Expanded Programs

• Within the patient program row, there is a structured list for each workflow
• Within each workflow, all of the historical states the patient has been in are displayed, in reverse chronological order by start date

Record Program Enrollment

• Basic program enrollment fields should be captured (program, dates, location)
• For any workflows set up within the program, options are given to enroll patient into
• User should be able to record a date completed (e.g. for retrospective entry)
• If a date completed is entered, outcome should be required (if configured)
• We should prevent overlapping enrollments of the same program?
• Question: Can we/should we limit the programs a patient is eligible to be enrolled in?

Edit Program Enrollment

• Dates/Location can be edited
• If a date completed is added, outcome (if configured) should be prompted for and required
• We should prevent overlapping enrollments of the same program?

Delete patient program

• User should be prompted to confirm a delete (or cancel)

Close Program

• Date completed is required when closing program
• If configured, outcome should be prompted for and required

Add State

• State to transition to and date should be entered
• if the patient is in a current state, they should be able to choose "no state" to transition to
• Dates should be validated for:
  • overlapping states
  • need to be within program enrolled/completed dates 

Edit State

• User can edit the state and date
• data validations as "Add State" above

Delete state

• User should be prompted to confirm a delete (or cancel)