Staff portal per practice
Each practice gets its own portal at sunpeds.ai. Staff submit the work of the week from one place instead of by text, paper and hallway conversation.
Vyra Holdings LLC · Georgia
A holding company that operates healthcare practices and builds the software it runs on. Every company it owns reports into one command deck: VyraMAX.
01 — The company
Vyra Holdings LLC is a Georgia holding company, with registration in progress. It owns and operates healthcare practices, and it builds its own operating software rather than assembling one from disconnected tools.
The thesis is simple. An owner should not have to log into eleven systems to know how the week went. One deck, one roster, one queue, one record of who did what and when. The operating companies stay focused on patients and staff. The holding company keeps the ring around all of it.
02 — The platform
A private executive operating system for the holding company. One command deck across every company it owns, with the staff floor of each practice wired directly into it.
Built for the operator, not for sale. VyraMAX is private software; this page describes capability, not a product for purchase.
Each practice gets its own portal at sunpeds.ai. Staff submit the work of the week from one place instead of by text, paper and hallway conversation.
Every submission carries a name, a signature and a timestamp, and stays visible until it is closed. Nothing is finished because someone said it was finished.
Staff submit availability and weekly schedules through the portal. Coverage for every location lands in one queue instead of a chain of messages.
Periodic vaccine counts are entered by location, submitted with a signature and held in the queue until reviewed and closed.
Supply orders to McKesson and front-office ordering run through the same submission path, so requests, approvals and receipts sit on one thread.
Requests are filed by staff, routed to the owner queue, and answered in place. The decision and its date live with the request.
Facility and equipment issues become workorders with an owner, an age and a closing note, per location.
Opening and closing routines are checklists that are completed, signed and dated, so the day has a record rather than a memory.
How the practice works is written down, versioned and published to staff. Reading an SOP is recorded as an attestation against a person and a date.
One roster spans every company and location in the group, with roles that decide what each person can see and submit.
Staff see their practice and their work. Holding-company views, financials and cross-company data stay on the owner side of the wall.
Every submission from every location arrives in a single queue on the owner deck, aging visibly until it is closed.
03 — The closed loop
The design principle behind the whole platform. A staff submission appears in the owner operations queue the moment it is filed, and every status change flows back to the person who filed it in real time. Nothing goes into a void.
04 — Operating focus
Vyra Holdings operates Sun Pediatrics, a pediatric practice with four locations across metro Atlanta. The practice is where the platform earns its keep: schedules, vaccine counts, supply ordering, time-off, workorders and daily checklists all run through the staff portal and into the owner queue.
Healthcare is the first operating vertical, not the last. The same portal, roster and queue model is built to carry additional companies as the group grows.
Sun Pediatrics — four locations
Metro Atlanta, Georgia
05 — Integration path
The practice runs on eClinicalWorks, and the integration workstream is in progress rather than live. The path is FHIR first through the eClinicalWorks interfaces, with selective HL7 v2 messaging considered later only where FHIR does not reach. Until that work is complete, VyraMAX makes no claim to live clinical or claims feeds; what it holds today is the operational layer around the practice.