Health

Health · vertical overview

The Health vertical turns SellioCRM into the administrative system of a clinic, practice, lab or network: patient records, schedule, provider directory, eligibility, authorizations, service, recall and analytics. That is nine screens under the Health menu plus two external portals. It is administrative by design and is never a clinical chart. It stays off until an administrator enables it.

The Health vertical is optional. While it is off, nothing changes in your SellioCRM: the Health menu does not exist and no screen in the vertical responds. An administrator turns the vertical on in Settings, under Verticals. From then on the Health group appears in the side menu, with nine items.

💡 The gate is total. With the vertical off, the Health group disappears from the menu for everyone, administrators included. Enabling it is always done in Settings, under Verticals.

What the vertical is, and what it is not

The module is administrative from end to end. It handles who the patient is, when they are coming in, which plan covers them, whether the procedure was authorized, what they raised with patient services and how long it has been since they came back. It does not store clinical notes, diagnoses, prescriptions or reports. That boundary shows up in the interface itself: every screen states that the content is administrative, with no clinical information.

The reason is practical. A CRM that stores clinical information becomes a regulated system with a whole different class of obligations. By staying on the administrative side, the vertical solves what actually costs a clinic money day to day, an empty schedule, a claim denied for lack of authorization, a patient who vanished, without becoming a second chart alongside the one the clinic already uses.

Patients: administrative records, identifiers, consent, encrypted sensitive data and the Patient 360 view.
Schedule: slot generation, booking with a lock against double-booking, telehealth by link and a waitlist.
Directory: health organizations, providers and services. It is the catalog that feeds the schedule.
Service: patient requests, complaints, ombudsman cases and appeals, with a deadline, escalation and NPS.
Eligibility: the member's coverage and the eligibility check with the payer.
Authorizations: prior authorization for a procedure, from draft through appeal, with a deadline and an authorization number.
Communication: your organization's sending policy, with a quiet window, time zone and a daily cap per patient.
Recall: rules for bringing back patients who have not returned in a while, with a preview of how many are actually contactable.
Analytics: patient acquisition by channel and specialty, and referral conversion and leakage.

Privacy is not an afterthought

The vertical was built compliance first, and that shows up in four concrete places. First, the patient's sensitive data, identity document and legal guardian, is encrypted and is not shown on screen by default: there is a Reveal button, and revealing requires you to declare a purpose. Second, every read of that data is written to an access trail that cannot be edited or deleted, recording who read it, what they read, the purpose they declared and whether it was an emergency access.

Third, identifiers such as a national ID or a member number are stored blind: the system can look them up by exact match without keeping the number in the clear, and the screen never shows the value of the identifier, only which system it belongs to. Fourth, no message goes out without passing the consent check, and consent is verified at send time, not just in the interface.

The two external portals

Besides the internal screens, the vertical publishes two portals for people outside your organization. The Patient portal, at its own sign-in page, shows the patient their appointments and their communication preferences. The Provider portal shows a referring provider the referrals directed to them and their own schedule. Both are entered through a link sent by e-mail, with no password, and both are read-only.

Access is a list of authorized e-mail addresses, and it is checked on every request. Revoke an address and access drops immediately, even if the person already has the page open.

A typical day at the clinic

Example: Vida Plena Clinic, Tuesday. The front desk opens Directory and confirms that Dr. Helena Prado is on file with the service Cardiology consultation. In Schedule, they generate slots from 09:00 to 12:00 with a 30 minute duration, which creates six openings. The patient Marcos Bueno arrives, already on file under Patients, with consent granted for appointment reminders by SMS. In Eligibility, the front desk records his coverage with the payer and clicks Check. The result comes back as Authorization required, so the team opens an authorization under Authorizations for the procedure and follows it through to Approved, noting the authorization number. Marcos is booked. At the end of the month, Recall shows 84 patients who have not returned in more than 180 days, of whom 61 are contactable once the consent, quiet window and daily cap filters are applied.

Who can use it

Turning the vertical on or off is an administrator action, in Settings. Once it is on, the screens follow the normal permissions of your access role in the CRM: someone without permission on a resource still does not see that resource. Access to the patient's sensitive data is the most restricted point, because every read is logged with a name and a purpose.

Where to go next

Patients, sensitive data and consent: how to create a record without exposing an identifier and how the sending gate works.
Schedule, service and directory: how to generate slots, book, use the waitlist and handle ombudsman cases.
Eligibility and authorizations: how to record coverage, run a check and carry a prior authorization through to the end.
Recall and communication: how to set the quiet window, the daily cap and the reactivation rules.
Patient and provider portals: how to authorize an address, hand over the link and revoke access.

Open this article inside the system →