How do I choose a development partner for a health-tech product?
Judge them on what your hospital buyers will judge you on. Ask for an EHR integration they have shipped, over FHIR, HL7 v2 or a service such as Redox, and how they test it before it touches live data. Ask how a clinical draft stays a draft until a clinician signs, and how they rerun their evaluation sets when a model or prompt changes. Ask what evidence they can hand a hospital's security reviewer, from the audit trail to the agreements for each service that touches patient data, and whether the architecture will still let you release quickly once integrations and compliance pile up. Finally, check that code, prompts and data sit in your own accounts. Unthinkable has shipped health products such as Mount Sinai's STEMI coordination app, a practice-management system for a UK clinic chain and AliveCor's EKG apps, and it also helps hospitals and clinics run, so it knows the questions your buyers will ask.
I am a doctor with a product idea. Can you build it without me hiring a tech team?
Yes. You bring the clinical problem; we bring the complete product team: product designer, AI engineer, architect, developers, testers and a senior lead. We start with a short paid discovery that turns your idea into a scoped first release, a clickable design and a fixed price. You own the code, IP and data from the first line, and we stay until the product works in production with real clinicians.
Can you work with Epic?
Yes. We integrate through Epic's FHIR APIs and SMART on FHIR launch, and use HL7 v2 interfaces where a hospital's setup needs them. We build and test in Epic's sandbox first, then work with the hospital's integration team for production access. Timelines depend on the health system's own review process, so we plan for that from the start rather than treating it as a final step.
Is it HIPAA compliant to use large language models with patient data?
It can be, if every service that touches PHI signs a BAA and the data flow is controlled. We use model providers that offer a BAA, send only the minimum data needed, redact where possible, keep logs of every access and host within your cloud account when required. HIPAA compliance is a property of the whole system and your processes, so we document the chain for your compliance review.
How do you make sure a clinical AI feature does not give wrong answers?
We do not rely on the model alone. Rules and code handle anything with a fixed answer, such as thresholds or eligibility. The model drafts, cites the record it used and states its confidence, and a clinician approves anything that affects care. Before release we test against cases your clinicians write and grade, and we rerun those tests every time the model or prompts change.
How much does it cost to build a healthcare AI product?
It depends mostly on integrations and compliance scope: EHR integration and clinical evaluation are often the largest items, not the AI itself. A first release is usually one fixed outcome, and you get a scoped estimate after a short discovery. Unthinkable reuses tested building blocks for FHIR, audit and review queues, so your budget goes to what is specific to your product.
Can you build a prior authorization or revenue cycle product?
Yes. These are good fits because the work mixes judgement and rules. An agent gathers chart evidence and drafts the request; payer rules, code checks and submission logic run as code; a coordinator approves before anything is sent. Every step is logged so you can show payers and auditors what was submitted and why. We integrate with EHRs, clearinghouses and payer portals where APIs allow.
Can our product meet GDPR and UK rules as well as HIPAA?
Yes, if it is designed for each market from the start. For the UK and Europe that means a lawful basis for processing health data, hosting in the right region, data processing agreements with every provider and a data protection impact assessment before launch. Unthinkable designs the data flows so one product can meet HIPAA and GDPR together, and documents them for your compliance team and data protection officer.