GITNUXSOFTWARE ADVICE
Healthcare MedicineTop 10 Best Electronic Health Record Systems Software of 2026
Ranking roundup of electronic health record systems software for healthcare teams, with evaluations of NextGen Healthcare and key tradeoffs.
How we ranked these tools
Core product claims cross-referenced against official documentation, changelogs, and independent technical reviews.
Analyzed video reviews and hundreds of written evaluations to capture real-world user experiences with each tool.
AI persona simulations modeled how different user types would experience each tool across common use cases and workflows.
Final rankings reviewed and approved by our editorial team with authority to override AI-generated scores based on domain expertise.
Score: Features 40% · Ease 30% · Value 30%
Gitnux may earn a commission through links on this page — this does not influence rankings. Editorial policy
NextGen Healthcare is the best fit for multi-site ambulatory teams that need governed orders and repeatable documentation structures, whereas MEDITECH works better when acute-care groups must standardize inpatient charts with tightly governed workflows across departments.
Editor’s top 3 picks
Three quick recommendations before you dive into the full comparison below — each one leads on a different dimension.
NextGen Healthcare
Order set governance ties standardized ordering logic to role-controlled workflow paths and audit trails.
Built for fits when multi-site ambulatory teams need governed orders and repeatable documentation structures..
MEDITECH
Editor pickConfigurable clinical templates and document structures tailored to inpatient encounters across multiple service lines.
Built for fits when acute-care teams need governed inpatient workflows and chart standardization across departments..
Veradigm
Editor pickCross-setting clinical workflow configuration that keeps documentation and orders consistent across encounter types.
Built for fits when hospitals or specialty groups need coordinated inpatient and ambulatory workflows with strong governance controls..
Comparison Table
NextGen Healthcare
SMBElectronic health record and practice management software focused on ambulatory and specialty practices.
Order set governance ties standardized ordering logic to role-controlled workflow paths and audit trails.
NextGen Healthcare is geared to organizations running multi-site ambulatory operations and needing consistent encounter documentation structures across departments. The system provides discrete capture paths for medications, problems, and orders, which supports downstream reporting and clinical handoffs. Governance is stronger than typical document-heavy EHRs because configuration can define encounter note types and order set behavior under defined roles.
A practical tradeoff is that deeper automation requires front-loaded configuration to align templates, encounter types, and governed orders with local clinical practice. NextGen fits well when clinics or hospitals need repeatable documentation and order workflows across teams, while integration work relies on system interfaces that connect to patient portals, health information exchange, and adjacent clinical applications.
- +Configurable encounter note types support consistent documentation across sites
- +Medication reconciliation and order workflows reduce handoff gaps
- +Governed order logic supports standardized prescribing and treatment plans
- +Integration patterns support HL7-based messaging into connected systems
- –Template and workflow alignment needs structured implementation planning
- –Some advanced automation behaviors depend on governed configuration
- –Role-based workflow tuning can take multiple iteration cycles
- –Cross-setting workflows may require additional training for staff
Multi-site ambulatory practices
Standardize visit documentation templates
Fewer documentation variations
Hospital outpatient departments
Reduce medication reconciliation failures
Fewer medication discrepancies
Show 2 more scenarios
Care management teams
Manage orders across roles
More consistent care plans
Governed order workflows route clinical actions based on configured role permissions and templates.
Integration engineers
Connect clinical systems for exchange
Lower interface rework
FHIR-oriented integration patterns and HL7 messaging support data exchange with connected applications.
Best for: Fits when multi-site ambulatory teams need governed orders and repeatable documentation structures.
MEDITECH
enterpriseHospital and health system EHR software with clinical, financial, and patient engagement modules.
Configurable clinical templates and document structures tailored to inpatient encounters across multiple service lines.
MEDITECH is often evaluated for complex inpatient environments where care teams need consistent chart structure, order placement, and medication administration workflows. The product supports structured encounters, configurable document types, and governance-oriented setup for order sets and clinical templates used across departments. System admins get control over user roles, audit visibility, and operational settings needed to run long-lived clinical deployments. Integration typically centers on HL7 interfaces plus clinical summary exchange artifacts for sharing care context with outside systems.
A key tradeoff is that large configuration changes can require coordinated governance work, which slows rapid workflow experimentation compared with systems that rely more on highly modular tooling. MEDITECH tends to work best for organizations migrating from legacy records where document workflows and orders must map cleanly into existing clinical processes. It also fits teams that value standardization across units and can staff analysts to maintain configuration as clinical policies evolve.
- +Strong inpatient workflow coverage for orders, results, and medication administration
- +Configurable document types and encounter structures support standardized documentation
- +Governed order sets help reduce cross-unit practice variation
- +Integration support via HL7 interfaces and clinical summary export
- –Deep configuration can slow turnaround for frequent workflow changes
- –Some workflows depend on site-specific governance and analyst support
- –Interface-heavy deployments require careful interface mapping and testing
- –User experience can feel complex for clinicians new to the system
Acute care IT and analysts
Standardize inpatient order and documentation
Lower variation across departments
Hospital clinical operations leads
Coordinate medication administration workflows
More consistent medication process
Show 2 more scenarios
Integration engineers
Connect external labs and imaging systems
Fewer integration gaps
Implement HL7 interfaces to route orders and results while maintaining clinical context for care teams.
Care management teams
Share discharge and summary information
Faster handoffs
Use clinical summary exports to support external providers receiving structured care context.
Best for: Fits when acute-care teams need governed inpatient workflows and chart standardization across departments.
Veradigm
SMBAmbulatory EHR and practice technology platform serving physician practices and healthcare networks.
Cross-setting clinical workflow configuration that keeps documentation and orders consistent across encounter types.
Veradigm is commonly evaluated in systems that need coordinated inpatient and ambulatory workflows with shared patient context across service lines. The product supports encounter documentation and structured order entry so downstream tasks like results review, medication reconciliation, and discharge planning can follow the same clinical thread. Exchange-oriented implementations use standard document formats for sharing patient summaries and clinical documents with external systems.
A frequent tradeoff is that deep workflow standardization depends on upfront governance for templates, order sets, and local documentation rules. Veradigm fits best when a hospital or multi-specialty network already plans for disciplined content maintenance and change control across sites. It also suits teams that need integration depth across internal departments rather than isolated clinic-level EHR replacement.
- +Configurable clinical documentation workflows across departments
- +Strong inpatient-to-ambulatory continuity in patient context
- +Standards-based clinical document exchange for referral sharing
- +Guided medication workflows aligned to reconciliation tasks
- –Change control for templates and order sets can be heavy
- –Some specialty workflows need configuration and training to match practice
Hospital informatics teams
Standardize orders across service lines
Fewer order workflow variations
Specialty clinics
Maintain continuity after referrals
Faster referral handoffs
Show 1 more scenario
Care management teams
Run medication reconciliation workflows
More consistent reconciliation completion
Guided medication steps align reconciliation timing with encounter transitions.
Best for: Fits when hospitals or specialty groups need coordinated inpatient and ambulatory workflows with strong governance controls.
athenahealth
SMBCloud-based EHR, practice management, and patient engagement software for ambulatory care.
Workflow automation that ties documentation, orders, and operational tasks to measurable execution checkpoints.
athenahealth focuses on ambulatory and hospital workflow orchestration using a large third-party integration footprint rather than a single internal toolkit. Core capabilities include clinical documentation for encounter notes, longitudinal problem and medication workflows, order entry, and electronic prescribing, plus patient communication via portal and messaging.
Automation centers on guided revenue and clinical operations tasks tied to orders, results, and documentation status. Integration depth is driven by an established API surface and a high-volume connectivity approach with health information exchange and partner systems.
- +Strong workflow automation tied to orders, results, and documentation status
- +Large connectivity footprint for exchanging data with external partners
- +Operational tools for task assignment across clinical and revenue workflows
- +FHIR API support for app integrations and data exchange
- –Configuration and governance are required to keep documentation templates consistent
- –Complexity rises when relying on many external integrations for core workflows
- –Some inpatient workflows can require tighter process alignment than teams expect
- –UI efficiency depends on staff training for faster note and order entry
Best for: Fits when practices need cross-system workflow automation and an integration-first EHR approach.
eClinicalWorks
SMBAmbulatory electronic health record and practice management software for physician offices and clinics.
Document templates and encounter note types are designed to support structured documentation and downstream reporting without separate tooling.
eClinicalWorks documents and routes clinical encounters through an ambulatory-first EHR workflow built for scheduling, documentation, orders, and patient communications in one system.
It provides core EHR functions like encounter note types, order entry, e-prescribing, problem list management, and medication reconciliation workflows tied to visits.
Reporting supports regulatory needs through export and attestation-oriented outputs, including CCD export and QPP reporting views.
Integration coverage centers on FHIR and other interface patterns used for health information exchange and system-to-system data exchange.
- +Strong ambulatory encounter documentation workflow with configurable note types
- +Built-in e-prescribing and medication reconciliation tied to visits
- +FHIR API support for app and workflow integration
- +CCD export and reporting outputs support common compliance workflows
- –Advanced automation often depends on configuration and governance discipline
- –Some complex specialty workflows require add-on modules or tighter template work
Best for: Fits when mid-size ambulatory groups need configurable encounter documentation plus integration via FHIR.
Practice Fusion
SMBCloud-based ambulatory EHR software for independent medical practices.
Encounter documentation with configurable document templates and encounter note types that standardize outpatient charts.
Practice Fusion targets ambulatory clinics that need an electronic health record with strong document and order capture workflows. It provides structured encounters, chart notes, e-prescribing, and medication reconciliation support designed around day-to-day outpatient operations.
Integration and automation rely on a published API and extensibility patterns that support external scheduling, reporting, and data movement. Governance features include role-based permissions, audit logging, and export capabilities for common reporting and continuity needs.
- +Order entry and charting workflows fit common outpatient clinic visit patterns
- +E-prescribing and medication reconciliation reduce medication handoff errors
- +Published API supports integration for external apps and reporting pipelines
- +Export and document templates support repeatable encounter documentation
- –Advanced inpatient workflows like eMAR and inpatient administration are not its core focus
- –Long-term configuration and template governance can require ongoing admin attention
- –Deep interoperability depends on which external systems connect through the API
- –Some complex clinical reporting layouts need careful configuration before scaling
Best for: Fits when outpatient teams need fast encounter documentation plus e-prescribing and integration via API.
Greenway Health
SMBAmbulatory EHR and practice management software for primary care and specialty practices.
Template-based clinical documentation and workflow governance that stays consistent across encounter note types.
Greenway Health is an EHR vendor used in ambulatory clinics and behavioral health settings, with configuration patterns that favor service-line workflows. Its charting, orders, and documentation tools are designed to support template-based encounter note types, repeatable medication workflows, and report generation tied to routine clinical operations.
The integration approach is centered on standard exchange mechanisms such as HL7 and C-CDA plus a documented FHIR API surface for application connectivity. Administrative control tends to focus on configuration and governance of templates and clinical workflows rather than on deep custom schema changes.
- +Behavioral health oriented documentation options with structured encounter templates
- +FHIR API support supports integrations that need application-level data access
- +Repeatable clinical templates support consistent documentation and order workflows
- +C-CDA export helps practices with legacy document exchange and reporting flows
- –Complex configuration of templates can slow onboarding for new sites
- –Granular governance for cross-module order set change control is not as explicit
- –Workflow automation depends on configured document and order patterns
- –Migration tooling for eCW style moves often requires careful project scoping
Best for: Fits when clinics need configurable ambulatory and behavioral health workflows with standard exchange and integration support.
CareCloud
SMBCloud-based EHR, practice management, and revenue cycle software for medical groups.
Configurable encounter note types and document templates designed to standardize structured charting across sites.
CareCloud pairs ambulatory workflow tools with revenue-cycle connectivity, which matters for clinics that want documentation, orders, and claim-related data to stay aligned. The EHR supports structured documentation through configurable note templates and encounter settings, plus core clinical operations like e-prescribing and order entry.
Integration coverage is centered on API-based extensibility and standards-oriented interoperability outputs such as C-CDA documents. Automation options focus on rule-driven documentation guidance and configurable workflows rather than pure user-interface scripting.
- +Configurable encounter and note templates reduce rework across provider teams
- +Document workflows connect to order entry tasks during real-time charting
- +C-CDA export supports cross-system document exchange needs
- +API integration supports clinical app attachments and interoperability projects
- –Advanced governance requires deliberate template and workflow design discipline
- –Discrete data import depth can lag beyond EHRs focused on migrations
- –Reporting customization can feel limited without relying on external tooling
- –Some specialty workflows depend on configuration rather than dedicated modules
Best for: Fits when multi-provider ambulatory teams need configurable documentation plus integration-ready interoperability.
Azalea Health
vertical specialistCloud-based EHR and hospital information software for rural providers and community healthcare organizations.
Template and encounter note type configuration that ties documentation structure to repeatable clinic workflows.
Azalea Health is a clinic-focused EHR that centers on structured ambulatory workflows and standardized documentation. Core capabilities include e-prescribing, order entry, visit documentation, and clinical task management tied to encounters.
The product also supports interoperability work through FHIR-based integrations and export formats used for care coordination and reporting needs. Administration focuses on configuration and user permissions to manage roles, templates, and operational governance across teams.
- +Encounter-centered workflow configuration reduces manual chart clean-up
- +FHIR-based integration approach supports external app connectivity
- +Medication workflows support e-prescribing and reconciliation steps
- +Template-driven documentation helps standardize visit note types
- –In-depth inpatient workflows are less complete than acute care EHR suites
- –Advanced governance for large multi-site deployments needs disciplined configuration
Best for: Fits when ambulatory clinics want standardized notes and integrations without building custom workflow tooling.
RXNT
SMBCloud medical software platform with EHR, e-prescribing, scheduling, and billing tools.
Behavioral health–oriented encounter and documentation structures that reduce rework across repeat visit types.
RXNT is an ONC-certified ambulatory EHR focused on behavioral health workflows and clinic operations. It supports charting, scheduling, and clinical documentation across encounter types, with medication and order workflows that connect directly to the visit.
RXNT’s integration story centers on health data exchange and interoperability outputs such as CCD export and HL7 messaging for downstream systems. Admin control is oriented around user roles, audit trails, and document templates to keep documentation consistent across clinicians.
- +Behavioral health charting templates map cleanly to visit documentation
- +Medication workflows support practical reconciliation during encounters
- +Chart content can be reused through document and encounter-type templates
- +Interoperability outputs support health information exchange and data sharing
- –Inpatient acute-care workflow depth is limited versus large hospital EHR suites
- –More complex automation often depends on integration work outside core configuration
Best for: Fits when behavioral health clinics need an ambulatory EHR with consistent documentation templates and practical interoperability.
Conclusion
After evaluating 10 healthcare medicine, NextGen Healthcare stands out as our overall top pick — it scored highest across our combined criteria of features, ease of use, and value, which is why it sits at #1 in the rankings above.
Use the comparison table and detailed reviews above to validate the fit against your own requirements before committing to a tool.
How to Choose the Right electronic health record systems software
Clinics and hospitals evaluating electronic health record systems software usually need the same core capabilities across charting, orders, results, and medication workflows, plus strong governance over how documentation and ordering logic changes over time. This guide frames that decision around integration depth, API and automation surface, and admin and governance controls visible in tools such as Epic, MEDITECH, Allscripts, and NextGen Healthcare.
The narrative also uses what each reviewed system does in real workflows like governed order sets, encounter note type standardization, and inpatient-to-ambulatory continuity so buyers can map implementation effort to expected operating behavior. The covered set includes NextGen Healthcare, MEDITECH, Veradigm, athenahealth, eClinicalWorks, Practice Fusion, Greenway Health, CareCloud, Azalea Health, and RXNT.
Electronic health record systems software for inpatient and ambulatory clinical workflows with governed documentation and orders
Electronic health record systems software manages patient charts, encounter documentation, clinical orders, results display, and medication workflows in a single operational record that supports both inpatient and ambulatory care. The category typically includes configuration for document type templates and encounter note types, plus workflow controls that determine how orders and charting move from draft to finalized states.
NextGen Healthcare differentiates itself with order set governance that ties standardized ordering logic to role-controlled workflow paths and audit trails, which directly affects how multi-site teams change practice. MEDITECH emphasizes governed inpatient workflows with configurable document types and encounter structures across multiple service lines, which matters when standardization must extend from orders to results and medication administration.
Evaluation criteria for electronic health record systems software
Electronic health record systems software should control how clinical documentation and ordering logic move through draft, review, and finalized states across teams. Governance quality matters because template changes and order behavior updates directly affect clinical throughput and audit defensibility.
Buyers should also verify that integration depth and automation reach the workflows that actually move daily work forward. Tools differ in how much ordering, results, and operational task logic can be coordinated internally versus via external integrations.
Order set governance tied to workflow paths and audit trails
NextGen Healthcare ties standardized ordering logic to role-controlled workflow paths and audit trails, which supports repeatable ordering across sites. Veradigm focuses on cross-setting clinical workflow configuration to keep orders and documentation consistent across encounter types.
Inpatient workflow coverage across orders, results, and medication administration
MEDITECH emphasizes governed inpatient workflows with configurable document types and encounter structures across service lines. MEDITECH also supports strong coverage for orders, results, and medication administration in inpatient workflows.
Encounter note type standardization designed for downstream use
eClinicalWorks uses structured document templates and encounter note types designed to support downstream reporting without separate tooling. CareCloud uses configurable encounter note types and document templates to standardize structured charting across sites.
Template and workflow configuration control for multi-site operations
athenahealth ties documentation, orders, and operational tasks to measurable execution checkpoints, which makes workflow state more observable. NextGen Healthcare provides configurable encounter note types that support consistent documentation across sites.
Automation behavior that follows governed configuration
athenahealth provides workflow automation that connects documentation, orders, and operational tasks to execution checkpoints. NextGen Healthcare supports governed configuration for advanced automation behaviors that depend on structured implementation planning.
Decision framework for selecting an electronic health record system
Selection should start with where governance must be enforced and which workflows require inpatient versus ambulatory depth. The right choice depends on whether the organization expects standardized ordering and documentation logic to be enforced through controlled workflow paths or through broader template configuration.
Buyers should also map implementation effort to the system’s configuration model. Tools that rely on governance and template alignment usually require more structured rollout to prevent inconsistency across sites and encounter types.
Choose the governance model that matches change control needs
If standardized ordering logic must follow role-controlled workflow paths with audit trails, NextGen Healthcare aligns best with that governance requirement. If governance is primarily about keeping documentation and orders consistent across different encounter types, Veradigm’s cross-setting configuration approach is the closer match.
Validate inpatient workflow depth before optimizing for ambulatory usability
If acute-care needs include governed inpatient workflows across orders, results, and medication administration, MEDITECH is the priority candidate. If inpatient depth is secondary to coordinated inpatient-to-ambulatory continuity with shared patient context, Veradigm fits that continuity emphasis.
Standardize documentation structures around how reports and handoffs work
If structured documentation templates must support downstream reporting without extra tooling, eClinicalWorks is built around that template-first documentation model. If multi-provider ambulatory teams need configurable documentation templates that connect real-time charting to order entry tasks, CareCloud matches that operational workflow.
Decide how much automation should be managed internally versus via integrations
If workflow automation must tie documentation and orders to measurable execution checkpoints, athenahealth supports that execution-state automation inside the product. If core automation should remain consistent across templates and governed configuration, NextGen Healthcare and MEDITECH both require structured template governance to keep advanced behaviors stable.
Assess whether configuration complexity aligns with available admin capacity
If the organization can staff analysts for deep configuration and site-specific governance support, MEDITECH handles deep inpatient workflow standardization. If the organization expects faster turnaround for frequent workflow changes, NextGen Healthcare’s governance model still requires planning for template and workflow alignment to avoid slow alignment cycles.
Check behavioral health fit when templates must match visit patterns
If behavioral health oriented documentation structures must reduce rework across repeat visit types, RXNT is designed around that ambulatory documentation need. If clinics need configurable ambulatory and behavioral health workflows with structured encounter templates and FHIR-based integration support, Greenway Health matches that template governance focus.
Who should buy these electronic health record systems
Different electronic health record systems succeed when governance priorities and workflow depth match organizational delivery. Buyers should align system configuration style with how order sets, encounter notes, and inpatient administration need to behave across teams.
Tool selection also depends on whether the organization runs multi-site ambulatory operations, acute inpatient departments, or behavioral health clinics that depend on encounter-centered documentation.
Multi-site ambulatory clinics with repeatable ordering and documentation requirements
NextGen Healthcare supports governed order sets tied to role-controlled workflow paths and audit trails, which helps standardize ordering across sites. eClinicalWorks supports configurable encounter note types that standardize documentation for downstream reporting.
Hospitals and acute-care teams that need governed inpatient workflows
MEDITECH is built for governed inpatient workflows with configurable document types and encounter structures across service lines. MEDITECH also emphasizes inpatient coverage for orders, results, and medication administration.
Organizations that must coordinate inpatient-to-ambulatory continuity across encounter types
Veradigm is designed for cross-setting workflow configuration that keeps documentation and orders consistent across encounter types. The tool’s emphasis on coordinated inpatient and ambulatory workflows supports continuity in patient context.
Clinics that require documentation templates tied to execution checkpoints
athenahealth ties documentation, orders, and operational tasks to measurable execution checkpoints, which improves visibility into workflow state. The approach is strongest when external partner connectivity is a key part of daily operations.
Behavioral health clinics focused on ambulatory encounter documentation
RXNT provides behavioral health oriented encounter and documentation structures that map cleanly to visit documentation needs. Greenway Health offers behavioral health oriented documentation options with structured encounter templates plus FHIR API support for application-level data access.
Common pitfalls when buying electronic health record systems software
Many buying mistakes come from misaligning governance expectations with the system’s configuration workload. Template and workflow alignment can determine whether documentation stays consistent across sites or degrades into manual cleanup and rework.
Mistakes also happen when buyers assume inpatient capabilities match ambulatory emphasis without validating medication administration depth and inpatient order workflows.
Assuming template standardization happens automatically without a governance rollout plan
NextGen Healthcare and eClinicalWorks both depend on structured template and workflow alignment to keep advanced behaviors consistent across sites. Buyers should plan rollout sequencing and template ownership to avoid misalignment across encounter note types.
Evaluating inpatient workflows only by documentation screens
MEDITECH emphasizes inpatient workflow coverage for orders, results, and medication administration, which needs demonstration during inpatient workflow validation. Tools that focus on ambulatory documentation may not match inpatient administration depth.
Underestimating how configuration complexity affects change turnaround
MEDITECH’s deep configuration can slow turnaround for frequent workflow changes and may require site-specific governance and analyst support. athenahealth increases complexity when organizations rely on many external integrations for core workflows.
Treating behavioral health documentation fit as a generic template requirement
RXNT maps behavioral health charting templates cleanly to visit documentation structures, which reduces rework when repeat visit types dominate. Greenway Health provides behavioral health oriented documentation options with structured encounter templates that need configuration discipline.
How We Selected and Ranked These Tools
We evaluated NextGen Healthcare, MEDITECH, Veradigm, athenahealth, eClinicalWorks, Practice Fusion, Greenway Health, CareCloud, Azalea Health, and RXNT by scoring feature coverage at 40%, ease of workflow configuration at 30%, and value for operational fit at 30%. Feature coverage prioritized order and documentation governance, encounter note type standardization, and inpatient versus ambulatory workflow depth across the tools’ core strengths.
Ease and value focused on how configuration and governance expectations show up in day-to-day execution and change turnaround. NextGen Healthcare earned the top rank by combining order set governance tied to standardized ordering logic, role-controlled workflow paths, and audit trails with configurable encounter note types that support consistent documentation across sites.
Frequently Asked Questions About electronic health record systems software
How do Epic, MEDITECH, NextGen Healthcare, and eClinicalWorks differ in supporting integrations through FHIR and HL7?
Which EHR systems provide governed order logic tied to configurable templates and workflow paths for clinics and hospitals?
When is CCD export used as a clinical document exchange output, and which vendors support it in this set?
What breaks if data migration arrives as documents instead of discrete data fields for medication reconciliation and problem list updates?
Which products expose a published API surface for automation and external system connections?
How do admin controls and RBAC typically affect clinicians’ ability to standardize documentation across encounter note types?
Where do audit logs and audit-friendly activity trails fit into EHR security and compliance workflows?
What tradeoff occurs when an EHR emphasizes guided workflow configuration over custom schema changes?
How should implementers plan for medication reconciliation workflow alignment during go-live across ambulatory and acute care?
Tools reviewed
Primary sources checked during evaluation.
Referenced in the comparison table and product reviews above.
Keep exploring
Comparing two specific tools?
Software Alternatives
See head-to-head software comparisons with feature breakdowns, pricing, and our recommendation for each use case.
Explore software alternatives→In this category
Healthcare Medicine alternatives
See side-by-side comparisons of healthcare medicine tools and pick the right one for your stack.
Compare healthcare medicine tools→