Pentla - Acceptance Criteria Dashboard

Step 1 — Platform Admin opens organisation management and starts creating a new organisation

Step 2 — Platform Admin creates the first unit (Production Facility)

Step 3 — Platform Admin creates the first Org Admin user using the primary contact email

Step 4 — Platform Admin sets verification status and activates the organisation

Step 5 — Org Admin accepts the invitation, sets password, and logs in

Step 6 — Org Admin completes the organisation profile

Step 7 — Org Admin configures organisation-wide preferences

Step 8 — Org Admin opens settings and sees sections appropriate for Custom Manufacturer

Step 9 — Org Admin invites team members: a CPO, a Production Manager, and a Technician

Step 10 — Org Admin enables notification preferences

Edge Cases

Step 1 — Org Admin views the current single-unit organisation's settings

Step 2 — Org Admin adds a second unit: a Clinic

Step 3 — Org Admin assigns the existing CPO to the new Clinic unit

Step 4 — Org Admin assigns a Technician to the Production Facility only

Step 5 — Org Admin views the user list and verifies unit assignments

Edge Cases

Step 1 — Log in as a CPO at a Custom Manufacturer

Step 2 — Log in as a CPO at an Integrated Clinic-Fab

Step 3 — Log in as a Physician at a Clinic (Prescribing Only)

Step 4 — Log in as an Admin at a Custom Manufacturer

Step 5 — Log in as a Production Manager at a Custom Manufacturer

Step 6 — Log in as a Technician at a Custom Manufacturer

Step 7 — Log in as a Billing Specialist at a Custom Manufacturer

Step 8 — Log in as an Org Admin and navigate to Settings at a Clinic (Prescribing Only)

Step 9 — Log in as an Org Admin and navigate to Settings at a Central Fab

Edge Cases

Step 1 — Org Admin navigates to User Management and selects a user to suspend

Step 2 — Org Admin suspends a CPO who has active clinical history (assessments, orders, fittings)

Step 3 — Org Admin reactivates the suspended CPO

Step 4 — Org Admin attempts to suspend the other Org Admin (leaving only themselves)

Step 5 — The remaining Org Admin attempts to remove their own Org Admin role

Step 6 — The remaining Org Admin attempts to suspend their own account

Step 7 — Org Admin views suspended users in the user list

Edge Cases

Step 1 — Platform Admin opens an active organisation's detail page

Step 2 — Platform Admin attempts to terminate the organisation while orders are in non-terminal states

Step 3 — After resolving outstanding orders, Platform Admin initiates termination

Step 4 — After termination, verify the organisation is in Terminated state

Step 5 — Verify data retention and accessibility

Step 6 — Verify no operational actions are possible

Edge Cases

Step 1 — Platform Admin enables Central Fab capabilities on the Custom Manufacturer

Step 2 — Org Admin verifies updated role availability

Step 3 — Org Admin verifies updated settings

Edge Cases

Step 1 — CPO opens the Patients area

Step 2 — CPO opens an assessment for that patient

Step 3 — CPO navigates to Orders and opens the device configurator

Step 4 — CPO navigates to Production to check an order at a quality checkpoint

Step 5 — CPO navigates back to Orders to perform a fitting

Data Flow Verification

Role-Based Access Spot-Checks

Organisation Lifecycle State Enforcement

User Lifecycle State Enforcement

Compliance and Audit Trail

Tenant Isolation

Data Minimisation (Cross-Organisation)

Deletion Constraints

Concurrent Operations

User Profile Access

Prerequisites

Mandatory and progressive fields

Draft orders without Clinical Prescription

Path A and B — CPO in the field

Path C and D — Admin creates, CPO continues

Path E and F — CPO creates directly in clinic

Transparency and consent per path

Edge Cases

Step 1 — Patient record created (Journey 0)

Step 2 — Verify transparency and consent

Step 3 — Enter Clinical Prescription (izvid) and Reimbursement Prescription (naročilnica)

Step 4 — Conduct Initial Assessment

Step 5 — Mark a required field as clinically unavailable

Step 6 — Upload scan files and clinical images

Step 7 — Complete assessment and create order

Step 8 — Trial Fitting after fabrication

Step 9 — Device Delivery

Step 10 — Post-delivery Follow-Up (2–4 weeks later)

Edge Cases

Step 1 — Create infant patient record

Step 2 — Transparency and guardian consent

Step 3 — Initial Assessment for cranial reshaping

Step 4 — Helmet order, fabrication, and initial fitting (Device Delivery)

Step 5 — Monthly Progress Review (checkup 1)

Step 6 — Progress Reviews 2 through N

Step 7 — Treatment complete

Edge Cases

Step 1 — Open returning patient and start Initial Assessment

Step 2 — Complete assessment and create order

Step 3 — Test Socket 1: Creation and Trial Fitting

Step 4 — CPO selects "Rebuild socket" — iteration loop

Step 5 — Test Socket 2: Trial Fitting — CPO selects "Proceed to definitive"

Step 6 — Definitive prosthesis delivery

Step 7 — Same patient returns 5 years later

Edge Cases

Steps

Edge Cases

Steps

Steps

Patient Lifecycle

Clinical Prescription Lifecycle

Reimbursement Prescription Lifecycle

Consent Lifecycle

Assessment Lifecycle

Attachments

Notifications

Patient Data Editing

Contextual Field Visibility

Regulatory Traceability

Step 1 — Create order from completed assessment

Step 2 — Configure device in the visual configurator

Step 3 — Link attachments

Step 4 — Set payment path (Path A)

Step 5 — Submit order (DRAFT → SUBMITTED)

Step 6 — Production through delivery (RECEIVED → IN_PRODUCTION → SHIPPED → DELIVERED)

Step 7 — Fitting

Step 8 — Complete order (Gate 3)

Edge Cases

Step 1 — Create order and configure prosthesis

Step 2 — Submit and fabricate test socket

Step 3 — Test socket fitting and iteration

Step 4 — Rebuild iteration

Step 5 — Proceed to definitive device

Edge Cases

Step 1 — Create order and configure helmet

Step 2 — Submit, fabricate, deliver, fit

Step 3 — Enter treatment phase (FITTING → IN_TREATMENT)

Step 4 — Treatment completion

Edge Cases

Step 1 — Configure and select Path C

Step 2 — Submit proposal (DRAFT → PENDING_APPROVAL)

Step 3 — Payer decision

Step 4 — Art 14 transparency and completion

Edge Cases

Step 1 — Place B2B order

Step 2 — Receiving organisation handles order

Step 3 — Status updates and delivery

Edge Cases

Step 1 — Create service order from existing device

Step 2 — Incident flagging

Step 3 — Fabricate, deliver, complete

Step 1 — Create adjustment order

Step 2 — Modify configuration

Step 3 — Submit and fabricate

Edge Cases

Step 1 — Validate warranty

Step 2 — Create reclamation order

Step 3 — Fabricate replacement and complete

Edge Cases

Patient PII visibility

Pricing visibility

Payer data visibility

Cross-org and compliance data

Search and dashboard visibility

Edge Cases

Gate 1 — Order creation

Gate 2 — Order submission

Gate 3 — Order completion

Cross-cutting gate behaviour

Step 1 — Device arrives at fitting

Step 2 — CPO rejects the device

Step 3 — Component modifications during rework

Step 4 — Rework and return to fitting

Edge Cases

Step 1 — Encounter validation warning

Step 2 — Override with justification

Step 3 — Verify override in traceability chain

Edge Cases

Search and history

Order lifecycle scope for cross-area consumers

Cancellation and rejection

Step 1 — CPO selects device type

Step 2 — Bilateral handling (if bilateral device)

Step 3 — Tree loads and pre-fill fires

Step 4 — CPO reviews and modifies components

Step 5 — Full validation on submission

Step 6 — Save and resume (edge case)

Step 1 — Device type selection and pre-fill

Step 2 — Knee unit cascade

Step 3 — Free-form entry for unlisted product

Step 4 — Component swap during fitting

Step 5 — Subtype with multiple activity variants (edge case)

Step 1 — Create a draft

Step 2 — Edit positions and rules

Step 3 — Add conditional dependencies and compatibility rules

Step 4 — Authoring validation (continuous)

Step 5 — Testing sandbox

Step 6 — Publish-time checks

Step 7 — Publish

Step 8 — In-progress orders unaffected (edge case)

Step 1 — Create an extension

Step 2 — Hide required position (edge case: blocked)

Step 3 — Preview and activate

Step 4 — Extension snapshot on order creation

Step 5 — New tree version triggers migration

Step 6 — Migration review

Step 7 — Extension deactivation

Step 1 — Create and manage catalogs

Step 2 — Add catalog entries

Step 3 — Inactive entry handling

Step 4 — Bulk import

Step 5 — Free-form entry promotion

Step 6 — Catalog usage statistics

Step 7 — Required position coverage check

Step 1 — Orders exist using current tree version

Step 2 — Domain expert publishes new version

Step 3 — In-progress orders continue unchanged

Step 4 — New order gets new version

Step 5 — Audit trail integrity

Step 1 — Reimbursement codes are Pentla-managed

Step 2 — Jurisdiction determines codes

Step 3 — Codes visible in configurator

Step 4 — Historical code retention

Step 1 — AFO tree accuracy

Step 2 — Prosthetic tree accuracy

Step 3 — Cranial helmet accuracy

Step 4 — Spinal accuracy