Margin analytics combines revenue, cost, and volume data to show contribution and allocated margin by service line, payer, and provider. It computes margin from your cost accounting method and states its assumptions. It does not decide which services to offer, which payers to accept, or how any patient should be treated.
Margin analysis is decided by allocation assumptions more than by data quality. Two defensible methods applied to identical data produce different service line rankings, and a platform that hides its method produces boardroom arguments rather than decisions. Taction builds margin analytics where the method is explicit, the assumptions are visible, and every figure traces to its inputs.
Our experts are ready to understand your business goals.
Margin analytics answers what a service line, case type, payer, or provider contributes after cost. That requires revenue at the encounter level, cost derived from your accounting method, and volume with consistent definitions, all reconciled to the general ledger. It sits inside a wider healthcare data analytics practice and depends on the modelling discipline our analytics consulting work brings to definitions before any dashboard exists. Two defensible methods applied to the same data produce different rankings, which is why the method has to be visible rather than embedded inside a dashboard.
Costs reach an encounter through a chosen method: relative value units, activity-based costing, or a hybrid. Method choice determines your results, so it is stated rather than embedded silently. Simplicity and defensibility trade off directly.
Contribution margin excludes indirect overhead. Fully allocated margin distributes it using assumptions people will dispute. Both views are reported, labelled clearly and separately. Confusing the two is the commonest error we see in boardroom material.
A service line is a grouping decision made by your finance and clinical leadership, not a natural category. Definition ownership must sit with them and be versioned. Disagreement here stalls more projects than data quality.
Expected reimbursement by payer and contract compared against actual, connected to your billing platform data. Yield analysis separates contract terms from collection performance. Underpayment and slow payment are different problems requiring different responses.
Attributing encounters and their margin to providers requires explicit rules where care is shared. Attribution rules are agreed openly because the results affect people. Shared care makes these rules contested rather than technical.
It does not determine service offerings, payer participation, staffing, or anything about an individual patient’s care. Those decisions belong to leadership and clinicians respectively. We state that boundary in our proposals rather than only here.
The work that decides credibility is definitions and reconciliation. A margin figure that does not tie to the general ledger will be dismissed by finance, and a service line nobody agreed will be dismissed by clinicians. We settle both before building visualisation. Our data warehouse and data lake practices supply the platform layer where you do not already have one. We also test sensitivity to alternative allocation assumptions and report it, because presenting one ranking as fact would misrepresent how much the method itself is driving the answer rather than the underlying performance.
Your chosen costing method implemented with drivers, assumptions, and version history recorded per period. Assumption records are what let a figure be explained later. Drivers are documented in language your leadership can actually review.
Modelled revenue and cost reconciled to the general ledger with variances explained rather than absorbed. Reconciliation is the credibility test finance applies first. Variances are explained rather than absorbed into a convenient allocation.
Service line, case type, and attribution definitions owned by named people, versioned, and documented readably. Readable definitions survive challenge from either finance or clinicians. Version history explains why a figure differs between two periods.
Payer mix, expected versus actual reimbursement, and contract yield reported at the level decisions are made. Yield detail distinguishes contract from collection problems. Reporting reaches contract and plan level rather than stopping at payer.
Source completeness, cost driver integrity, and encounter linkage monitored through our data quality practice. Quality controls prevent a quiet distortion becoming a decision. A quiet distortion becoming a board decision is the risk here.
Reporting to encounter level with method and assumptions visible, using our data visualisation practice. Drill-down is what converts a number into a discussion. Method and assumptions appear on the report rather than in an appendix.
We publish no figures on margin improvement, cost savings, or contribution gains, because those depend entirely on your case mix, your contracts, and the decisions your leadership makes. What we deliver is instrumentation so your team measures impact against its own data. The benefit is a margin figure people will actually argue about productively, because the method is visible and the numbers reconcile. Analytics that cannot survive that scrutiny changes nothing. Read the items below as credibility and traceability rather than as any claim about margin improvement, which follows from decisions your leadership makes.
Modelled results tie to the general ledger with variances explained. Reconciliation is what stops finance rejecting the platform in the first meeting. Unreconciled analytics get rejected in the first meeting, and rightly so.
Costing method, drivers, and allocation assumptions appear alongside results. Visible method turns disagreement about numbers into disagreement about assumptions. Disagreement about assumptions is productive; disagreement about the numbers themselves is not.
Contribution and fully allocated margin are reported separately and labelled. Separate views prevent overhead assumptions being mistaken for operational performance. Labelling prevents an overhead assumption being read as operational performance.
Service line and attribution definitions are owned, versioned, and readable. Agreed definitions remove the recurring argument about what a figure covers. The recurring argument about what a figure covers simply stops.
Contract terms and collection performance are distinguishable rather than blended. Yield separation directs effort at the actual cause. Contract renegotiation and collections work are directed at the right cause each time.
Allocation assumptions drive results more than data precision does. Assumption sensitivity is reported, because a single ranking presented as fact would mislead. Sensitivity is reported rather than concealed behind a single ranking.
We start with definitions and reconciliation, not dashboards, because a beautiful platform built on contested definitions gets abandoned. Discovery is paid and time-boxed and produces an itemised fixed-scope estimate with a build or configure recommendation. Where your cost accounting system already produces defensible results and the gap is reporting, we scope that alone. Delivery runs in short increments with finance and clinical leadership reviewing figures each time. Finance and clinical leadership both review figures before anything is published, because a platform either of them rejects will not be used regardless of its quality.
Cost accounting method, source systems, and ledger structure assessed for what is achievable now. Source reality constrains the method more than preference does. What is achievable now differs from what would be ideal.
Service lines, case groupings, and attribution rules agreed with finance and clinical leadership in writing. Written agreement precedes any implementation work. We do not proceed on an analyst’s interpretation of a service line.
Revenue and cost models built and reconciled to the ledger before anything is visualised. Reconciliation first because unreconciled figures are worthless. Visualisation follows reconciliation rather than preceding it in our sequence.
Every allocation and driver assumption documented in language leadership can review and challenge. Documented assumptions are a deliverable rather than an appendix. Leadership should be able to challenge an assumption without an analyst present.
Results tested against alternative allocation assumptions so sensitivity is known. Sensitivity results are shared rather than kept internal to the project. Knowing how much the method drives the answer changes how decisions get made.
Reporting released with method documentation and definition ownership transferred, using our modern data architecture foundations. Definition ownership stays with your team. Method documentation travels with the reporting rather than sitting separately.
We build modelling and reporting on your data platform, with governance through our data governance practice. Compliance covers HIPAA safeguards where encounter-level data is involved, access control appropriate to financial and provider-level information, and audit sufficient to reconstruct any published figure. We hold one firm position: margin data informs organisational decisions and is never wired into anything that affects an individual patient’s care or access. We also report the payer and geographic mix of patients affected wherever a service reduction is being considered, so the decision is made with that visible.
We decline to build anything that routes, prioritises, or restricts patients by payer or expected margin. Patient steering by financial value is a line we will not cross. That refusal appears in our proposals.
Provider-level margin depends on attribution rules and case mix. We decline to build punitive provider rankings, and we require case mix context alongside any provider figure. Case mix travels with every provider figure structurally.
Every published figure records its method version, drivers, and allocation assumptions. Method records are what make a historical figure explicable. A figure from two years ago remains explicable to whoever asks.
Financial and provider-level data carries role-based access with logging, since exposure has real consequences. Access design is deliberate rather than inherited. Provider-level financial exposure has genuine consequences for individuals involved.
Where service reductions are contemplated, payer and geographic mix of affected patients is reported. Impact visibility ensures the decision is informed. An uninformed reduction decision affects patients unevenly and invisibly.
Inputs, definitions, method versions, and outputs are retained so any figure can be reproduced. Reproducibility is what survives a board challenge. A board challenge is answered with reproduction rather than with recollection.
We have been building healthcare software since 2013, which is over 12 years, and we have delivered more than 200 healthcare projects. We built our own EHR platform, Voyant Health, so encounter data, charge capture, and the relationship between clinical activity and billed revenue are working knowledge. We are ISO 27001 certified, our leadership brings more than 20 years of personal experience in the field, and we work from four US offices in Chicago, Cheyenne, Austin, and Sacramento. We will also tell you when your cost accounting system already produces defensible results and only reporting is missing.
We settle service line and attribution definitions in writing before building. That sequence delays the first visual and prevents abandonment later. Abandoned platforms almost always trace back to contested definitions.
Figures tie to the ledger with variances explained before anything is published. Reconciliation is the test that decides whether finance trusts the platform. Finance trust is won or lost at that first reconciliation meeting.
Allocation assumptions and their sensitivity are reported alongside results. Published sensitivity makes disagreement productive rather than personal. Sensitivity results are shared rather than kept inside the delivery project team alone.
Taction is ISO 27001 certified, with documented access control, encryption, and change control that stands up to a customer security review. Provider-level and financial data carry role-based access with full logging.
Margin data will not be wired into patient routing or access decisions. That refusal is stated in our proposals rather than only in conversation. Organisational decisions are legitimate; individual patient steering is not.
Four US offices in Chicago, Cheyenne, Austin, and Sacramento, with delivery overlapping your hours through definition workshops and reconciliation. Escalation reaches a named delivery lead rather than a shared support queue.
Pricing turns on your cost accounting maturity, source system count, and whether a data platform already exists. The tiers below cover engineering. Third-party licensing, cloud infrastructure, data subscriptions, and hardware are separate from engineering cost and itemised clearly. Cost accounting software, benchmark datasets, and comparative data subscriptions are licensed directly by your organisation and sit outside our engineering estimate at every tier. Where definitions are unagreed, that facilitation work is quoted honestly rather than absorbed into a build estimate that then overruns once the disagreement surfaces in a definition workshop later on.
$40,000 to $80,000 for contribution margin by service line with ledger reconciliation, method documentation, and encounter-level drill-down. Allocated margin and yield analysis can follow in a later phase of work.
$80,000 to $200,000 for contribution and allocated margin, payer mix and yield, provider attribution, sensitivity analysis, quality controls, and reporting. This tier covers most single-facility finance programmes that we are asked to scope.
Starting at $200,000 for multi-facility systems with consistent definitions, several source systems, platform build, and consolidated governance. Source system count and definition governance drive the figure more than facility numbers.
A paid, time-boxed discovery phase produces a method and source assessment, draft definitions, reconciliation feasibility, build or configure recommendation, and an itemised estimate. The draft definitions are yours whether or not we build.
Cost accounting maturity, source system count, ledger structure, and definition disagreement. Unagreed definitions delay projects more than any technical factor. Facilitating definition agreement is real work we quote openly and separately.
Budget annually for method and driver review, definition maintenance, reconciliation monitoring, and source system change handling. Contract changes require yield model updates. Driver reviews follow your cost accounting cycle rather than ours.
If your last margin discussion became an argument about allocation, start with definitions and reconciliation. A paid discovery phase gives you an assessment of your costing method and source systems, draft service line and attribution definitions for your leadership to agree, a reconciliation feasibility review against your ledger, sensitivity indications from alternative allocation approaches, a build or configure recommendation, and an itemised fixed-scope estimate. You keep the definitions and the assessment regardless.
These are the questions chief financial officers, decision support leaders, and service line directors raise before scoping margin work. Several concern method rather than technology, which is where this work genuinely lives. One concerns a use we refuse. Where an answer depends on your cost accounting maturity, the discovery assessment settles it quickly and is worth having on its own. We would rather explain that allocation assumptions drive your rankings than hand you a single confident number that falls apart the first time a service line director interrogates it properly.
That is your finance leadership’s decision, and it has consequences we will explain rather than make for you. Relative value unit methods are simpler and cruder. Activity-based costing is more defensible and considerably more work to maintain. We implement your choice, document its drivers, and report sensitivity so the trade-off stays visible.
Because they answer different questions and get confused constantly. Contribution margin shows what a line adds before overhead, which is operationally actionable. Fully allocated margin distributes overhead using assumptions reasonable people dispute, which matters for investment decisions. Presenting only one, unlabelled, is how margin analysis loses credibility.
Only if they reconcile to the ledger, which is why we build reconciliation before visualisation. Unreconciled analytics get rejected in the first meeting regardless of how good the model is, and rightly so. We explain variances rather than absorbing them into an allocation that makes the totals agree.
Provider-level margin depends heavily on attribution rules and case mix, so we require both to be visible alongside any provider figure and we decline to build punitive rankings. Compensation decisions are leadership’s, and using unvalidated attribution to make them produces exactly the disputes that end analytics programmes.
No. Margin data informs decisions about services, contracts, and operations at an organisational level. Wiring it into anything that routes, prioritises, or restricts an individual patient by payer or expected margin is a line we will not cross, and we state that in our proposals rather than waiting to be asked.
By settling them in writing before implementation, with named owners and version history. Definition disputes are the most common reason margin platforms get abandoned, and they are organisational rather than technical. We facilitate the discussion and document the outcome, and we will not proceed on an analyst’s interpretation.
Your email address will not be published. Required fields are marked *
Our expert reaches out shortly after receiving your request and analyzing your requirements.
If needed, we sign an NDA to protect your privacy.
We request additional information to better understand and analyze your project.
We schedule a call to discuss your project, goals. and priorities, and provide preliminary feedback.
If you're satisfied, we finalize the agreement and start your project.