GitoCare runs on one open, FHIR-native API, so the tools you already use plug in behind the same port. Bring your own login, bridge your own Slack or Teams, connect your BI tool, and export everything in one call. Your data stays yours.
Live built into the product today. Roadmap designed and on the way. Some payment, clearinghouse, and fax rails run in a secure sandbox until your go-live.
We already verify Google sign-in in production. The same OIDC connector covers Microsoft Entra and Okta, so you configure it once in Admin. The one-click Sign in with your company button on the login screen activates with your identity provider.
Sign in with your Google Workspace identity over OIDC. This is the connector we run in production today.
Company SSO against your Entra directory. Set your issuer and allowed email domain in Admin.
Bring your Okta org as the single sign-on for your whole team, over standard OIDC.
For accounts not on company SSO, a built-in authenticator-app second step, with admin reset and recovery codes.
For identity providers that speak SAML instead of OIDC.
Auto-provision and deprovision staff from your directory.
Built-in messaging and tasks with group channels and group task assignment, plus smart audiences that reach a whole department. Already live in Teams or Slack? Bridge GitoCare notifications straight into your channel instead.
Message a teammate or a whole group, then turn any message into a task assigned to a person or a team. No copy and paste into a second app, no dropped handoffs.
Ava Bennett's auth expires Friday. Can someone re-verify? @Billing
On it.
Person and group channels, Slack-style @mentions, and tasks you assign to a person, a team, or a whole group.
Message or assign a task to a department across one or more clinics. It resolves to the right people as your team changes.
Bridge notifications, like a new task or a team broadcast, into your Teams channel. No patient details ever leave.
The same outbound bridge into your Slack channel, PHI-minimal by design.
Reply from Slack or Teams and have it post back into GitoCare.
Staff build their own communication groups from the directory, scaling to hundreds of employees.
Every record is standard HL7 FHIR on a foundation you can read, write, and export in a single call. Point your own BI tool at it, or migrate away whenever you like.
Every record is standard HL7 FHIR, read and written over one clean, JSON-native API.
Point Power BI, Tableau, or any tool at the open API to build the dashboards your practice wants.
Export your entire dataset in a single call. Leaving is as easy as arriving, so you are never locked in.
Payments settle to your own bank, benefits and claims run through a national clearinghouse, and paper still moves by fax when it has to.
Card, tap, and patient balances settle through Stripe into your own bank account, never held by us.
Real-time benefit checks and electronic claim submission through a national clearinghouse.
Inbound and outbound fax, API-first, for the referrals and records that still move on paper.
Auto-post payments straight from electronic remittance advice.
The public datasets a practice needs are wired in and kept fresh, so nobody free-types a code or an NPI.
Providers are resolved and NPI-deduped from the national registry, never free-typed.
Live diagnosis and procedure code lookups from the national library.
CARC, RARC, place-of-service, and taxonomy references served with source and freshness.
Because everything is API-first, adding one more system is a connector, not a project. Tell us what you already use and we will map the fit.