Skip to main content

CareOS

CareOS is the set of building blocks for healthcare EHRs: the colours, type, spacing and 185 components that the CareOS screens are made of, from the schedule and the patient chart to claims, prior authorization, the patient portal, the phone app and the check-in kiosk.

It is for product teams that build EHR, practice management (PM), revenue cycle (RCM) and patient apps. A team that uses it does not design a patient banner, an allergy list, an ICD-10 picker, an ERA posting row or a break-the-glass dialog again; it composes screens from parts that already carry the clinical, billing and privacy rules.

Install​

npm install health-components

The package ships:

EntryWhat
health-componentsReact components with TypeScript types (ESM and CommonJS, tree-shakeable).
health-components/styles.cssTokens for all five themes plus every component style.
health-components/elementsThe same components as custom elements (<co-button>) for Angular, Vue, Svelte and plain HTML.
health-components/tokensEvery token as typed data, for charts, canvas or native code.
health-components/tokens.css, tokens.jsonTokens only.
health-components/fonts.cssOptional Roboto and Roboto Mono from Google Fonts.
health-components/cdn/careos-elements.jsOne script tag with every element and React bundled, for pages without a build step.

Three layers​

  1. Foundations. Tokens for colour in five themes (Classic, Clinical Sidebar, Focus Rail, Command Bar, Dark), type, spacing, radius, shadow, z-index and density. Every component reads them as CSS variables (--co-*), so a theme change needs no code change. See Foundations.
  2. Basic components. Generic controls with every variant, size and state: buttons, inputs, selection, badges, avatars, cards, table parts, feedback, overlays, navigation parts, charts, layout rows.
  3. Complex components. Healthcare parts built only from the basic ones: patient identity and clinical lists, medications and e-prescribing, orders and notes, revenue cycle, scheduling and visits, work queues, quality and care programs, access control and audit, app shells for desktop, phone and kiosk.

Use the highest layer that fits. Build a claim screen from ClaimForm, not from TextFields in a table.

Pick your framework​

  • React: import components, wrap the app in ThemeProvider.
  • Angular: register the custom elements once, use <co-*> tags in templates.
  • Vue and plain HTML: the same custom elements.
  • Next.js and SSR: the React components render on the server.

Explore​

  • Components: live examples in every theme, guidelines, props and the Web Component API.
  • Storybook: every component and state with interactive controls and accessibility checks.
  • Screen recipes: which components make up the common EHR screens.