Extract patient intake forms to structured JSON
Patient intake forms collect demographics, insurance details, medical history, and consent signatures. Every facility uses its own layout. Sensible extracts intake form data into validated JSON for EHR integration, insurance verification, and patient onboarding automation.
Why patient intake forms confuse standard parsers
Custom facility layouts, mixed handwriting, and checkbox-heavy medical history sections resist OCR.
Every clinic designs its own intake forms with different field ordering. Sensible adapts to any layout using LLM reasoning and SenseML.
Patients fill forms by hand. Sensible interprets handwriting and validation cross-checks values against expected formats.
Intake forms list conditions, medications, and allergies with checkboxes or yes/no fields. Sensible maps checked items to structured arrays.
Fields we extract
Extract any data you need from patient intake forms into your desired output schema
Patient name, date of birth, gender, address, phone, email, SSN (masked), emergency contact name/phone/relationship
Primary insurance carrier, group number, member ID, policyholder name, policyholder DOB, secondary insurance, employer name
Current medications, allergies, surgical history, chronic conditions, family history, current symptoms, primary care physician
Patient consent for release of protected health information.
Patient demographics, emergency contacts, and insurance information form.
Patient-completed form covering medications, allergies, surgeries, and family history.
Supported intake form types
Sensible processes intake forms from any healthcare facility, many available in our healthcare template library. Custom facility configurations build in hours.
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
Common Questions
Details on Sensible intake form extraction.
Sensible extracts patient name, date of birth, address, phone, email, emergency contact, employer, and preferred pharmacy from standard intake forms.
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 scores indicate extraction certainty on each field, and low-confidence fields are flagged for human review.
Yes. Sensible captures insurance company, policy number, group number, subscriber name, subscriber DOB, and relationship to patient from the insurance section of intake forms.
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.
Documents are deleted after 30 days by default. You can configure shorter retention periods or request immediate deletion via API.
Yes. Sensible offers a free tier with 50 documents per month. 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 PDF, PNG, JPG, and TIFF files. PDFs can be native or scanned.
Accuracy depends on document quality and configuration. Most production deployments achieve 95%+ accuracy with proper validation rules and confidence scoring.
Most documents process in 2 to 10 seconds depending on complexity and page count.