Roles and permissions
Every person gets their own login, and sees only what their role allows — four permission levels across 65 permission objects.
Sensitivity applies to encounters, not to the API.
Outpatient clinic management and electronic medical records
Clinical records and clinic operations for outpatient care.
A practical clinical-record and clinic-operations solution for outpatient care, implemented and supported on open-source OpenEMR.
Every person gets their own login, and sees only what their role allows — four permission levels across 65 permission objects.
Sensitivity applies to encounters, not to the API.
Every action is written to an audit trail, and an integrity report checks the trail has not been altered.
Integrity is verified with a hash, not an HMAC, and the rows are not chained. We do not describe the audit trail as immutable.
Build the clinical forms your clinic actually uses, without writing code.
No forms ship pre-configured; each is built for your clinic during implementation.
Change 491 settings, lists and layouts to match how your clinic works.
Billing generators are the exception — they cannot be added as modules.
Password rules are applied to every account, and enforced at sign-in.
This is an account-policy control. Nothing beyond that is implied by it.
Fifty-five built-in reports, with CSV and print output.
Ten reports are disabled together with their parent feature. This is reporting — there is no business-intelligence or dashboard layer.
Your data sits in an open, documented database — you can export it, and you can leave.
Export means CSV output and direct database access. It is not a migration service.
Configurable patient registration, with duplicate detection and record merge.
This is duplicate detection and merge, not a master patient index.
Appointment scheduling with recurring appointments and clinic holidays.
A live board showing where each patient is in today's visit.
It is an in-office board for staff, not a public-facing ticketing display.
Eighteen ready-to-use forms, including a full ophthalmology examination.
A further sixteen forms ship uninstalled and can be enabled during implementation.
Problems, allergies, medications and immunizations are kept as structured lists rather than free text.
Your clinicians maintain these lists. The system does not merge or reconcile entries on its own.
A clinician can sign a note, which locks the record against further edits.
This is an application-level control. We make no claim about its standing in law.
Two-factor authentication is available per user, voluntarily.
It is optional and per-user. It cannot be mandated for everyone by an administrator.
Ready-to-use forms, structured clinical lists, and e-signature with record locking.
Registration with duplicate detection, appointment scheduling, and a live patient-flow board.
Four permission levels across 65 permission objects, with per-person logins.
Audit trail with an integrity report, enforced password policy, and optional per-user two-factor authentication.
Fifty-five built-in reports with CSV and print output. Reporting, not analytics.
An open, documented database you can export from and leave.
What is active on day one, what needs configuration, and what ships switched off.