Reviews · Primoro

❓

Open questions

decisions parked from meetings View dashboard →

Every question raised in a meeting that wasn't decided on the spot. Resolve them with answers that get written into the relevant spec section.

📝

1 open View all meetings →

Spec changes proposed from meeting transcripts, waiting to be applied as draft or dismissed.

🔗

61 pending View all →

Other modules' specs that may need cascade updates because of a recent spec change elsewhere.

Appointment Manager (technical) — caused by change on Surgery & Decon Day View
Appointment Manager must confirm whether its API contract with PMS systems (Dentally, etc.) exposes charted tooth data linked to appointments, since Surgery Decon Day View depends on this as the primary source for ToothNumbers[].
External Provider API Gateway & Rate Governance (technical) — caused by change on Surgery & Decon Day View
Rate governance and traffic classification may need to account for new PMS API queries (charted treatment data per appointment) if they introduce a distinct traffic class or high-frequency polling pattern.
Lab Manager (technical) — caused by change on Surgery & Decon Day View
Lab Manager's day-view integration may benefit from the same charted tooth data source once clarified, to align tooth-number display across decon and surgery tablets.
Digital Forms (technical) — caused by change on Smart Treatment Proposals
Digital Forms must reference the form template library as an authoritative source that practices can clone and customise, affecting form creation and assignment workflows.
Admin Control Plane (technical) — caused by change on Smart Treatment Proposals
Admin Control Plane must document seed template deployment and management as part of tenant provisioning and onboarding.

📄

22 pending View all →

Modules whose website copy may be stale because their UX or technical spec just changed.

Surgery & Decon Day View — from technical update
Add open question on PMS API availability of charted tooth data linked to appointments
Smart Treatment Proposals — from technical update
Document the pre-populated form template library as a technical requirement, including branding inheritance, clone-and-edit capability, and Foxbury seed templates
Digital Forms — from technical update
Confirm whether aftercare content blocks must support rich media (video and images) at MVP or only in a later iteration
Digital Forms — from ux update
Confirm whether aftercare template builder requires a dedicated drag-and-drop design view or can reuse the existing forms component library
Task Manager — from technical update
Work packages must support a CalendarId field linking them to a role/team calendar; the system maintains one calendar per configured role/team

✏️

16 drafts

Module specs with unsaved or unpromoted drafts. Open the editor to review, save, or discard.