The pre-visit history — shipped inside FormWorks and the patient portal.
Clinical · Full PHI · Every specialtyThis ships as a mode of FormWorks rather than as an app of its own, because almost all of it was already there: the forms engine has had branching questions, red flags with severities and an acknowledgement permission, and final-once-submitted submissions since the beginning. What was added is the record of a form ASKED of a patient before a visit, the patient answering it on their own portal link, and a history drafted from their answers for the clinician to edit. Accepting the draft creates a DRAFT note they sign themselves.
It does not write into the chart by itself: accepting a draft creates an unsigned note, and the signature is the clinician’s own act on their own screen.
Every app page carries this section. A listing with only benefits is an advertisement.IntakeTalk reads the intake form the clinic asked for, the patient’s own answers and writes submissions, red-flag events, a draft note the clinician signs. Its data class is Full PHI. Every app works on the same patient record — nothing is copied into a silo.
It does not write into the chart by itself: accepting a draft creates an unsigned note, and the signature is the clinician’s own act on their own screen.
Every record stays; only the workflow leaves.
IntakeTalk is in design: the surface exists and the platform underneath is ready. Join the waitlist and it moves up the build order.
Tell us what you run and we will show you this app inside a practice shaped like yours — or answer the question the page above did not.