Patient orders
Patients place and track orders, including guest orders for people who are not registered yet. Order history, status, and reorder paths stay in one account view, which takes pressure off support calls.
A patient portal is where orders, resupply, documents, and questions meet. We built one for a US DME network, including guest orders and communication preferences. A browser extension gives care teams patient context, clinical fields, and document management inside their existing workflow. Role-based access and audit logging sit underneath every screen.
One workflow can touch a referral, a supplier, a delivery team, a patient, a payer and an EMR. We work across the chain, or just the handoff that hurts.
Patients place and track orders, including guest orders for people who are not registered yet. Order history, status, and reorder paths stay in one account view, which takes pressure off support calls.
Patients see when a resupply is due, confirm what they still use, and send the request without a phone call. Care teams receive the request with the history they need to approve or adjust it.
Patients upload prescriptions, insurance cards, and signed forms from a phone or desktop. Care teams review the files in the same context as the order, and every document keeps a timestamped history.
Patients choose how the network reaches them and which messages they want to receive. Preferences follow the patient across orders, resupply, and support, so teams stop guessing which channel works.
A browser extension shows the patient record, clinical fields, and documents while staff work in the portal or another system. Teams see the same order and document state without switching tabs or rekeying details.
Every screen runs behind role-based access, and sensitive actions write to an audit log. We define who can see orders, documents, and clinical fields, then test those rules before launch and after each change.
Every step is a handoff. The software has to keep the state, the reason and the evidence together, or operations rebuilds the process in spreadsheets.
We trace orders, resupply, documents, and support calls from the patient side and the care team side.
Discovery · Workflow mapRoles, permissions, and audit requirements are written down before a single screen is built.
Security · RolesPatient screens and the care team extension are designed together, using real order and document data.
UX · PrototypesFront end, APIs, and integrations ship in short increments, with working screens to review each week.
Angular · React · APIsOrders, documents, and patient records connect through the interfaces your systems already expose.
Integrations · APIsAccess, audit, and workflow tests run with care teams before patients see the new portal.
QA · LaunchMost portals fail at the handoffs. An order lives in one tool, a document in an inbox, and a resupply request in a phone log. Patients see fragments, care teams rebuild context, and support volume grows. The portal has to hold the whole loop.
Order status sits in one system, documents in another, and notes in a third. Patients call to ask what happened. A portal that reads from each system gives one clear answer.
Phone-based resupply is slow, easy to miss, and hard to audit. Patients who are ready to reorder wait for a call, while care teams work through lists instead of exceptions.
Staff toggle between the portal and the clinical system, retyping details as they go. A browser extension that carries patient context into the workflow removes the copy and paste step.
Prescriptions and forms sent by email land in personal inboxes with no audit trail. Uploads tied to the order keep documents attached to the right patient and the right request.
Modules follow the workflow, not a product catalogue. Each one gets an owner, an integration boundary and a way to reconcile with the system of record.
Registration, login, guest orders, and profile details in one place.
Order status, history, and reorder paths for every order a patient places.
Resupply due dates, patient confirmation, and care team review in one request flow.
Upload, review, and timestamped history for prescriptions, insurance cards, and signed forms.
Channel, consent, and contact settings that follow the patient across every request.
Browser extension that shows patient context, clinical fields, and documents inside the care team workflow.
Representative healthcare work. Client names are under NDA; the workflows and numbers are what we can share.
Mitrix built a patient portal for a US DME network covering orders, resupply, documents, communication preferences, and guest orders. Care teams use a browser extension for patient context, clinical fields, and document management.
Read the DME caseThe resupply workflow connects due dates, patient confirmation, and care team review in one path. It cuts the phone tag that causes patients to drop off before a refill ships. Patients confirm what they still use before the request reaches the team.
Read the resupply articleWe work across patient portals, EMR integration, healthcare CRM, document AI, and analytics for healthcare teams. The same delivery team stays on the work from scoping through launch, with support after release.
Explore healthcare workBuying gets you a working portal quickly, with limits on workflow and integration. Building costs more upfront and fits your orders, resupply rules, and care team tools. We scope both paths against your systems before recommending one, and we can extend a purchased platform where it stops fitting.
Buy when standard order and document flows cover most patients and speed matters more than fit.
Build when resupply rules, guest orders, or care team context differ from what platforms offer.
Hybrid works when a platform handles accounts while custom work covers resupply and the extension.
Decide after an integration review, since the EMR and order systems set the real cost.
Existing platforms respected, new surfaces kept boring. The stack follows the integration and compliance constraints.
If yours is not here, send it. We answer in plain language, with the constraints we would check first.
A patient portal should let patients manage orders, resupply, documents, and communication preferences without calling support. It should also give care teams the context they need to act on those requests. For DME, that means guest orders and resupply confirmations alongside account login and a message inbox.
An EHR is the clinical record of care. A patient portal is the patient-facing layer that connects to it, handling orders, documents, and messages. The portal reads and writes through integrations, while the EHR remains the source for clinical data.
Yes. Patients see when a resupply is due, confirm what they still use, and submit the request. Care teams review it with order history and approve or adjust it. The workflow replaces phone tag and keeps a record of each request.
Access is role-based, and sensitive actions write to an audit log. We scope permissions for patients, care teams, and administrators, then test the rules before launch. Integrations use the authentication and transport your systems require, and we review access after each release.
The portal connects to order management, document storage, and patient records through the interfaces those systems expose. We map the available APIs and file feeds during discovery, then confirm what is real time and what runs on a schedule.
Buy if standard account, order, and document flows cover most of your patients and you need speed. Build if resupply rules, guest orders, or care team context are central to your model. A hybrid is common: a platform for accounts and custom work around it.
Tell us where the handoff breaks: intake, eligibility, delivery, reconciliation, billing or the patient experience.
AI Assistant