{"id":41,"date":"2026-10-18T07:36:48","date_gmt":"2026-10-18T07:36:48","guid":{"rendered":"https:\/\/7dayscare.com\/?page_id=41"},"modified":"2026-10-18T07:42:24","modified_gmt":"2026-10-18T07:42:24","slug":"for-companies","status":"publish","type":"page","link":"https:\/\/7dayscare.com\/index.php\/for-companies\/","title":{"rendered":"For Companies"},"content":{"rendered":"\t\t<div data-elementor-type=\"wp-page\" data-elementor-id=\"41\" class=\"elementor elementor-41\">\n\t\t\t\t<div class=\"elementor-element elementor-element-a4cf247 e-flex e-con-boxed e-con e-parent\" data-id=\"a4cf247\" data-element_type=\"container\" data-e-type=\"container\">\n\t\t\t\t\t<div class=\"e-con-inner\">\n\t\t\t\t<div class=\"elementor-element elementor-element-5752c22 elementor-widget__width-inherit elementor-widget elementor-widget-html\" data-id=\"5752c22\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"html.default\">\n\t\t\t\t\t<section class=\"sdc-hero\">\r\n  <div class=\"sdc-wrap sdc-hero-grid\">\r\n    <div>\r\n      <p class=\"sdc-eyebrow\">For clinics, groups and organisations<\/p>\r\n      <h1>Your own <span class=\"sdc-tone-mint\">instance<\/span>. Your servers,\r\n        your data, <span class=\"sdc-grad-text\">your upgrade schedule<\/span>.<\/h1>\r\n      <p class=\"sdc-hero-lede\">A full <strong>ERP, CRM and EHR<\/strong> in one database, on infrastructure\r\n        you choose &#8212; plus <strong>custom development<\/strong> that turns your own way of\r\n        working into part of the product, and leaves you owning it. Built on open-source Odoo\r\n        Community, so there is no licence fee and no charge per user, ever.<\/p>\r\n      <div class=\"sdc-hero-actions\">\r\n        <a class=\"sdc-btn sdc-btn--primary\" href=\"\/pricing\/\">Open the price calculator<\/a>\r\n        <a class=\"sdc-btn sdc-btn--ghost sdc-on-dark\" href=\"#case\">Work out your own case<\/a>\r\n      <\/div>\r\n    <\/div>\r\n    <div class=\"sdc-doors\">\r\n      <a class=\"sdc-door\" href=\"#whole\">\r\n        <span class=\"sdc-door-number\">01<\/span>\r\n        <span><b>ERP, CRM and EHR &#8212; plus the part nobody sells<\/b>\r\n          <span class=\"sdc-door-sub\">One system instead of five, and custom work you end up owning.<\/span><\/span>\r\n        <span class=\"sdc-door-go\">&#8594;<\/span>\r\n      <\/a>\r\n      <a class=\"sdc-door\" href=\"#why\">\r\n        <span class=\"sdc-door-number\">02<\/span>\r\n        <span><b>Revenue that is already yours<\/b>\r\n          <span class=\"sdc-door-sub\">Not new business &#8212; money your process loses on the way through.<\/span><\/span>\r\n        <span class=\"sdc-door-go\">&#8594;<\/span>\r\n      <\/a>\r\n      <a class=\"sdc-door\" href=\"#ahead\">\r\n        <span class=\"sdc-door-number\">03<\/span>\r\n        <span><b>Moves your competitors cannot make<\/b>\r\n          <span class=\"sdc-door-sub\">Because their licence, their vendor or their data model stops them.<\/span><\/span>\r\n        <span class=\"sdc-door-go\">&#8594;<\/span>\r\n      <\/a>\r\n    <\/div>\r\n  <\/div>\r\n<\/section>\r\n\r\n<div class=\"sdc-trust\">\r\n  <div class=\"sdc-wrap sdc-trust-inner\">\r\n    <span><b>&#10003;<\/b> No licence fee, no per-user charge<\/span>\r\n    <span><b>&#10003;<\/b> Your database, never shared with another organisation<\/span>\r\n    <span><b>&#10003;<\/b> Self-hosted or hosted by us &#8212; and you can move<\/span>\r\n    <span><b>&#10003;<\/b> An isolated architecture where the duty is heavier<\/span>\r\n  <\/div>\r\n<\/div>\r\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t<div class=\"elementor-element elementor-element-8695f5e e-con-full e-flex e-con e-parent\" data-id=\"8695f5e\" data-element_type=\"container\" data-e-type=\"container\">\n\t\t\t\t<div class=\"elementor-element elementor-element-1dc59be elementor-widget elementor-widget-html\" data-id=\"1dc59be\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"html.default\">\n\t\t\t\t\t<!-- =========================================================== whole -->\r\n<section class=\"sdc-band sdc-band--subtle\" id=\"whole\">\r\n  <div class=\"sdc-wrap\">\r\n    <p class=\"sdc-eyebrow sdc-center\">What you are actually buying<\/p>\r\n    <h2 class=\"sdc-section-title sdc-center\">An EHR is one of ten areas. The ERP and the CRM are the\r\n      other nine &#8212; and then there is the part that is not a product at all<\/h2>\r\n    <p class=\"sdc-section-lede sdc-center\">A record system keeps the clinical record. It does not run the\r\n      rota, pay the practitioners, chase the referrer, raise the invoice, or report on any of it.\r\n      So a clinic buys a record system, then buys four more things, then pays somebody to keep\r\n      the five in agreement. <strong>This is one system, on one database<\/strong>, and it arrives\r\n      as all three.<\/p>\r\n\r\n    <div class=\"sdc-system-grid\">\r\n      <article class=\"sdc-system\">\r\n        <p class=\"sdc-system-tag\">ERP<\/p>\r\n        <h3>The business that runs the care<\/h3>\r\n        <p>Odoo 19 Community underneath, with no licence fee and no per-user charge.<\/p>\r\n        <ul>\r\n          <li>Rota, rooms and resources<\/li>\r\n          <li>Orders, invoicing, payments and accounting<\/li>\r\n          <li>Practitioner pay on four formulas, with contract version timelines<\/li>\r\n          <li>Payout runs that write real supplier bills<\/li>\r\n          <li>HR, time off, expenses, procurement and inventory<\/li>\r\n          <li>Governance, training and workforce designations<\/li>\r\n        <\/ul>\r\n      <\/article>\r\n      <article class=\"sdc-system\">\r\n        <p class=\"sdc-system-tag\">CRM<\/p>\r\n        <h3>Everything before somebody is a patient<\/h3>\r\n        <p>The half of the funnel a record system has no model for.<\/p>\r\n        <ul>\r\n          <li>Referrer and partner register<\/li>\r\n          <li>Enquiry capture with a clock on it<\/li>\r\n          <li>Website, content, campaigns and newsletters<\/li>\r\n          <li>Events, courses and certificates<\/li>\r\n          <li>Attribution from first click to admitted patient<\/li>\r\n          <li>Booking funnel analytics &#8212; views, starts, drop-offs<\/li>\r\n        <\/ul>\r\n      <\/article>\r\n      <article class=\"sdc-system\">\r\n        <p class=\"sdc-system-tag\">EHR<\/p>\r\n        <h3>The clinical record, in full<\/h3>\r\n        <p>Encrypted per document and per field, with the keys held separately.<\/p>\r\n        <ul>\r\n          <li>Episodes from admission to discharge<\/li>\r\n          <li>Versioned treatment plans with nested goals<\/li>\r\n          <li>Template-driven notes with typed answers<\/li>\r\n          <li>Scored instruments charted over the episode<\/li>\r\n          <li>E-signature bound to the record it belongs to<\/li>\r\n          <li>Seven compliance packs, installed per market<\/li>\r\n        <\/ul>\r\n      <\/article>\r\n    <\/div>\r\n\r\n    <div class=\"sdc-plus\">\r\n      <div>\r\n        <p class=\"sdc-plus-sign\">&#43;<\/p>\r\n        <h3>Custom development &#8212; the thing on your paper, built into the product and\r\n          owned by you<\/h3>\r\n        <p>Every clinic has a way of working that no product has a page for. A triage rule nobody\r\n          else uses. A report the board asks for in a shape no vendor ships. A funding stream with\r\n          its own arithmetic. On a fixed product, that is a feature request. Here it is a module.<\/p>\r\n        <p>You get the source. The module sits in your repository, on your server, under your\r\n          upgrade schedule. <strong>If we stopped trading tomorrow, it would still run.<\/strong><\/p>\r\n      <\/div>\r\n      <ol class=\"sdc-plus-steps\">\r\n        <li>You describe it the way you actually do it &#8212; on paper, in a meeting, in the\r\n          spreadsheet you have been using instead.<\/li>\r\n        <li>We build it as a module on the platform, against the same models the rest of the\r\n          product uses. It is not a bolt-on beside your data; it is part of it.<\/li>\r\n        <li>It ships with your instance, and it is in the inventory with everything else &#8212;\r\n          tested, versioned, and visible under Apps like any other module.<\/li>\r\n        <li>You own it. Keep it private, or hand it to the next supplier. Neither needs our\r\n          permission.<\/li>\r\n      <\/ol>\r\n    <\/div>\r\n\r\n    <figure class=\"sdc-figure\">\r\n      <img decoding=\"async\" src=\"\/wp-content\/themes\/sevendayscare\/assets\/img\/diagram-paper-to-product.svg\" alt=\"Left: a hand-drawn sheet describing a clinic's own way of working, with a box labelled our way. An arrow across the middle reads built as a module on the product itself, leading to a running page of the product with a Save button, labelled yours, in your repository, on your server. Set apart on the right behind a dashed line: a fixed product drawn as a padlocked box labelled the roadmap, with five dots beneath it and the caption you are fifth in the queue.\">\r\n      <figcaption><b>The difference is not how fast somebody builds it.<\/b> It is who decides\r\n        whether it gets built, and who owns it afterwards.<\/figcaption>\r\n    <\/figure>\r\n\r\n    <div class=\"sdc-sourced\">\r\n      <p><strong>How unusual that is, stated carefully.<\/strong> Our own feature comparison puts\r\n        this platform against seventeen others &#8212; ten in the United States, seven in Europe.\r\n        On the row <em>custom development on the product, owned by the clinic<\/em>, exactly one of\r\n        those seventeen also has it: OpenEMR, which is self-hosted open source. The same is true\r\n        of <em>full source access<\/em>. For the other sixteen, the product is the product: you file\r\n        a request and you wait your turn behind everyone else who filed one.<\/p>\r\n      <p>That is the whole claim, and it is the shape of the claim we are willing to make. We are\r\n        not telling you our competitors are bad software &#8212; several are very good at the part\r\n        they do. We are telling you what happens the first time you need something they have not\r\n        decided to build.<\/p>\r\n      <cite>Source: <code>docs\/marketing\/08-COMBINED-FEATURE-MATRIX.md<\/code> &#167;6, rows O5 and\r\n        O10, across the eighteen-platform table. Marks are read conservatively: a partial or\r\n        higher-tier-only implementation counts in a competitor's favour.<\/cite>\r\n    <\/div>\r\n  <\/div>\r\n<\/section>\r\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t<div class=\"elementor-element elementor-element-97265b6 e-con-full e-flex e-con e-parent\" data-id=\"97265b6\" data-element_type=\"container\" data-e-type=\"container\">\n\t\t\t\t<div class=\"elementor-element elementor-element-47fdb30 elementor-widget elementor-widget-html\" data-id=\"47fdb30\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"html.default\">\n\t\t\t\t\t<!-- ============================================================= why -->\r\n<section class=\"sdc-band\" id=\"why\">\r\n  <div class=\"sdc-wrap\">\r\n    <p class=\"sdc-eyebrow sdc-center\">Why an organisation does this<\/p>\r\n    <h2 class=\"sdc-section-title sdc-center\">Four arguments, each one a mechanism and its consequence<\/h2>\r\n    <p class=\"sdc-section-lede sdc-center\">The <strong>mechanism<\/strong> is what the system actually\r\n      does. The <strong>consequence<\/strong> is the part you can check against your own week.\r\n      <strong>No percentage appears on this page<\/strong> &#8212; we have none that are sourced, and\r\n      \u00a7<a href=\"#case\">Work out your own case<\/a> gives you the arithmetic instead.<\/p>\r\n\r\n    <div class=\"sdc-module-grid\">\r\n      <article class=\"sdc-module-card\">\r\n        <div class=\"sdc-module-card-top\"><h3>Efficiency &#8212; the work that stops existing<\/h3><\/div>\r\n        <p class=\"sdc-plan-for\">Most clinics run four systems: a booking tool, a clinical record, an\r\n          accounting package and a marketing list. The cost is not the four subscriptions. It is\r\n          the people who carry data between them, and the disagreements when they miss something.<\/p>\r\n        <ul class=\"sdc-module-features\">\r\n          <li><strong>One database carries the clinical record, the schedule and the invoice<\/strong> &#8212; the invoice and the booking are the same data, so nobody reconciles them<\/li>\r\n          <li><strong>Reports are built from the data you already enter<\/strong> &#8212; the reporting round stops being an assembly job from four exports<\/li>\r\n          <li><strong>Payout runs produce real supplier bills in the accounts<\/strong> &#8212; no spreadsheet handed to the bank, and no re-keying of it<\/li>\r\n          <li><strong>Roles are configuration<\/strong> &#8212; adding reception, supervision, quality or a case worker is a permission, not a project<\/li>\r\n          <li><strong>A new brand or a second site is a configuration choice<\/strong>, not a new project<\/li>\r\n        <\/ul>\r\n      <\/article>\r\n\r\n      <article class=\"sdc-module-card\">\r\n        <div class=\"sdc-module-card-top\"><h3>Revenue &#8212; money that is already yours<\/h3><\/div>\r\n        <p class=\"sdc-plan-for\">None of this is new business. It is revenue your current process\r\n          loses on the way through.<\/p>\r\n        <ul class=\"sdc-module-features\">\r\n          <li><strong>Cancellation policy with tiered penalties, applied automatically<\/strong> &#8212; late cancellations and no-shows currently written off because nobody chased them<\/li>\r\n          <li><strong>&#8220;Not yet booked&#8221;<\/strong> &#8212; sessions bought but unscheduled, shown as a list. The single most overlooked number in a clinic<\/li>\r\n          <li><strong>Recalls<\/strong> &#8212; repeat episodes that currently depend on somebody remembering<\/li>\r\n          <li><strong>Enquiry capture with a clock on it<\/strong> &#8212; enquiries that die in a shared inbox over a weekend<\/li>\r\n          <li><strong>Attribution from first click to admitted patient<\/strong> &#8212; which channel produces <em>patients<\/em>, not clicks, so spend moves to what works<\/li>\r\n          <li><strong>Four figures that always agree<\/strong> &#8212; sessions bought, going to earn, earned, not yet booked<\/li>\r\n        <\/ul>\r\n      <\/article>\r\n\r\n      <article class=\"sdc-module-card\">\r\n        <div class=\"sdc-module-card-top\"><h3>Performance &#8212; knowing, fairly<\/h3><\/div>\r\n        <p class=\"sdc-plan-for\">The platform answers a question most reporting products do not:\r\n          <strong>is the record true?<\/strong> &#8212; not only <em>how are we doing?<\/em><\/p>\r\n        <ul class=\"sdc-module-features\">\r\n          <li><strong>Alignment reports<\/strong> &#8212; where the record and what happened disagree. An empty report is the good outcome<\/li>\r\n          <li><strong>Six fairness rules enforced by the system<\/strong> &#8212; rates hidden below a minimum sample; what a person controls separated from what they do not; every figure one click from the sessions behind it; no league table on a person&#8217;s own page<\/li>\r\n          <li><strong>Outcome measurement at admission and discharge<\/strong> &#8212; evidence that treatment works, in a form you can put in front of a payer, a regulator or a board<\/li>\r\n          <li><strong>Occupancy and capacity<\/strong> &#8212; whether the constraint is rooms, hours or demand, which is a different decision each time<\/li>\r\n          <li><strong>A professional sees only themselves<\/strong> &#8212; enforced by permission, never by a pre-set filter<\/li>\r\n        <\/ul>\r\n      <\/article>\r\n\r\n      <article class=\"sdc-module-card\">\r\n        <div class=\"sdc-module-card-top\"><h3>Satisfaction &#8212; what the patient notices<\/h3><\/div>\r\n        <ul class=\"sdc-module-features\">\r\n          <li><strong>Booking against real availability<\/strong> &#8212; they book, and it is booked. No call-back, no telephone tag<\/li>\r\n          <li><strong>Their own portal<\/strong> &#8212; their documents, their plan, their goals, their progress<\/li>\r\n          <li><strong>Monitoring between sessions<\/strong> &#8212; care continues instead of pausing for three weeks<\/li>\r\n          <li><strong>Secure messaging with their clinician<\/strong> &#8212; a question answered without an appointment<\/li>\r\n          <li><strong>One record<\/strong> &#8212; they are not asked the same question by three different people<\/li>\r\n        <\/ul>\r\n      <\/article>\r\n    <\/div>\r\n\r\n    <figure class=\"sdc-figure\">\r\n      <img decoding=\"async\" src=\"\/wp-content\/themes\/sevendayscare\/assets\/img\/diagram-one-record.svg\" alt=\"On the left, four separate systems &#8212; a booking tool, a clinical record, accounts and a marketing list &#8212; with dashed arrows between them labelled re-keying, reconciling and disagreeing. On the right, one database holding scheduling, the clinical record, orders and invoices, enquiries and campaigns, and documents with the access log.\">\r\n      <figcaption><b>The cost is not the four subscriptions.<\/b> It is the people who carry\r\n        data between them, and the disagreements that appear when they miss something. On one\r\n        database the invoice and the booking are the same data, so there is nothing to\r\n        reconcile and nothing to assemble a report from.<\/figcaption>\r\n    <\/figure>\r\n  <\/div>\r\n<\/section>\r\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t<div class=\"elementor-element elementor-element-68e785f e-con-full e-flex e-con e-parent\" data-id=\"68e785f\" data-element_type=\"container\" data-e-type=\"container\">\n\t\t\t\t<div class=\"elementor-element elementor-element-7e91a50 elementor-widget elementor-widget-html\" data-id=\"7e91a50\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"html.default\">\n\t\t\t\t\t<!-- ======================================================== platform -->\r\n<section class=\"sdc-page-head\" id=\"platform\">\r\n  <div class=\"sdc-wrap\">\r\n    <p class=\"sdc-eyebrow\">What is in the instance<\/p>\r\n    <h1>Ten areas. <span class=\"sdc-grad-text\">Every one of them ships<\/span>, and is tested.<\/h1>\r\n    <p class=\"sdc-hero-lede\">This is not a roadmap. The module-by-module inventory is generated from the\r\n      code itself, so the figures below are counted rather than claimed.<\/p>\r\n\r\n    <div class=\"sdc-counts\" style=\"margin-top:var(--sdc-space-10)\">\r\n      <div class=\"sdc-count\"><b>88<\/b><span>modules<\/span><\/div>\r\n      <div class=\"sdc-count\"><b>504<\/b><span>models<\/span><\/div>\r\n      <div class=\"sdc-count\"><b>249<\/b><span>test files<\/span><\/div>\r\n      <div class=\"sdc-count\"><b>7<\/b><span>compliance packs<\/span><\/div>\r\n      <div class=\"sdc-count\"><b>0<\/b><span>per-user licence fees<\/span><\/div>\r\n    <\/div>\r\n  <\/div>\r\n<\/section>\r\n\r\n<section class=\"sdc-band\" id=\"inventory\">\r\n  <div class=\"sdc-wrap\">\r\n    <dl class=\"sdc-areas\">\r\n      <div class=\"sdc-area\">\r\n        <dt>Clinical record<\/dt>\r\n        <dd>Episodes from admission to discharge &#183; <b>versioned treatment plans<\/b> with nested\r\n          goals and a review history &#183; template-driven session notes with typed answers &#183;\r\n          scored instruments charted over the episode &#183; goals and between-session monitoring &#183;\r\n          group session notes filed per attendee &#183; intake questionnaires &#183; recalls &#183;\r\n          ICD-10-CM coding<\/dd>\r\n      <\/div>\r\n      <div class=\"sdc-area\">\r\n        <dt>Documents<\/dt>\r\n        <dd>Encryption per document and per field &#183; keys held separately &#183;\r\n          <b>disposal by destroying the key<\/b> &#183; an access log no administrator can edit &#183;\r\n          retention configurable per document type &#183; a client document portal<\/dd>\r\n      <\/div>\r\n      <div class=\"sdc-area\">\r\n        <dt>Scheduling<\/dt>\r\n        <dd>Availability rules and exceptions &#183; rooms and resources &#183; clinician calendars &#183;\r\n          team and room views &#183; <b>online booking against real availability<\/b> &#183; time zones<\/dd>\r\n      <\/div>\r\n      <div class=\"sdc-area\">\r\n        <dt>Sessions and money<\/dt>\r\n        <dd>Session credits and packages &#183; tiered cancellation policy &#183; memberships &#183;\r\n          offline payment &#183; orders and invoicing &#183; practitioner pay with four formulas and\r\n          contract version timelines &#183; <b>payout runs that write real supplier bills<\/b><\/dd>\r\n      <\/div>\r\n      <div class=\"sdc-area\">\r\n        <dt>CRM and acquisition<\/dt>\r\n        <dd>Referrer and partner register &#183; enquiry capture with a clock on it &#183; website and\r\n          content &#183; campaigns and newsletters &#183; events, courses and certificates &#183;\r\n          <b>attribution from first click to admitted patient<\/b><\/dd>\r\n      <\/div>\r\n      <div class=\"sdc-area\">\r\n        <dt>Reporting<\/dt>\r\n        <dd>Alignment reports &#183; performance reports under six fairness rules &#183; occupancy and\r\n          capacity &#183; finance dashboards &#183; team dashboards &#183; care reports &#183;\r\n          <b>a daily health digest<\/b><\/dd>\r\n      <\/div>\r\n      <div class=\"sdc-area\">\r\n        <dt>Governance<\/dt>\r\n        <dd>Risk assessments &#183; activity review &#183; workforce designations, sanctions and access\r\n          termination &#183; training records &#183; contingency plans &#183; <b>a compliance health check\r\n          that reports only what is wrong<\/b><\/dd>\r\n      <\/div>\r\n      <div class=\"sdc-area\">\r\n        <dt>Communication<\/dt>\r\n        <dd>Secure chat inside the record &#183; metered chat consultation &#183; video sessions &#183;\r\n          push, email and SMS notification<\/dd>\r\n      <\/div>\r\n      <div class=\"sdc-area\">\r\n        <dt>E-signature<\/dt>\r\n        <dd>Consent and agreements signed and <b>bound to the record<\/b> they belong to, with the\r\n          signed copy kept where you can produce it years later<\/dd>\r\n      <\/div>\r\n      <div class=\"sdc-area\">\r\n        <dt>Compliance packs<\/dt>\r\n        <dd>GDPR\/EU &#183; UK &#183; US (HIPAA) &#183; Germany &#183; Norway &#183; Finland &#183;\r\n          Switzerland &#8212; <b>installed per market as needed<\/b>, not carried by everybody<\/dd>\r\n      <\/div>\r\n    <\/dl>\r\n\r\n    <figure class=\"sdc-figure\">\r\n      <img decoding=\"async\" src=\"\/wp-content\/themes\/sevendayscare\/assets\/img\/diagram-stack.svg\" alt=\"Four stacked layers. Surfaces: the mobile app, the client portal, the expert workspace and the back office. Below it the API gateway, holding named operations, short-lived tokens and rate limits. Below that the business core with 88 modules, 504 models and the roles, record rules and access log. At the bottom the data layer: PostgreSQL, encrypted documents and key custody.\">\r\n      <figcaption><b>Each layer talks only to its neighbour.<\/b> That is why changing a payment\r\n        provider or an AI vendor never reaches the app, and why the app can never reach the\r\n        database. The rules live in one place, so they hold through an export and through a\r\n        report &#8212; not only on the screen that was built to show them.<\/figcaption>\r\n    <\/figure>\r\n  <\/div>\r\n<\/section>\r\n\r\n<section class=\"sdc-band sdc-band--subtle\" id=\"roles\">\r\n  <div class=\"sdc-wrap\">\r\n    <p class=\"sdc-eyebrow\">Who uses it<\/p>\r\n    <h2 class=\"sdc-section-title\">Eight kinds of person, and a ninth you define<\/h2>\r\n    <p class=\"sdc-section-lede\" style=\"margin-left:0\">A role is configuration. Supervision, a county\r\n      case worker, an external partner &#8212; each is added and permitted, not built.<\/p>\r\n\r\n    <div class=\"sdc-roles\" style=\"margin-top:var(--sdc-space-8)\">\r\n      <div class=\"sdc-role\"><b>Clinician<\/b><span>Their caseload, diary, notes, plans, instruments, goals, reports, messages<\/span><\/div>\r\n      <div class=\"sdc-role\"><b>Clinical administrator<\/b><span>Everything clinical across the service, plus client transfer and oversight<\/span><\/div>\r\n      <div class=\"sdc-role\"><b>Reception<\/b><span>Diary, booking, arrivals, payments &#8212; and not the clinical record<\/span><\/div>\r\n      <div class=\"sdc-role\"><b>Finance<\/b><span>Orders, invoices, payouts, dashboards &#8212; and not the clinical record<\/span><\/div>\r\n      <div class=\"sdc-role\"><b>Manager<\/b><span>Alignment and performance reports, occupancy, capacity<\/span><\/div>\r\n      <div class=\"sdc-role\"><b>Quality<\/b><span>Outcome measurement, the governance register, the health check<\/span><\/div>\r\n      <div class=\"sdc-role\"><b>Client<\/b><span>Their own portal, and nothing else<\/span><\/div>\r\n      <div class=\"sdc-role\"><b>Anything else<\/b><span>A role is configuration, not a project<\/span><\/div>\r\n    <\/div>\r\n\r\n    <div class=\"sdc-notice\" style=\"margin-top:var(--sdc-space-10)\">\r\n      <strong>Access is enforced at three independent levels, and a user must pass all three<\/strong>\r\n      <p>Role, module access, and a record rule enforced <em>in the data layer rather than on the\r\n        screen<\/em> &#8212; so the rule holds through an export and through a report, which is where\r\n        most products leak.<\/p>\r\n    <\/div>\r\n  <\/div>\r\n<\/section>\r\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t<div class=\"elementor-element elementor-element-95ec31b e-con-full e-flex e-con e-parent\" data-id=\"95ec31b\" data-element_type=\"container\" data-e-type=\"container\">\n\t\t\t\t<div class=\"elementor-element elementor-element-8a25abd elementor-widget elementor-widget-html\" data-id=\"8a25abd\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"html.default\">\n\t\t\t\t\t<!-- =========================================================== ahead -->\r\n<section class=\"sdc-band\" id=\"ahead\">\r\n  <div class=\"sdc-wrap\">\r\n    <p class=\"sdc-eyebrow\">Getting ahead<\/p>\r\n    <h2 class=\"sdc-section-title\">Four moves your competitors cannot easily make<\/h2>\r\n    <p class=\"sdc-section-lede\" style=\"margin-left:0\">Not because they are worse at running a\r\n      clinic. Because their licence, their vendor or their data model will not let them.<\/p>\r\n\r\n    <div class=\"sdc-moves\" style=\"margin-top:var(--sdc-space-10)\">\r\n      <article class=\"sdc-move\">\r\n        <div class=\"sdc-move-number\">01<\/div>\r\n        <h3>Open the system wide<\/h3>\r\n        <p class=\"sdc-move-sub\">without a budget conversation<\/p>\r\n        <p>Give reception, supervision, quality, a referrer or a county case worker their own\r\n          access. There is no per-user licence, so the question is whether they <em>should<\/em>\r\n          have it &#8212; not what it costs.<\/p>\r\n        <div class=\"sdc-move-stops\">\r\n          <b>What stops a competitor<\/b>\r\n          <span>Paying per seat means rationing access. Rationed access is why their data is\r\n            incomplete, and incomplete data is why their reports are arguments.<\/span>\r\n        <\/div>\r\n      <\/article>\r\n\r\n      <article class=\"sdc-move\">\r\n        <div class=\"sdc-move-number\">02<\/div>\r\n        <h3>Prove outcomes<\/h3>\r\n        <p class=\"sdc-move-sub\">to a payer, in their language<\/p>\r\n        <p>Scored instruments at admission, during treatment and at discharge, charted, tied to\r\n          the episode and the plan that produced them. When a commissioner, an insurer or a\r\n          board asks what your treatment achieves, you answer from the record.<\/p>\r\n        <div class=\"sdc-move-stops\">\r\n          <b>What stops a competitor<\/b>\r\n          <span>A clinic whose outcome questionnaires live in a separate tool answers with an\r\n            estimate, and an estimate loses a tender to a number.<\/span>\r\n        <\/div>\r\n      <\/article>\r\n\r\n      <article class=\"sdc-move\">\r\n        <div class=\"sdc-move-number\">03<\/div>\r\n        <h3>Launch a second brand<\/h3>\r\n        <p class=\"sdc-move-sub\">as configuration, not a project<\/p>\r\n        <p>A new service line, a new site or a whole second brand is a configuration choice.\r\n          Same database, same reporting, separate public face &#8212; and one set of numbers at\r\n          the end of the month.<\/p>\r\n        <div class=\"sdc-move-stops\">\r\n          <b>What stops a competitor<\/b>\r\n          <span>On a per-tenant product they buy a second subscription, and then reconcile two\r\n            sets of numbers for the rest of the brand&#8217;s life.<\/span>\r\n        <\/div>\r\n      <\/article>\r\n\r\n      <article class=\"sdc-move\">\r\n        <div class=\"sdc-move-number\">04<\/div>\r\n        <h3>Change vendor<\/h3>\r\n        <p class=\"sdc-move-sub\">including changing us<\/p>\r\n        <p>The foundation is open source and the database is yours. You can take it, host it\r\n          elsewhere, or have somebody else maintain it &#8212; and we know that when we quote you.<\/p>\r\n        <div class=\"sdc-move-stops\">\r\n          <b>What stops a competitor<\/b>\r\n          <span>Nothing, except that their supplier cannot offer it. It is the strongest\r\n            position a buyer of clinical software can hold.<\/span>\r\n        <\/div>\r\n      <\/article>\r\n    <\/div>\r\n\r\n    <div class=\"sdc-notice\" style=\"margin-top:var(--sdc-space-10)\">\r\n      <strong>What we will not claim<\/strong>\r\n      <p>That software makes you compliant. That anything is unhackable. That our staff could\r\n        never read your documents under any circumstance. Those are all false, and a supplier\r\n        who says them to you is telling you something about their other claims.<\/p>\r\n    <\/div>\r\n  <\/div>\r\n<\/section>\r\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t<div class=\"elementor-element elementor-element-3d382c1 e-con-full e-flex e-con e-parent\" data-id=\"3d382c1\" data-element_type=\"container\" data-e-type=\"container\">\n\t\t\t\t<div class=\"elementor-element elementor-element-e90f124 elementor-widget elementor-widget-html\" data-id=\"e90f124\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"html.default\">\n\t\t\t\t\t<!-- ============================================================ case -->\r\n<section class=\"sdc-band sdc-band--subtle\" id=\"case\">\r\n  <div class=\"sdc-wrap\">\r\n    <p class=\"sdc-eyebrow\">Work out your own case<\/p>\r\n    <h2 class=\"sdc-section-title\">We will not hand you a return figure, because we would be inventing it<\/h2>\r\n    <p class=\"sdc-section-lede\" style=\"margin-left:0\">Here is the arithmetic instead. Every input\r\n      is a number you already have or can get in an afternoon.<\/p>\r\n\r\n    <div class=\"sdc-table-wrap sdc-doc\" style=\"margin-top:var(--sdc-space-8)\">\r\n      <table>\r\n        <thead>\r\n          <tr><th>Line<\/th><th>What to measure<\/th><th>The calculation<\/th><\/tr>\r\n        <\/thead>\r\n        <tbody>\r\n          <tr><td><strong>A &#183; Reconciliation time<\/strong><\/td><td>Hours a month your team spends moving data between systems, reconciling them, or assembling reports<\/td><td>hours &#215; loaded hourly cost &#215; 12<\/td><\/tr>\r\n          <tr><td><strong>B &#183; Late cancellations and no-shows<\/strong><\/td><td>How many a month, and what you recover today<\/td><td>(sessions &#215; average value) &#8722; what you recover<\/td><\/tr>\r\n          <tr><td><strong>C &#183; Prepaid and unscheduled<\/strong><\/td><td>Sessions bought but never booked, over the last year<\/td><td>count &#215; average value<\/td><\/tr>\r\n          <tr><td><strong>D &#183; Lost enquiries<\/strong><\/td><td>Enquiries received against enquiries converted &#8212; the gap nobody followed up<\/td><td>gap &#215; conversion rate &#215; average episode value<\/td><\/tr>\r\n          <tr><td><strong>E &#183; Licence fees<\/strong><\/td><td>What you pay now, per user per month, across all four systems<\/td><td>current annual spend<\/td><\/tr>\r\n          <tr><td><strong>F &#183; The cost<\/strong><\/td><td>Implementation, and the annual fee<\/td><td><a href=\"\/pricing\/\">the calculator<\/a><\/td><\/tr>\r\n        <\/tbody>\r\n      <\/table>\r\n    <\/div>\r\n\r\n    <p style=\"margin-top:var(--sdc-space-6)\"><strong>A + B + C + D + E against F, over three\r\n      years.<\/strong> If that does not clear your hurdle, do not buy it &#8212; and tell us which\r\n      line was weakest, because that is more useful to us than a signature.<\/p>\r\n\r\n    <p style=\"margin-top:var(--sdc-space-4)\"><strong>Two honest cautions.<\/strong> Line A rarely\r\n      goes to zero; it goes down. Line D depends on your follow-up actually happening once the\r\n      system shows you the gap &#8212; the platform surfaces it, your team closes it.<\/p>\r\n  <\/div>\r\n<\/section>\r\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t<div class=\"elementor-element elementor-element-6b2fe74 e-con-full e-flex e-con e-parent\" data-id=\"6b2fe74\" data-element_type=\"container\" data-e-type=\"container\">\n\t\t\t\t<div class=\"elementor-element elementor-element-8ed9b24 elementor-widget elementor-widget-html\" data-id=\"8ed9b24\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"html.default\">\n\t\t\t\t\t<!-- ======================================================= two ways -->\r\n<section class=\"sdc-band\" id=\"deployment\">\r\n  <div class=\"sdc-wrap\">\r\n    <p class=\"sdc-eyebrow sdc-center\">Two ways to have it<\/p>\r\n    <h2 class=\"sdc-section-title sdc-center\">Run it yourself, or let us run it<\/h2>\r\n    <p class=\"sdc-section-lede sdc-center\">Both are your own instance and your own database. The\r\n      difference is who holds the servers &#8212; and you can move between them later, because\r\n      that is a database and a file store moving, not a rebuild.<\/p>\r\n\r\n    <div class=\"sdc-table-wrap sdc-doc\" style=\"margin-top:var(--sdc-space-8)\">\r\n      <table>\r\n        <thead>\r\n          <tr><th><\/th><th>Self-hosted<\/th><th>Hosted by us<\/th><\/tr>\r\n        <\/thead>\r\n        <tbody>\r\n          <tr><td><strong>Where it runs<\/strong><\/td><td>Your datacentre or your cloud account<\/td><td>Our infrastructure<\/td><\/tr>\r\n          <tr><td><strong>Who holds the data<\/strong><\/td><td>You<\/td><td>We do, as your processor, under contract<\/td><\/tr>\r\n          <tr><td><strong>Who patches the servers<\/strong><\/td><td>You, or us under a management agreement<\/td><td>Us<\/td><\/tr>\r\n          <tr><td><strong>Upgrade timing<\/strong><\/td><td>Entirely yours<\/td><td>Agreed window<\/td><\/tr>\r\n          <tr><td><strong>Isolated-network option<\/strong><\/td><td><strong>Yes<\/strong> &#8212; the full isolated architecture<\/td><td>Partly; the internal zone is ours, not your LAN<\/td><\/tr>\r\n          <tr><td><strong>Suits<\/strong><\/td><td>An IT function, a security policy that requires it, or a legal duty that makes it simpler<\/td><td>Wanting the capability without running servers<\/td><\/tr>\r\n          <tr><td><strong>Cost shape<\/strong><\/td><td>Lower recurring; you carry the infrastructure<\/td><td>Higher recurring; nothing to run<\/td><\/tr>\r\n        <\/tbody>\r\n      <\/table>\r\n    <\/div>\r\n  <\/div>\r\n<\/section>\r\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t<div class=\"elementor-element elementor-element-059738e e-con-full e-flex e-con e-parent\" data-id=\"059738e\" data-element_type=\"container\" data-e-type=\"container\">\n\t\t\t\t<div class=\"elementor-element elementor-element-bca2b77 elementor-widget elementor-widget-html\" data-id=\"bca2b77\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"html.default\">\n\t\t\t\t\t<!-- ======================================================== security -->\r\n<section class=\"sdc-band sdc-band--subtle\" id=\"security\">\r\n  <div class=\"sdc-wrap sdc-duo\">\r\n    <div>\r\n      <p class=\"sdc-eyebrow\">Where your data sits<\/p>\r\n      <h2 class=\"sdc-section-title\">One database, and an isolated option where the duty is heavier<\/h2>\r\n      <p class=\"sdc-section-lede\" style=\"margin-left:0\">The standard deployment is a straightforward\r\n        one: application, database and file store behind TLS, with roles and record rules doing\r\n        the access work.<\/p>\r\n      <p style=\"margin-top:var(--sdc-space-5)\">Where the duty is heavier we offer an architecture in\r\n        which <strong>the clinical record has no route from the internet at all<\/strong>. An\r\n        internet-facing gateway serves patients and referrers and holds an identifier and a\r\n        password and nothing else; it reaches the internal system only through a fixed list of\r\n        named operations from one address; the encryption keys sit on a third host in a separate\r\n        trust domain.<\/p>\r\n      <p style=\"margin-top:var(--sdc-space-5)\"><strong>What that buys, precisely:<\/strong> somebody\r\n        who takes the entire internet-facing tier holds a set of opaque identifiers and password\r\n        hashes with nothing to join them to.<\/p>\r\n    <\/div>\r\n\r\n    <div class=\"sdc-category-card\">\r\n      <h3>Security, and one honest limit<\/h3>\r\n      <ul class=\"sdc-ticks\" style=\"margin-top:var(--sdc-space-5)\">\r\n        <li><strong>Encryption<\/strong> per document and per field &#8212; you choose what<\/li>\r\n        <li><strong>Key custody<\/strong> off the application host, with an unwrap quota and a log that host cannot rewrite<\/li>\r\n        <li><strong>Access log<\/strong> on every read and write. Being an administrator grants nothing by itself<\/li>\r\n        <li><strong>Break-glass<\/strong> &#8212; time-boxed, needs a written reason, raises an alert<\/li>\r\n        <li><strong>Automatic logoff<\/strong> after inactivity, enforced on the server<\/li>\r\n        <li><strong>Disposal by destroying the key<\/strong><\/li>\r\n        <li><strong>HIPAA, GDPR and UK packs<\/strong> &#8212; the obligation is yours; what we carry is your copy of it<\/li>\r\n      <\/ul>\r\n      <p style=\"margin-top:var(--sdc-space-6)\"><strong>The honest limit:<\/strong> no key-custody\r\n        design defends against an attacker resident in the application process waiting for\r\n        legitimate reads. A legitimate open unwraps a key into the process. What the design buys\r\n        is rate-limited access with a witness &#8212; not prevention.<\/p>\r\n    <\/div>\r\n  <\/div>\r\n<\/section>\r\n\r\n<section class=\"sdc-band\" id=\"isolated\">\r\n  <div class=\"sdc-wrap\">\r\n    <figure class=\"sdc-figure\" style=\"margin-top:0\">\r\n      <img decoding=\"async\" src=\"\/wp-content\/themes\/sevendayscare\/assets\/img\/diagram-isolated.svg\" alt=\"Three zones separated by two firewalls. On the internet, a gateway holding an identifier, a password hash and nothing that names anybody. Behind the first firewall, your internal network with the clinical record, scheduling, orders, finance, the database and documents, reachable only through named operations. Behind the second, a key host in a separate trust domain holding the key-encryption key, an unwrap quota and a log the application host cannot rewrite.\">\r\n      <figcaption><b>The isolated option, offered where the duty is heavier.<\/b> It is not the\r\n        standard deployment and it costs more to run &#8212; three hosts, two firewall rules and a\r\n        key authority instead of one server. Ask for it when a regulator, an insurer or your own\r\n        security policy makes the ordinary arrangement hard to defend.<\/figcaption>\r\n    <\/figure>\r\n  <\/div>\r\n<\/section>\r\n\r\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t<div class=\"elementor-element elementor-element-6007025 e-con-full e-flex e-con e-parent\" data-id=\"6007025\" data-element_type=\"container\" data-e-type=\"container\">\n\t\t\t\t<div class=\"elementor-element elementor-element-3bb453e elementor-widget elementor-widget-html\" data-id=\"3bb453e\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"html.default\">\n\t\t\t\t\t<!-- =========================================================== live -->\r\n<section class=\"sdc-band\" id=\"live\">\r\n  <div class=\"sdc-wrap\">\r\n    <p class=\"sdc-eyebrow\">Getting live<\/p>\r\n    <h2 class=\"sdc-section-title\">Eight phases, and the two things that decide how long<\/h2>\r\n\r\n    <div class=\"sdc-phases\" style=\"margin-top:var(--sdc-space-8); max-width:70ch\">\r\n      <div class=\"sdc-phase\"><b>Discovery<\/b><span>Your structure, roles, pathways, reporting obligations and current systems<\/span><\/div>\r\n      <div class=\"sdc-phase\"><b>Foundation<\/b><span>Infrastructure, platform, roles and record rules, your branding, your language<\/span><\/div>\r\n      <div class=\"sdc-phase\"><b>Clinical configuration<\/b><span>Episodes, note templates, instruments, treatment plan structure. Your model, not a default<\/span><\/div>\r\n      <div class=\"sdc-phase\"><b>Operations<\/b><span>Scheduling, capacity, finance, purchasing, payroll interface<\/span><\/div>\r\n      <div class=\"sdc-phase\"><b>Acquisition<\/b><span>Website, enquiry capture, referrer register, campaigns<\/span><\/div>\r\n      <div class=\"sdc-phase\"><b>Migration<\/b><span>From your current systems, scoped once we have seen them<\/span><\/div>\r\n      <div class=\"sdc-phase\"><b>Training<\/b><span>Role-based, in your language<\/span><\/div>\r\n      <div class=\"sdc-phase\"><b>Hypercare<\/b><span>A raised response level after go-live<\/span><\/div>\r\n    <\/div>\r\n\r\n    <p style=\"margin-top:var(--sdc-space-6); max-width:80ch\"><strong>Duration depends on two things\r\n      only:<\/strong> how much configuration your clinical model needs, and how much data has to\r\n      move. A straightforward deployment runs in weeks; one replacing an established clinical\r\n      record system runs longer, and we will not quote it before seeing that system.<\/p>\r\n  <\/div>\r\n<\/section>\r\n\r\n<section class=\"sdc-band\">\r\n  <div class=\"sdc-wrap\">\r\n    <div class=\"sdc-cta\">\r\n      <h2>Price it on the modules you actually switch on<\/h2>\r\n      <p>Four questions and a list of modules. A one-off build figure and an annual support\r\n        figure, itemised, with nothing hidden behind &#8220;contact us&#8221;.<\/p>\r\n      <div class=\"sdc-cta-actions\">\r\n        <a class=\"sdc-btn sdc-btn--invert\" href=\"\/pricing\/\">Open the price calculator<\/a>\r\n        <a class=\"sdc-btn sdc-btn--ghost sdc-on-dark\" href=\"#\">Book a discovery call<\/a>\r\n      <\/div>\r\n    <\/div>\r\n  <\/div>\r\n<\/section>\r\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t","protected":false},"excerpt":{"rendered":"<p>For clinics, groups and organisations Your own instance. Your servers, your data, your upgrade schedule. A full ERP, CRM and EHR in one database, on infrastructure you choose &#8212; plus custom development that turns your own way of working into part of the product, and leaves you owning it. Built on open-source Odoo Community, so [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"class_list":["post-41","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/7dayscare.com\/index.php\/wp-json\/wp\/v2\/pages\/41","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/7dayscare.com\/index.php\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/7dayscare.com\/index.php\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/7dayscare.com\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/7dayscare.com\/index.php\/wp-json\/wp\/v2\/comments?post=41"}],"version-history":[{"count":5,"href":"https:\/\/7dayscare.com\/index.php\/wp-json\/wp\/v2\/pages\/41\/revisions"}],"predecessor-version":[{"id":46,"href":"https:\/\/7dayscare.com\/index.php\/wp-json\/wp\/v2\/pages\/41\/revisions\/46"}],"wp:attachment":[{"href":"https:\/\/7dayscare.com\/index.php\/wp-json\/wp\/v2\/media?parent=41"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}