Launch telehealth and patient platforms on HIPAA-ready services

Use one SDK to build a telehealth service or a patient portal, with Conjoin services for sign-in, patient records, messaging, billing, and AI that each apply HIPAA safeguards to patient data.

Get early access Explore the platform

A patient platform needs HIPAA controls before its first patient

HIPAA requires the company behind a patient platform to put access controls and audit controls on every system that contains protected health information, and to sign a business associate agreement with each vendor that stores or sends that information for it. Conjoin builds those controls into Auth, Database, Storage, Messaging, and AI. And because one business associate agreement covers every Conjoin service that your platform uses, your compliance reviewer can focus on the clinical code that your team writes.

One telehealth visit, service by service

During one telehealth visit, a different Conjoin service does the work behind each step that the patient takes, from signing in to paying the copay.

Sign patients, providers, and staff in under separate roles

Patients, providers, and billing staff sign in through Conjoin Auth, which connects to a hospital's directory over SAML or OIDC so that staff can use the accounts that they already have. Auth also asks each user for the second factor that your MFA policy requires. Your code then checks every request against the roles that you define in Auth, so a patient can open only their own records, a provider can open the records of their assigned patients, and billing staff can open only the billing records.

Outcome

The patient portal, the provider dashboard, and the admin console all check access against the same roles in Auth.

Store records and files in the region that you choose

Conjoin Database stores clinical records, visit notes, and treatment plans with field-level encryption on the sensitive fields. Your app uploads lab reports, imaging files, and consent forms to a Conjoin Storage container in the region where patient data has to reside. When a patient downloads a result, Storage issues a signed URL that expires after the time that you set. With a lifecycle policy on that container, Storage moves older files to archive storage and deletes each one once the holding period that your jurisdiction requires ends.

Outcome

Conjoin writes an audit entry for every read and every write of a patient record.

Tell patients and providers about every new result

Conjoin Messaging sends appointment reminders, test result notices, and treatment plan updates, and logs the delivery of every message. When the lab posts a result or a patient replies, your backend publishes an event to a Conjoin Relay broadcast channel. Relay then pushes that event to every provider dashboard that subscribes to the channel. Before the visit, Conjoin AI turns the patient's intake form into a structured summary, which your platform stores with the patient record.

Outcome

A provider's dashboard shows a new lab result as soon as your backend publishes it.

Collect copays and payment plans

Conjoin Billing charges each copay and bills each payment plan on the schedule that you set. After each payment, Billing generates an itemized receipt, which Messaging sends to the patient with the updated balance. When a charge fails, Billing retries it on your dunning schedule and emails the patient at each retry. For insurance claims, write your practice's adjudication rules as code and deploy them to Conjoin Runtime, where the Conjoin SDK is already installed and authenticated.

Outcome

Your billing code works with one SDK for charges, receipts, and adjudication rules.

One BAA, one patient account, and fewer missed visits

The first two figures are Conjoin's own, while the third is from a systematic review of telephone and SMS reminders for hospital appointments.

One account

for each patient's results, bills, and messages

One BAA

covers every Conjoin service

29%

fewer missed hospital appointments with automated reminders, relative to the baseline rate

Sources: Hasvold and Wootton, 'Use of Telephone and SMS Reminders to Improve Attendance at Hospital Appointments: A Systematic Review,' Journal of Telemedicine and Telecare (2011).

HIPAA safeguards built into the services

Encryption, access checks, and audit logging are part of the services themselves, so your code can call Database or Storage directly.

MFA with backup codes

Auth issues every user who turns on MFA a set of backup codes, so a patient who loses their phone can still sign in and enroll a new factor.

Encrypted clinical data

Database encrypts the sensitive fields in each patient record, while Storage writes PHI files only to the region that you assign to each container.

Audited messaging

For every message that your platform sends to a patient, Messaging records the send time, the channel, and each delivery event, which your code can query by message ID.

Point-in-time recovery

You can restore a patient database to any second within its retention window, which defaults to 7 days and which you can set for each instance.

AI inside the same access controls

When Conjoin AI summarizes an intake form, it retrieves only the records that the requesting clinician's account can open in Storage and Database. Its policy firewall then redacts personal data from the prompt before Conjoin forwards the prompt to a third-party model.

Installment plans and itemized invoices

Billing splits a large balance into installments and issues an itemized PDF invoice for each one.

Patient products that you can build on Conjoin

A small therapy practice and a hospital can build different patient products on the same Conjoin services.

Telehealth for therapy and behavioral health

Patients sign up through Conjoin Auth with a magic link or a code by text message, while therapists sign in under a role that grants access only to their own caseload. Conjoin Database encrypts session notes and treatment plans field by field. For session recordings and consent forms, your app uses a Conjoin Storage container in the region that the practice chooses. Conjoin Messaging sends an appointment reminder 24 hours before each session and a summary after it. Conjoin Billing charges the copay after the session and tries a declined card again 1, 3, and 7 days later. Once a therapist finishes an intake call, Conjoin AI drafts a summary of the notes in the format of the patient record, which the therapist reviews before saving it to the record.

What this delivers

Under one BAA with Conjoin, the practice's developers write the scheduling and therapy features, while the Conjoin services encrypt the notes, log each read, and retry the copays.

Hospital patient portal

Hospital staff sign in through Conjoin Auth over SAML with the Active Directory accounts that they already use, so only patients register with an email address or a phone number. Conjoin Database stores bookings, lab results, and refill requests, which your queries return only to the clinicians assigned to each patient. An ingestion job copies lab reports and imaging files from the hospital's medical record system into Conjoin Storage, which serves each file to the patient through a signed link that expires. Conjoin Messaging sends reminders, result notices, and refill alerts on each patient's preferred channel and files each delivery confirmation under the patient record. Conjoin Billing collects copays and sends itemized statements through Messaging. Conjoin AI checks each incoming patient question against the hospital's clinical protocols and routes the urgent ones to the provider on duty.

What this delivers

A patient opens results, bills, and messages from one account. Behind that account, Conjoin logs every read of a record, so the hospital's auditors can trace each read to the staff member who makes it.

Build your next app on Conjoin

Conjoin will open with a free Build tier, while the pricing page already lists the launch prices for Pro and Business. If you tell us what you're building, we'll talk you through early access.

See pricing Get early access