Trusted by teams turning documents into production data
Healthcare
Prescriptions arrive as handwritten pads, e-prescribing exports, refill faxes, and pharmacy printouts. Drug names, doses, and instructions sit in unstructured fields that pharmacy and EHR systems need to parse correctly. Sensible converts any prescription format into normalized JSON ready for medication reconciliation and adherence workflows.
Validated JSON
Schema-enforced output; every field matches your contract
Source coordinates
Every value links back to page + bounding box for audit
Per-document pricing
Predictable cost. No token-volatility surprises
Trusted by teams turning documents into production data
Prescriptions mix handwriting, abbreviated sig codes, and drug names that vary across systems. We pair OCR-tuned models with deterministic post-processing to turn them into normalized, validated medication data.
01
Sig codes like "1 tab PO BID PRN pain" need to expand to plain-language instructions for patient-facing systems. Confidence scores flag low-legibility scripts for pharmacist review before they reach the patient.
02
Brand names, generic names, and abbreviations all need to map to a consistent identifier. Sensible normalizes against RxNorm so downstream systems receive a stable drug code regardless of how the prescription was written.
03
Some prescriptions list four or five medications on one form. Each drug-dose-direction triplet gets extracted as a separate structured record so pharmacy systems can fill them independently.
Managed services
Solutions engineers handle plan, build, deploy, and adjust on your behalf. You see clean JSON in your API response. Same engine as self-serve, just with the configuration work outsourced.
What's included
01Plan.Engineers review your samples and pick the right method
02Build.SenseML configs written from your samples
03Deploy.Same engine as self-serve, ready for production
04Adjust.We update configs when formats shift or new edge cases appear
05Integrate.Help with custom integration into your downstream systems
We configure every prescription extraction to your exact schema, not a fixed field list. The fields below are the ones pharmacy teams pull most often — tell us what your pharmacy or EHR pipeline needs and we map the rest.
01
Patient and prescriber
Patient name, date of birth, prescriber name, NPI, DEA number, prescription date, pharmacy
02
Medication
Drug name (brand and generic), dose, route, form, quantity, days supply, RxNorm code
03
Directions and refills
Sig expanded text, refills authorized, refills remaining, indication, substitution permitted
config.json
SenseML
{ /* SenseML: prescription extraction */
"fields": [
{
"method": {
"id": "queryGroup",
"queries": [
{ "id": "drug_name", "description": "drug name, medication, RX" },
{ "id": "quantity", "description": "quantity, dispense quantity" },
{ "id": "sig", "description": "directions, sig, instructions" },
{ "id": "refills", "description": "refills, refills authorized" }
// + more fields, mapped to your schema
]
}
}
]
}Sensible processes prescriptions from any source, with pre-built configurations for common e-prescribing systems.
Surescripts NCPDP, Epic MyChart prescriptions, Cerner e-RX, Allscripts, athenaClinicals — pre-built configurations match each format.
Traditional pads, fax-received prescriptions, and scanned legacy forms. OCR-tuned models with pharmacist-review confidence thresholds.
Answers about handwritten scripts, RxNorm normalization, and multi-drug prescriptions.
Yes. Each drug-dose-direction triplet on the prescription gets extracted as a separate structured record. Pharmacy systems can fill, refill, and track each medication independently.
Yes. Brand names, generic names, and abbreviations get mapped to RxNorm codes so downstream pharmacy and EHR systems receive a stable identifier regardless of how the prescription was written.
OCR-tuned models extract drug, dose, and sig from handwritten scripts. Per-field confidence scores flag low-legibility prescriptions so pharmacists can review uncertain extractions before they reach patient-facing systems.
Prescriptions from any source. Pre-built configurations cover the major e-prescribing systems, including Surescripts NCPDP, Epic, Cerner, Allscripts, and athenaClinicals. Handwritten or faxed scripts, and any e-prescribing format not listed here, get configured in SenseML.
Yes. Sensible sends extraction results to your webhook endpoint when processing completes. You can also poll the API for status.
Yes. Sensible flags extractions with low confidence for human review. You can configure review thresholds and workflows.
Sensible is SOC 2 Type II certified and HIPAA compliant. Data is encrypted in transit and at rest.
Document data is stored indefinitely by default. Custom retention policies are available and can be configured for same-day deletion if needed.
Yes. Sensible offers a 14-day free trial on the Growth plan. No credit card required to start.
Sensible uses per-document pricing for predictable costs. No token-based billing or usage surprises. Volume discounts are available for higher throughput.
Sensible provides REST APIs and SDKs for Python and Node.js. Most integrations take a few hours. Webhooks, Zapier, and direct API calls are all supported.
Sensible processes PDFs (native or scanned), Microsoft Word (DOC, DOCX), spreadsheets (XLSX, XLS, CSV), single-page images (JPEG, PNG), multi-page images (TIFF), and email bodies with attachments.
Accuracy depends on document quality and configuration. Most production deployments achieve 95%+ accuracy with proper validation rules and confidence signals.
Processing speed depends on document size, page count, OCR requirements, and which extraction methods are used. Simple single-page documents process in seconds. Larger or more complex documents that use LLM-based extraction take longer.
Start free
Free 14-day trial. No credit card required. Start extracting in minutes.