Healthcare
Patient intake forms collect demographics, insurance details, medical history, and consent signatures. Every facility uses its own layout. Sensible converts intake form data into structured JSON for EHR integration, insurance verification, and patient onboarding automation.
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






Every facility designs its own intake form, handwriting fills the margins, and medical-history checklists run long. We read the handwritten and printed fields and structure the history against your schema.
01
Every clinic designs intake forms differently: field ordering, section layout, page count all vary. The extraction adapts to each facility's form while outputting a consistent patient record schema.
02
Patients fill forms by hand, and handwriting varies enormously. LLM parsing interprets the content; confidence scores flag uncertain fields so your intake staff reviews only what needs review, not every form.
03
Conditions, medications, allergies: medical history sections capture these through checkboxes, yes/no fields, or free text. Each item is captured regardless of the input method the form uses.
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
Every intake form is different, so we build the config around your exact schema rather than a fixed list. These are the fields front-office teams request most; we map whatever else your EHR schema needs.
01
Demographics
Patient name, date of birth, gender, address, phone, email, SSN (masked), emergency contact name/phone/relationship
02
Insurance
Primary insurance carrier, group number, member ID, policyholder name, policyholder DOB, secondary insurance, employer name
03
Medical history
Current medications, allergies, surgical history, chronic conditions, family history, current symptoms, primary care physician
config.json
SenseML
{ /* SenseML: patient intake form extraction */
"fields": [
{
"method": {
"id": "queryGroup",
"queries": [
{ "id": "patient_name", "description": "patient name, full name, first name last name" },
{ "id": "date_of_birth", "description": "date of birth, DOB, birth date" },
{ "id": "member_id", "description": "member ID, insurance ID, subscriber ID, policy number" },
{ "id": "allergies", "description": "allergies, drug allergies, known allergies, allergy list" }
// + more fields, mapped to your schema
]
}
}
]
}Sensible processes intake forms from any healthcare facility. The hybrid approach handles handwritten content, printed text, and checkbox grids, all validated against your patient record schema.
Hospitals, primary care clinics, urgent care centers, dental offices, behavioral health practices, specialty clinics
Registration/demographics, insurance verification, medical history, medication reconciliation, consent/HIPAA authorization
Answers about facility form support, handwriting recognition, and EHR integration.
Patient name, date of birth, address, phone, email, emergency contact, employer, and preferred pharmacy are pulled from standard intake forms by default. Intake forms differ by practice, so these are examples rather than a fixed list. The demographic fields are defined in configuration and shaped to your form.
Sensible detects checked and unchecked boxes in medical history grids, symptom checklists, and consent forms. Each checkbox field is returned with a boolean value.
Yes. Sensible uses LLM-based parsing for handwritten content. Confidence signals indicate extraction certainty on each field, and low-confidence fields are flagged for human review.
Yes. Insurance company, policy number, group number, subscriber name, subscriber DOB, and relationship to patient come back from the insurance section. If your intake form carries insurance fields beyond these, the configuration is extended to capture them. You extract whatever you define.
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.