Formulary management software maintains the list of medications an organisation has approved, the conditions attached to each one, and the committee record behind every decision. It presents formulary status inside prescribing and dispensing workflows. It does not substitute medications, deny therapy, or make formulary decisions.
Most hospital formularies live across a committee minute archive, a spreadsheet, the EHR’s medication list, and the memory of one pharmacist. When those four disagree, prescribers find out at the point of dispensing. Taction builds the system of record that makes formulary status, restrictions, and their approval history one thing instead of four.
Our experts are ready to understand your business goals.
A formulary is a governed list: which drugs are approved, at what tier, with what restrictions, and on whose authority. The software manages the decision workflow that produces that list and the interfaces that publish it into prescribing, dispensing, and reporting systems. It sits within the broader healthcare software development stack alongside pharmacy operations tooling, and where the need is dispensing, inventory, and patient-facing pharmacy workflow rather than the formulary itself, our pharmacy application development work covers that ground. Formulary software governs policy. Clinicians and pharmacists apply it to patients.
Each entry carries approval status, tier, restriction criteria, approved indications, effective dates, and the committee decision that created it. The record is the authority, not a downstream copy. Downstream systems hold copies.
Requests move through submission, clinical review, financial review, and committee vote. The P&T workflow enforces sequence and quorum, and records dissent alongside the decision. Agenda packs assemble from the queue automatically.
Restrictions encode prescriber specialty, indication, care setting, or duration limits. Restriction logic informs the prescriber at order entry, and an override path with documented reason always remains available. Hard blocks are deliberately avoided.
Approved interchange pairs are recorded with their protocol and scope. The software surfaces the interchange protocol for pharmacist action. It never swaps a medication autonomously. Scope and expiry are recorded with each pair.
Tier assignment, contract status, and acquisition cost context inform review. Cost visibility supports committee decisions and is deliberately separated from clinical restriction logic. Contract expiry dates surface in the committee queue for review.
Approved status publishes to the EHR medication list, dispensing systems, and reporting. Publication events are versioned so you can reconstruct the formulary as it stood on any past date. Every publication event is logged.
The recurring failure is not a missing feature, it is drift: the committee approves a restriction, the EHR is updated three weeks later, and the dispensing system never is. Our builds treat publication and reconciliation as first-class rather than as an afterthought bolted onto an authoring screen. We also decline to curate drug data ourselves. Where order set content and prescribing defaults are the actual requirement, that is our computerised provider order entry work rather than formulary management, and we split the scope accordingly at the outset. Publication design comes first.
A single authoritative store for status, tiers, restrictions, and effective dates, with versioned history and the committee decision attached to every entry. Effective dating answers retrospective questions about what status applied when.
Request intake, monograph attachment, reviewer assignment, agenda building, voting, and minute generation. Committee automation removes the manual agenda assembly that consumes pharmacy administrative hours. Reviewer workload becomes visible to pharmacy leadership.
Restriction criteria and approved interchange pairs configured as governed rules with scope, protocol reference, and expiry. Rule configuration stays in pharmacy hands, not in a code release. Changes route through approval before publication.
Formulary status pushed to the EHR and dispensing systems through supported interfaces. Our EHR and EMR integration services handle transport and reconciliation, including drift detection between systems. Mismatches raise work items automatically.
Structured requests, clinical justification capture, pharmacist review, and decision recording with turnaround reporting. Exception workflow makes the volume and pattern of exceptions visible to the committee. Turnaround targets are configurable per request type.
Reporting on prescribing against formulary, exception volumes, and interchange uptake, built on our healthcare data analytics practice. Variance reporting identifies where policy and practice diverge. Reports break down by prescriber group and site.
We publish no figures on drug spend, formulary compliance, or exception turnaround, because those depend entirely on your case mix, your contracting position, and your current committee practice. What we deliver is instrumentation so your team measures impact against its own data. There is a further honesty point specific to this category: software does not change prescribing behaviour. Savings come from committee decisions, contracting, and clinical engagement. The system makes those decisions visible and enforceable, which is necessary but not sufficient on its own. Read the items below as visibility, not savings.
Prescribers, pharmacists, and reporting all read the same record. Single source removes the situation where three systems give three different answers about the same drug. Downstream copies are reconciled rather than trusted.
Every status change carries its committee, date, vote, and rationale. Decision provenance supports accreditation review and answers the question of why a restriction exists. Historical status is reconstructable for any past date.
Automated comparison between the formulary of record and downstream systems surfaces mismatches. Drift detection catches the update that never propagated before a prescriber does. Alerts route to a named owner, not a shared inbox.
Structured exception data shows which restrictions generate constant workarounds. Exception patterns are the strongest signal that a policy needs revisiting rather than reinforcing. The committee sees volume, requester, and justification together.
Agenda building, monograph collation, and minute drafting move from manual work to workflow output. Administrative time returns to clinical pharmacy work. Pharmacy administrative hours return to clinical work rather than collation.
The software will not stop a determined prescriber or fix a contract. Behaviour change requires clinical leadership and engagement that no platform supplies. Engagement with prescribers remains your clinical leadership’s work.
We start with your committee, not your requirements document, because the workflow you actually run rarely matches the one written down. Discovery is paid and time-boxed and produces an itemised fixed-scope estimate along with a build or configure recommendation. If your EHR and existing pharmacy information system already cover the requirement between them, we say so and scope only the gap. Delivery runs in short increments with your pharmacy leadership reviewing working software, because formulary workflow is the sort of thing that looks correct on paper and fails in the first real committee cycle.
We observe an actual P&T cycle end to end, including the informal steps. Practice mapping finds the reviewer handoffs and side channels that requirements interviews never surface. We map what happens, not what is documented.
We compare the formulary as recorded against the EHR, dispensing system, and reporting. The drift audit usually produces the strongest early business case for the project. Mismatch counts are usually higher than expected.
We identify which licensed drug database you use and design against it. Data licensing is your decision and your recurring cost, and we recommend licensing rather than curating. Curation is a safety liability.
Restriction logic, interchange records, exception workflow, and downstream publication with reconciliation. Publication design includes rollback and versioned effective dating. Pharmacy staff edit rules directly after handover, with no developer release needed.
One full committee cycle running in the new system with the old process in parallel. The parallel cycle is where governance assumptions get tested under real deadline pressure. Parallel running ends only after reconciliation matches.
Phased rollout by service line or facility, with pharmacy-owned configuration training. Handover covers rule editing, publication runbooks, and drift monitoring. Each facility goes live only after its downstream systems reconcile cleanly.
We build formulary systems as governed policy platforms with published interfaces, not as engines that act on patients. Publication uses supported EHR and pharmacy system interfaces, and prescribing-time context can surface through the same channels that carry other clinical decision support content. Where electronic prescribing is in scope, our Surescripts integration work covers the transactional side. Compliance covers HIPAA safeguards, audit trails sufficient for accreditation review, and clear allocation of every clinical and regulatory determination to a named person. We also name, in the contract, which determinations remain with your pharmacists and which with the committee.
The system is clinical decision support. It does not diagnose, prescribe, substitute, deny, or select therapy for a patient. Pharmacists and prescribers make every clinical decision, with override paths always available.
Formulary status, therapeutic interchange approval, and non-formulary exception decisions are committee and pharmacist determinations. The software records and enforces them. It does not generate them. No rule in the system generates a formulary decision.
Drug identifiers, interactions, and classifications come from a licensed drug database you subscribe to. We integrate it as market context and make no reseller or certification claim about any vendor.
Restrictions can affect patient groups unevenly. We build subgroup reporting on exception volumes and denials so your committee can review access effects, and we treat adverse findings as a gate.
If demand or spend forecasting is in scope, it is a model and gets subgroup validation, documented limitations, and no role in individual patient access decisions. Model output informs planning, never a patient’s access.
Immutable decision history, role-based configuration rights, and retention supporting retrospective review. Audit integrity matters when a restriction is questioned years later, alongside medication inventory records. Configuration changes carry the same audit weight as decisions.
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 medication lists, prescribing interfaces, and publication mechanics are working knowledge rather than a diagram. 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 recommend against custom work when your existing systems cover the requirement.
Building Voyant Health meant building medication lists, order interfaces, and publication paths. That experience shapes how we size formulary integration work. Publication paths into a live medication list are where projects usually go wrong.
We build so that restriction rules and interchange records are edited by pharmacy staff, not by a developer in a release cycle. That is a design constraint, not a feature.
More than 200 healthcare projects since 2013, with engineers who have worked inside enough pharmacy and EHR environments to estimate integration realistically. Estimates come from that history rather than from optimism.
Taction is ISO 27001 certified, with documented access control, encryption, and change management that stands up to a customer security review. Your security questionnaire is answered from existing documentation, not improvised.
If your pharmacy information system and EHR already cover this between them, we say so. Configuration advice costs us revenue and saves you a maintenance obligation. We put that recommendation in writing.
Four US offices in Chicago, Cheyenne, Austin, and Sacramento, with delivery overlapping your hours for the daily contact pharmacy projects need. Escalation reaches a named delivery lead rather than a support queue.
Formulary software pricing depends on how many facilities you publish to, how complex your restriction model is, and the state of your downstream systems. The tiers below cover engineering. Third-party licensing, cloud infrastructure, data subscriptions, and hardware are separate from engineering cost and itemised clearly. This is a category where that separation matters: a licensed drug database subscription is a recurring vendor cost you carry regardless of who builds the platform, and folding it into a project figure would misrepresent your total cost of ownership from the first year onward.
$40,000 to $80,000 for a formulary system of record plus P&T committee workflow for a single site, with publication to one EHR instance. Suits a department proving the committee workflow before wider rollout.
$80,000 to $200,000 for the record, committee workflow, restriction and interchange configuration, exception workflow, downstream publication with drift detection, and reporting. This tier covers most single-system deployments we are asked to scope.
Starting at $200,000 for multi-facility systems with per-site formularies, central governance, multiple EHR instances, and integrated utilisation analytics. Facility count and the number of EHR instances drive the final figure most.
A paid, time-boxed discovery phase delivers a drift audit, committee practice map, drug data strategy, build or configure recommendation, and an itemised fixed-scope estimate. The audit is yours whether or not we build.
Facility count, EHR instances, restriction model complexity, exception volume, and downstream system quality. Legacy dispensing systems raise integration cost more than anything else. Older dispensing platforms often need custom transport built from scratch.
Budget annually for support, EHR upgrade regression testing, and interface monitoring. Drug database subscription and content licensing are quoted separately as vendor costs. We do not mark up vendor data subscriptions.
If you suspect your formulary of record and your EHR disagree, start there. A paid discovery phase gives you a drift audit across your downstream systems, a map of how your P&T cycle actually runs, a drug data strategy, a build or configure recommendation, and an itemised fixed-scope estimate for whatever remains. If the recommendation is to configure what you already own, you keep the audit and spend nothing further with us. Talk to our team about your facility count, your EHR instances, and how formulary status reaches your medication management workflow today.
These are the questions pharmacy directors and P&T chairs ask before scoping formulary work. Several concern boundaries: what the software enforces, what your committee decides, and what remains a pharmacist’s judgement in the moment. Others concern cost of ownership, where the honest answer involves a recurring vendor subscription that has nothing to do with us. Where an answer depends on your specific EHR version, dispensing system, or drug data licence, discovery resolves it quickly, and we would rather set expectations now than after a statement of work. Ask the awkward version first.
No. It records approved therapeutic interchange protocols and surfaces them for pharmacist action. A pharmacist reviews and applies interchange within the approved protocol and documents it. The system does not swap a medication for a patient, and building it to do so would move a clinical judgement into a rules engine where it does not belong.
Formulary management governs which drugs are approved and under what conditions, and publishes that policy. Our computerised provider order entry work covers the ordering interface, prescribing defaults, and order transmission. Formulary status appears inside CPOE, so the two integrate, but they are separate builds with separate owners and separate scopes.
Almost certainly yes, and you should. Curating drug identifiers, classifications, and interaction data internally is a clinical safety liability and a permanent staffing cost. We integrate the commercial database you subscribe to. That subscription is a recurring vendor cost separate from our engineering fee. Every serious formulary platform assumes one.
We will not claim it does. Spend reflects committee decisions, contracting, and prescribing behaviour. What the software provides is visibility into variance, exception patterns, and interchange uptake, so your team can measure against its own baseline and act. The savings, if any, come from decisions people make with that data.
They should not, and we do not build them that way. Restriction logic informs and requires documented justification, but an override path remains available with the reason captured. Hard blocks on medication access create clinical risk and generate workarounds that destroy the data you were trying to collect.
Yes, in the enterprise tier. Per-site formularies with central governance, site-specific restrictions, and separate publication targets are a common requirement for multi-hospital systems and long-term care pharmacy. Complexity sits in reconciliation and reporting rather than in the record itself, so we scope those carefully. Reporting across sites is the piece to specify carefully.
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.