Seven Short Walkthroughs

Installing VESPER Psychology takes a few minutes. Open the download, drag the app into Applications, and launch it. Here is every screen from there. First launch opens the setup screen. Three things: your name as it will appear on reports, your license key, and where case files will live. Enter the key from your trial email, and choose the folder on this computer where cases will live. There is no VESPER cloud for case files; that folder is the record. Setup is complete. This is the dashboard before the first case. Everything from setup lives under Settings. Practice information is what the report header and the attestation carry: your name, credentials, license, and practice. AI features are optional. Connect your own key here, or use the workspace without one. Names, dates, and identifiers are replaced with single-use tokens on this machine before any text is sent. Data and storage: where the workspace is on disk, and what is in it. The assessment library: the instruments the workspace knows, with their validity scales. And the privacy panel: what runs on this machine, and what leaves it, in what form. The workspace on disk has the shape you would expect: a folder per case, and shared folders for templates, writing samples, and forms. That is the install. Next: a case, start to finish.

Onboarding: from a referral to a case ready for testing. One sample case, no real person. A case starts from the referral. New Case opens the intake wizard: six short screens. Name and date of birth, save, and the case exists: a folder on disk and a card on the dashboard. Screen two is the referral. Browse to the referral letter and the fields fill from it: the referring party, the question, the legal context. You correct what it got wrong. Sixteen evaluation types. The type decides the report structure later. Demographics and family, then the presenting complaints in the examinee's own terms. Medical and substance use history, and recent events. Everything here becomes the case record. Complete the intake and the case record opens: background, referral, medical history, clinical history, each in its own view, each editable. Try to move to testing now and the gate holds: the extracted data has to be confirmed first. Nothing advances on its own. Records go into the case in folders you would recognise, on your own disk, in the workspace you chose at setup. Drop them in and they are listed with a category. Review Extracted Data opens the confirmation view. The ingestor reads what you uploaded and lays out what it found, section by section: demographics, referral questions, history. Nothing is accepted until you confirm it. Section by section, you mark what is right. With the intake confirmed, the case moves to testing. Notes travel with the case from here on: identity and living situation, legal framing, record gaps, collateral planning. That is onboarding. Next: testing.

Testing: instruments, scores, and what the workspace does with them. One sample case, no real person. Instruments live in the assessment library, each with its scales and validity indicators. Search by name or filter by category. Each case has a battery. The suggested battery follows the evaluation type; what is ordered, what is completed, and what is still pending sit in one table. Order Measures adds an instrument from the catalog. Defaults for the evaluation type are already in. Drop the publisher's score report onto the case. It reads the instrument, the administration date, and the scale values, and the row fills in. It does not score answer sheets. Review on a row opens the report it came from, so the number and its source stay together. Test Results is the stored record: what was administered, when, how many scales, and validity cutoffs checked against the values entered. Arithmetic, not interpretation; the interpretation is yours. Each instrument has its own page, scale by scale, with the values as entered. Testing notes sit beside the data: battery selection, validity and effort, observations during testing. When the battery is in, the case moves on to interviews. That is testing. Next: interviews.

Interviews: record, transcribe on this machine, and take notes. One sample case, no real person. Interviews: each session is a row in the case, whether you recorded it, imported it, or typed it. Add a session and press record. Transcription runs on this computer, offline, and the words arrive as they are spoken. The audio does not leave the machine. Stop, and the transcript is in the record, timestamped. Or import a transcript you already have: VTT, PDF, Word, or text. Each file becomes a session. Or type. A manual session is a session like any other. Notes are categorised so the report can find them later: mental status observations, interview content, collateral planning. Until the interview stage is done, the report sections that depend on it stay pending and say so: behavioral observations and clinical interview findings. When the interviews are in, the case moves to diagnostics. That is interviewing. Next: diagnostics.

Diagnostics. The clinician decides every item. One sample case, no real person. Diagnostics. The rule first: the software never diagnoses. Each consideration is evidence laid out for you, and each gets your decision: render, defer, or reject. Open a consideration and the criteria summary is there, with what supports it, what contradicts it, and the onset and course. Evidence presented, never a conclusion. Severity and course specifiers are yours to set. Render the one the evidence supports. Reject the one the record does not support. Its formulation slot switches to Rule Out. There is no accept-all. Defer what needs more record. Every item gets a decision before the report can be built. Your clinical notes on each condition sit beside it, with the basis for what you rendered or ruled out. A formulation template can start them. The final formulation is rebuilt from your decisions and notes: impressions, conditions ruled out, response style and validity, prognosis. Approve each section. Your formulation is the authoritative narrative. Working notes, open questions, and reminders travel to the report stage. The evidence map shows which finding rests on which instrument, with its validity indicators and your decision. Attest that these decisions reflect your independent clinical judgment. Three gates, all yours; then the report can be built. Approve and build. The decisions are saved to the record and the draft is assembled. That is diagnostics. Next: the report.

The report: assembled from what you confirmed, reviewed, signed, and sealed. One sample case, no real person. The report is built from the approved formulation, once every consideration is decided and you have attested. Approve and build. Every section arrives marked draft, clinician review required, with the sources it was assembled from and a confidence figure where it is low. Nothing here is final until you have read it. The sections follow the evaluation type. Jump to any of them from the rail. Generate the Word document, then export it, or a PDF, onto your own disk. An editor pass reviews the draft and flags what it finds, by severity, section by section. It never edits your text; you dismiss or act on each flag. The consistency checks count down as you work; they gate completion. Before you attest: six checks the record has to satisfy. Testing, interviews, decisions, the reviewed draft. Sign with your name and credentials. The attestation is recorded with an integrity hash. Then Complete: sign and publish. The report locks, its hash is fixed, and the court packages open up. For court: a discovery package of the record, exported as one archive, and a testimony package. Every action in the case is in the audit trail, each entry hashed with the one before. Verify it in one click. You decide, you sign, and the workspace can prove nothing changed. That is the report. Ten-day trial at vesperpsych.com.