prevention-point v0.3.3

Technical

• this is a test release with no actual changes

prevention-point v0.3.2

Technical

• feat(ci): add action to build containers on tag
• feat(ci): use multi-layer build caching for frontend container
• fix(ci): push specific tags second for better web UI display

prevention-point v0.3.1

Improvements

• fix(frontend): broken services api path call

prevention-point v0.3.0

• Merge pull request #503 from CodeForPhilly/features/k8s-deployment
• Merge pull request #505 from CodeForPhilly/dep-2
• fix(k8s): move postgresql data into subPath to avoid conflict w/ lost+found
• fix(k8s): remove duplicate use of http port name
• fix(k8s): switch to Recreate update strategy to deal with PVC
• fix(k8s): remove liveness probe on backend
• Merge pull request #502 from CodeForPhilly/visit-ID-required-for-sep-data-473
• Merge pull request #506 from CodeForPhilly/fixes/enable-admin

prevention-point v0.2.0

Alphanumeric sep id 497 (#501)

* Getting there

* SEP ID should now accept alphanumeric strings. Lowercaseness is enforced on creation and search.

* Fixed backend tests and made sep id unique in model.

Prevention Point Release v0.1.0-rc.1

Prevention Point project release v0.1.0-rc.1

This is the first featured MVP release that is going public with the Prevention Point organization. This MVP covers basic functionality for the unified reporting system that will improve Prevention Points operations.

Release features:

• Adding new participants with participant data and visit data
• Modifying existing participant data and adding new visits to a program queue
• Searching for existing participants via, first name, last name, and/or IDs
• Modifying existing participant and visit data from within the program queue
• Removing participants from queue programs

prevention-point v1.0.0-beta.1

First tagged release:

The minimum viable product for the Prevention Point project is intended to replace the check-in and queue management process.

The check-in process is as follows:

1. Individual speaks with front desk employee
2. Front desk employee adds individual to HRSC sheet according to program of care
3. Providers for program monitor HRSC sheet (“queue”) to determine next individual that will be seen
4. Individual is either called for their appointment or leaves without being seen