Healthcare
Healthcare organizations typically use VeroXM for the public-facing side of the practice - provider directories, service and condition pages, appointment-request copy - not for clinical or patient records, which belong in a system built and certified for that. This walkthrough sets up a Providers collection and a Services collection, and tests appointment-request copy.
Modeling a provider directory
| Field | Type | Notes |
|---|---|---|
| name | text | Provider's displayed name and credentials |
| bio | richtext | Professional bio |
| photo | media | |
| specialties | multi_enumeration | e.g. pediatrics, cardiology |
| services | relation | Points at entries in a Services collection |
| acceptingPatients | boolean | Drives an availability badge on the directory |
Rendering the directory
GET /collections/providers/content
?where[acceptingPatients]=true&where[specialties][in]=cardiologyTesting appointment-request copy
The call-to-action on a service page - how it frames booking an appointment - is a reasonable thing to test, since it is marketing copy, not clinical content. Duplicate the service entry, change the copy, and run it as an experiment; record a conversion when a visitor completes the appointment-request form:
Recording a request-submitted conversion
POST /public/v2/projects/:uuid/experiments/variants/:variantId/convertKeep patient data out of VeroXM
Content Experiments and the Content API are built for public, non-patient content. Do not store patient records, appointment details tied to an identified patient, or any other protected health information in VeroXM - keep that in your EHR or a system designed and configured for that data.