PROTOTYPE STATUS
What PharmacOps demonstrates and what still needs validation.
This page distinguishes the prototype's scope, connected features and planned development. The published status reflects this first version of the prototype.
| Capability | Status | Evidence | Limitation |
|---|---|---|---|
| Landing page and content | Available | Pages rendered in this version | Describes a concept and its status; not a hospital deployment |
| Populated landing page twin | Demonstration scene | 5 × 4 T01 with 16/20 positions and example rules | Not real inventory; not synchronised with /demo |
| Example identification | Tested in demonstration | Ten sample cases in /demo | Does not analyse new images or measure accuracy |
| Destinations and reservations | Tested in demonstration | Grouping by destination and reserving positions | State isolated in browser memory |
| Confirmation and unloading | Tested in demonstration | Explicit actions and session events | Human declaration; no physical sensor |
| Individual review | Tested in demonstration | Shared T01 positions, without fixed zones | Does not represent an actual hospital queue |
| Automatic mode | Prepared playback | Filling, fictional sign-in, guided review and unloading by zone | Simulates capture, identification and confirmations; no analysis or hardware |
| Human feedback | Tested in demonstration | DEMO roles, reasoned decisions and a collection of reviewed signals | In memory; roles without authentication; no automatic training |
| Engine evaluation and learning | Planned development | Documented architecture and feedback schema | No pipeline, real data or measured accuracy improvement |
| Connected mobile capture | Pending | /captura informa que no está disponible | No pairing or server authorisation |
| New image analysis | Pending | /estacion informa que no está conectado | No provider, test samples or authorised catalogue |
| Physical automation | Planned development | Phase 2 concept diagram | No robot or physical verification |
| Clinical validation | Pending | No published results | Does not determine suitability for dispensing |
What we will measure
We will evaluate the process using authorised samples and measurable criteria.
- Identification
- Labelled samples and catalogue/model versions
- Review
- Unresolved cases and recorded interventions
- Time per phase
- Session and confirmation timestamps
- Location
- Comparison of destination and physical verification
Visible evidence. Distinguish what was observed, supplied by the catalogue and confirmed by a person.
Explicit review. Do not force an identity from insufficient information.
Traceable actions. Record confirmations and corrections without deleting previous events.
Declared scope. Distinguish prototype, example, live integration and future development.
Where the data comes from
The homepage shows a fixed T01 scene with 20 cells, 16 of them occupied. The selected generic names and strengths were checked against AEMPS CIMA. Zones, destinations and quantities are fictional. The demo offers ten sample cases with prepared identification results; reservations and confirmations are calculated locally during the session. These are independent scenes with the same rules for organising by destination. No hospital catalogue is connected and no authorised samples are loaded.
What the operator does
In the planned MVP, the operator presents a sample, reviews the evidence, physically places the item and confirms its location. The demo lets you confirm each movement or play it in automatic mode. A recorded location does not mean stock has been released for use.
Image processing
This version does not allow uploads or capture of new images. No image processing server or provider is configured, and retention, deletion and access for a connected session have not been defined. Capture will remain disabled until these points and privacy documentation are resolved.
Validation pending
There are no accuracy metrics or clinical results. Evaluation requires authorised samples, verified labels, catalogue and model versions, test conditions and professional review. The LabORA challenge is the source of the challenge, not product accreditation.
