The patient portal in circleOS is best understood as a set of patient-facing links and pages.
Instead of one big staff-managed account area, your team usually shares focused links for one specific job:
- service booking links so a patient can book from a service page
- service-variant booking links so a patient can book one specific variant
- product-variant checkout links so a patient can open a checkout flow for a specific purchasable variant
- appointment links so a patient can open an existing booking
- forms links so a patient can complete anything that is currently required
- plan links so a patient can open an active plan
- document links so a patient can open a published document, such as a shared PDF
- diagnostic-result links so a patient can open a patient-facing diagnostic result route when your results-sharing flow supports it
In other words, the patient portal is the patient-facing side of work you already manage inside circleOS.
What patients can do
Depending on the link you send, patients can:
- book from a service or service-variant link
- open a checkout flow from some product-variant links
- open an existing appointment, and in some flows cancel it from the patient app
- complete required forms on their phone or computer
- open active plans, published documents, or published diagnostic results you have shared with them
What your team controls in circleOS
Your team still controls the workflow from inside circleOS:
- decide which booking, appointment, form, plan, document, or result link should be shared
- decide which forms are required
- send or copy patient-facing links from Copy share link → Copy Patient App URL on supported pages, or from the required-forms workflow
- activate plans and publish documents before sharing them
- review form submissions and appointment changes after the patient completes them
That means staff still decide what is ready to share and when it should be sent.
What to expect in day-to-day use
For most practices, the patient portal is not a separate setup project.
It is the patient-facing layer of the work you already do in circleOS:
- services and variants power booking flows
- some product variants can power direct checkout flows
- existing bookings power appointment-management links
- required forms power intake and consent flows
- active plans power patient plan links
- published documents and published diagnostic results power patient sharing
Use Copy share link → Copy Patient App URL from the action menu when a patient-facing URL is available. In practice, that is commonly exposed on service, service-variant, booking, active plan, published document, diagnostic-result, and product-variant detail pages. Product detail pages themselves do not currently expose a patient-facing link.
If Copy Patient App URL is disabled, that record is not ready to share from that page yet. Common reasons are that the document is not published yet, the plan is not active yet, or the page only supports an internal circleOS route.