What is the Dental Studio patient record?
The Dental Studio patient record is the planned shared context for the entire suite. It is intended to connect reviewed identity and contact information, medical and dental history, intake forms, consents, supporting documents, treatment context, insurance coverage, claims, balances, prescriptions, pharmacy events, and patient communication.
It is more than a document folder and more deliberate than a generic customer profile. Every important fact should have a source, status, author or system actor, timestamp, and history.
Record domains planned for the suite
- Patient identity and contacts: demographics, communication preferences, responsible parties, guardians, and emergency contacts.
- History and intake: medical and dental history, medications, allergies, concerns, consents, and submitted documents.
- Clinical context: reviewed findings, treatment plans, procedure context, notes, images or links to authoritative imaging systems, and follow-up requirements.
- Coverage and revenue: plans, subscriber details, benefit responses, estimates, claim history, remittance, adjustments, balances, and payments.
- Medication workflow: authorized prescription references, selected pharmacy, consent, fulfillment state, delivery status, and exceptions.
- Communications and evidence: invitations, notices, acknowledgments, staff decisions, approvals, and audit events.
Source and review matter
Patient-entered information should not silently become verified clinical truth. Imported data should not lose its provenance. Automation should not overwrite a clinician’s or authorized staff member’s decision without a visible review path.
Dental Studio is designed around explicit states such as submitted, imported, reviewed, corrected, superseded, and archived. The record should preserve both the current view and the evidence needed to understand how it changed.
Role-specific views, one underlying lifecycle
Front-desk, clinical, billing, and administrative users do not need the same screen or authority. They do need a coherent patient state. The intended model gives each role a focused workspace while enforcing access and actions on the same governed record.
Records connect the other modules
Patient intake creates reviewed inputs. Insurance and billing attaches coverage, claim, remittance, and balance events. Pharmacy delivery coordination records authorized fulfillment and delivery events. The patient record provides the durable context between them.