GITNUXSOFTWARE ADVICE
Healthcare MedicineTop 10 Best Health IT Software of 2026
Top 10 health it software for clinics, ranking Epic, Meditech, CareCloud, athenahealth, NextGen Healthcare, and Kareo by workflow fit.
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
CareCloud is the best pick if outpatient clinics want one workflow spine that ties charting, orders, and claims execution together, whereas Epic fits mid-size to enterprise clinics needing deep clinical workflow configuration with controlled integrations.
Editor’s top 3 picks
Three quick recommendations before you dive into the full comparison below — each one leads on a different dimension.
CareCloud
Order-to-medication workflow uses structured orders and e-prescribing within visit documentation.
Built for fits when outpatient clinics need one workflow spine for charting, orders, and claims execution..
athenahealth
Editor pickEHR work queues connect clinical status changes to claim follow-up actions across staff roles.
Built for fits when ambulatory teams want clinical work and revenue-cycle execution aligned through automated tasking..
NextGen Healthcare
Editor pickConfigurable encounter-driven routing and task automation that ties clinical events to follow-ups within ambulatory workflows.
Built for fits when ambulatory groups want shared clinical and operational workflows with configurable automation and external connectivity..
Related reading
Comparison Table
CareCloud
SMBHealthcare software for medical billing, practice management, EHR, and patient experience.
Order-to-medication workflow uses structured orders and e-prescribing within visit documentation.
CareCloud is designed for outpatient operations where clinical intake, structured documentation, and billing steps share the same workflow context. Core capabilities include clinical documentation, order entry with e-prescribing, patient account workflows, and reporting for operational performance. Integration depth is supported through HL7 connectivity and FHIR exchange patterns that allow data flow into and out of the system for participating external applications.
A key tradeoff is that deeper automation depends on configuration choices and template discipline across providers and sites. CareCloud fits clinics that need consistent documentation standards and repeatable charge and coding workflows alongside day-to-day charting, rather than teams that expect heavy customization without governance.
- +Outpatient charting and billing workflows share the same operational context
- +Configurable clinical documentation templates support repeatable provider workflows
- +e-prescribing coverage supports medication order workflows during visits
- +HL7 and FHIR exchange support bidirectional integration with external systems
- –Template governance is required to keep documentation consistent across providers
- –Some specialty workflows may require more configuration to match local practice patterns
- –Reporting depth can depend on how charge and clinical fields are mapped
- –Advanced automation needs careful change control to avoid workflow drift
Ambulatory practice administrators
Reduce rework between charting and billing
Fewer manual handoffs
Multi-provider clinical teams
Standardize documentation across sites
More uniform chart quality
Show 2 more scenarios
Integration teams
Exchange patient and clinical data
Cleaner interoperability pipelines
HL7 interfaces and FHIR exchange support connecting to external systems and registries.
Medical office pharmacists
Manage medication orders during visits
Faster medication reconciliation
e-prescribing is handled directly from the order workflow tied to the encounter.
Best for: Fits when outpatient clinics need one workflow spine for charting, orders, and claims execution.
More related reading
athenahealth
SMBCloud-based healthcare software for electronic health records, medical billing, and patient engagement.
EHR work queues connect clinical status changes to claim follow-up actions across staff roles.
Athenahealth’s ambulatory EHR workflows connect clinical activity to operational execution, including order handling, medication workflows, and appointment and task management. Its interoperability posture uses standardized messaging for exchange and FHIR APIs for pulling and pushing clinical and administrative data to connected systems. Operational automation shows up in guided next steps for front desk, care teams, and revenue cycle staff tied to patient status and work queues. Audit and access controls support clinic governance by limiting who can view and act on records and workflows.
A key tradeoff is dependency on disciplined configuration and staff process adoption, because automation and work queues only produce consistent throughput when teams follow defined operational patterns. Athenahealth fits best for mid-size ambulatory practices that want tight alignment between clinical documentation and billing operations rather than separating EHR use from revenue cycle execution.
- +Clinical tasks route into revenue cycle work queues for faster follow-through
- +FHIR access supports connected apps for patient-facing and operational data flows
- +Built-in automation for reminders and task assignment reduces manual coordination
- +Interoperability supports standard message exchange for external system connectivity
- –Work queue behavior depends on consistent configuration and staff adherence
- –Reporting depth can require specialist understanding of workflow states
- –Some specialty documentation paths may need extra configuration effort
- –API-based integrations can require change management as workflows evolve
Practice operations managers
Automate work queues tied to patient status
Fewer missed follow-ups
Care coordination teams
Coordinate orders and medication processes
More complete medication workflows
Show 2 more scenarios
Integration engineers
Connect external apps using FHIR access
Lower integration glue code
FHIR endpoints support data exchange for apps that need patient and clinical updates.
Revenue cycle staff
Route claim tasks from clinical events
Quicker claim resolution
Claim follow-up tasks use clinical and scheduling triggers to prioritize next actions.
Best for: Fits when ambulatory teams want clinical work and revenue-cycle execution aligned through automated tasking.
NextGen Healthcare
SMBHealthcare software for ambulatory electronic health records, practice management, patient experience, and interoperability.
Configurable encounter-driven routing and task automation that ties clinical events to follow-ups within ambulatory workflows.
NextGen Healthcare is a fit for ambulatory organizations that need a single record workflow across scheduling, documentation, prescribing, and patient communications. Administration supports role-based access configuration and audit-oriented activity tracking for operational governance. Integration is handled through HL7-oriented interfaces and FHIR access patterns used for pulling or pushing clinical data to external systems.
A key tradeoff is that deeper workflow automation depends on careful configuration of templates and routing rules, which increases upfront analyst time. NextGen Healthcare is most effective when the organization has stable provider workflows and uses standardized documentation and order patterns across specialties.
- +Ambulatory workflows include built-in orders and encounter documentation templates
- +Interoperability supports external data exchange through HL7 and FHIR interfaces
- +Administration covers RBAC configuration with audit visibility for operational oversight
- +Automation uses configurable routing and task triggers tied to clinical events
- –Workflow automation needs disciplined template and configuration management
- –Multi-module deployments can require more governance to keep roles aligned
- –Specialty deviations may need additional build work to match documentation patterns
Ambulatory practices
Standardizing documentation and order workflows
More consistent chart completion
Integration teams
Connecting labs, imaging, and referral systems
Fewer manual handoffs
Show 2 more scenarios
Clinic operations leaders
Governing access and activity visibility
Better compliance control
RBAC configuration plus audit-oriented activity tracking supports controlled operational administration.
Care coordination managers
Automating follow-ups from visits
Higher follow-through rates
Configurable automation triggers follow-up tasks based on encounter events and documentation status.
Best for: Fits when ambulatory groups want shared clinical and operational workflows with configurable automation and external connectivity.
Epic
enterpriseEnterprise electronic health record software for hospitals, health systems, and connected care workflows.
Epic’s clinical build model ties orders, documentation, and reusable decision logic into a single configurable workflow experience.
Epic is an enterprise EHR vendor centered on a tightly integrated clinical workflow across inpatient and ambulatory care. Epic’s core strength is its configurable build approach that connects order entry, documentation, and patient context through a consistent internal architecture.
Epic also supports interoperability through HL7 and FHIR interfaces for clinical data exchange and downstream integrations. Epic’s governance model, including role-based access and audit visibility, is geared for multi-department deployment with controlled change management.
- +Highly configurable workflows link documentation, orders, and patient context consistently
- +Interoperability interfaces support both HL7 and FHIR-based integrations
- +Strong access control patterns help manage user permissions across departments
- +Extensibility supports integration use cases beyond core clinical modules
- –Implementation and ongoing build governance require sustained operational discipline
- –Custom workflow changes often need careful testing to avoid downstream regressions
- –Tooling can feel heavyweight for small clinics with narrow process needs
- –Integration projects may depend on specialized interface and mapping work
Best for: Fits when mid-size to enterprise clinics need deep clinical workflow configuration and controlled integrations.
Oracle Health
enterpriseHealth IT platform spanning electronic health records, population health, and healthcare data infrastructure.
Enterprise care coordination workflows can be orchestrated through configurable automation tied to linked clinical data across systems.
Oracle Health records and clinical data across enterprise workflows, with an emphasis on interoperability through documented integration paths. Core modules cover EHR and related clinical documentation, care management workflows, and population-oriented reporting use cases.
The solution’s integration focus centers on connecting to external systems via HL7 and FHIR interfaces, then coordinating those data flows with configurable automation. Governance relies on administrative controls such as RBAC and audit log capture to support regulated operations.
- +FHIR-first integration pattern supports external clinical and analytics systems
- +Audit log coverage supports compliance workflows across user actions
- +RBAC options support separation of duties across clinical and admin roles
- +Configurable workflow automation reduces manual data movement
- –Requires tighter integration governance to keep interface mappings consistent
- –Clinicians may face more configuration steps for common documentation patterns
- –Enterprise deployments often need dedicated implementation resources
- –Reporting configuration can be slower than lighter EHR models
Best for: Fits when large clinical organizations need EHR workflows tied to enterprise integrations and audit-ready operations.
Veradigm
API-firstHealthcare technology products for practice operations, data, analytics, and networked clinical workflows.
Standards-driven integration layer designed to move orders and results across ambulatory and specialty workflows with less manual reconciliation.
Veradigm is a healthcare IT software vendor used by clinical organizations and health systems to support EHR-adjacent workflows and operational reporting. Its product set is built around interoperability connections, order and results data exchange, and configuration for care delivery use cases across ambulatory and specialty settings.
Integration depth shows up in how Veradigm exposes and consumes clinical and administrative data through standards-based interfaces. Automation and governance typically show through configurable workflows and audit-centric operational controls used by managed service implementations.
- +Strong integration focus for exchanging clinical orders and results with external systems
- +Configuration supports different care delivery patterns without custom UI build-outs
- +Operational reporting capabilities align with common quality and performance workflows
- +Interfacing with health information exchange reduces manual data re-entry in many flows
- –Full value depends on integration work with surrounding EHR and middleware components
- –Workflow configuration breadth can increase setup effort for complex organizational roles
- –Some clinical workflow tasks may require external system coordination for completeness
- –Admin tuning for governance and audit expectations can be time-consuming during rollout
Best for: Fits when mid-market clinics need standards-based interoperability and reporting support around their core EHR.
MEDITECH
enterpriseElectronic health record software for hospitals, health systems, and community care organizations.
Deep inpatient workflow configuration that ties order logic and documentation behavior to hospital operational standards.
MEDITECH is a health IT EHR suite focused on deep acute-care workflows and inpatient-to-ambulatory continuity. It supports order entry, medication processes, and clinical documentation tied to structured workflows used in hospital environments.
Integration capability relies on standard healthcare messaging and document exchange patterns used for connectivity to external systems. Admin teams get configuration controls for clinical content behavior and operational governance across facilities running MEDITECH.
- +Strong inpatient workflow coverage for orders, meds, and documentation in acute settings
- +Clinical content configuration supports facility-specific practice patterns and order logic
- +Integration supports common healthcare interchange needs through HL7 interfaces
- +Audit log coverage helps track user activity tied to clinical and administrative changes
- –Workflow depth can increase training time for cross-service teams
- –More complex integrations often require dedicated interface engineering effort
- –Clinical change management can slow down rapid local iterations across facilities
- –Limited app ecosystem depth compared with marketplaces that support many add-ons
Best for: Fits when hospital groups need inpatient workflow depth with controlled clinical configuration across multiple units.
Greenway Health
SMBAmbulatory healthcare software for electronic health records, practice management, and revenue cycle operations.
Configurable outpatient order and workflow automation supports clinic-specific process mapping without custom application development.
Greenway Health is an ambulatory-focused health IT vendor that centers its workflows on everyday clinical operations rather than specialty-only modules. Core capabilities include EHR charting, e-prescribing, clinical documentation tools, and configurable order and workflow support for outpatient care.
Greenway also provides integration paths for data exchange via health information exchange and standards-based messaging, plus connectivity to partner systems used by clinics. Administrative controls and reporting support help clinics manage day-to-day operations across providers, sites, and departments.
- +Strong outpatient workflow coverage across charting, orders, and daily documentation
- +E-prescribing workflow is integrated into routine clinical task flows
- +Integration options support data exchange needs with external health systems
- +Administrative controls help manage provider access across multi-user environments
- –Inpatient and acute-care workflow breadth is limited versus acute-specialized EHRs
- –Higher automation outcomes depend on clinic-specific configuration and ongoing governance discipline
- –Advanced clinical decision support depth is thinner than large-suite competitors
- –Some interoperability scenarios require additional partner connectivity work
Best for: Fits when outpatient clinics need configurable clinical workflows and integrated e-prescribing with practical integration support.
Practice Fusion
SMBCloud-based ambulatory EHR software for charting, e-prescribing, scheduling, and patient management.
Chart documentation and visit workflow configuration are designed around fast outpatient use with patient communications built in.
Practice Fusion is an ambulatory EHR used for daily clinical documentation, orders, and patient charting in outpatient settings. The product focuses on configurable clinical workflow, including problem list management and medication reconciliation within visits.
Practice Fusion also provides patient-facing features such as scheduling and communications, plus reporting for quality and compliance workflows. Integration with external systems relies on its interoperability tooling and available API and data exchange options for exchanging clinical information.
- +Configurable clinical workflow supports repeatable outpatient visit patterns
- +Patient messaging and scheduling help reduce staff coordination work
- +Medication reconciliation features align with common outpatient safety checks
- +Reporting covers common quality and documentation needs for clinics
- –Workflow automation depth is limited compared with enterprise EHR stacks
- –Advanced interoperability tooling can require more integration effort than competitors
- –Admin governance controls and audit capabilities are not as granular as top EHRs
- –Order set and CDS breadth is narrower for complex specialty workflows
Best for: Fits when outpatient clinics need an ambulatory EHR with visit documentation and basic interoperability for external systems.
RXNT
SMBCloud-based healthcare software for EHR, practice management, billing, scheduling, and e-prescribing.
Template-driven ambulatory documentation with medication and problem workflows tied into the encounter flow.
RXNT is designed for ambulatory clinical documentation and workflow for specialty practices. It centers on structured problem lists, medication workflows, and encounter documentation designed for repeatable visits.
RXNT’s integration approach is built around an interoperability layer for exchanging clinical data with surrounding systems and supporting clinical reporting and referral workflows. Clinics comparing EHR and EMR options usually evaluate RXNT based on how well its ambulatory documentation model fits their templates and how much API and integration work is required for their existing infrastructure.
- +Ambulatory encounter templates support consistent documentation across recurring visit types
- +Medication and reconciliation workflows reduce missed steps during charting
- +Structured problem list handling improves visit-to-visit continuity
- +Interoperability focus helps connect clinical data to external workflows
- –Specialty and template configuration can require clinical governance discipline
- –Depth of advanced CDS and complex inpatient order workflows may not match inpatient-focused EHRs
- –API coverage needs validation for each surrounding system because feature parity varies by integration type
- –Reporting workflows may need customization to mirror existing internal measures
Best for: Fits when ambulatory teams need structured documentation and medication workflows tied to consistent visit templates.
Conclusion
After evaluating 10 healthcare medicine, CareCloud 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 health it software
Clinics evaluating health IT software face a tradeoff between outpatient workflow consistency and enterprise integration control, and this guide covers CareCloud, athenahealth, NextGen Healthcare, Epic, Oracle Health, Veradigm, MEDITECH, Greenway Health, Practice Fusion, and RXNT. Each tool is reviewed with a focus on how clinical tasks, orders, and documentation move through real operational work queues and interfaces.
The selection set emphasizes integration depth through named API access patterns and messaging standards, plus automation and governance controls that keep templates, workflows, and interface mappings from drifting across teams. CareCloud leads the ranking, followed by athenahealth and NextGen Healthcare, with Epic and Oracle Health positioned for deeper configuration and audit-ready enterprise operations.
Health IT software for clinics: EHR workflows, integration APIs, and governance
Health IT software for clinics is the clinical workflow system that coordinates documentation, orders, results, and medication steps across ambulatory or inpatient deployments. It is measured by how clinical changes trigger downstream work, how orders and results cross system boundaries, and how administrators control template and workflow configuration.
In this clinic-focused set, CareCloud ties structured order-to-medication workflow to e-prescribing inside visit documentation, while athenahealth connects clinical status changes to claim follow-up actions through work queues. NextGen Healthcare and Epic push encounter-driven routing and configurable workflow logic so the same operational spine can manage clinical events and follow-ups while maintaining governed configuration.
Clinic workflow execution features for EHR and health IT integration
Care teams also need administrative control so templates, workflow states, and interface behavior do not drift across providers and sites. The strongest options in this set tie configuration discipline to repeatable documentation patterns and governed interoperability workflows.
Order-to-medication and visit-embedded e-prescribing workflow
CareCloud uses a structured order-to-medication workflow inside visit documentation with e-prescribing execution tied to the same operational context.
Clinical status work queues tied to claims follow-up
athenahealth routes clinical task outcomes into revenue cycle work queues so staff roles can complete follow-up actions from the same clinical trigger stream.
Encounter-driven routing and task automation across ambulatory workflows
NextGen Healthcare and Epic both support encounter-driven routing, but NextGen Healthcare emphasizes configurable routing and task automation that ties clinical events to follow-ups within ambulatory workflows.
Clinical build model that links orders, documentation, and reusable decision logic
Epic combines order placement, documentation, and reusable decision logic into a single configurable workflow experience with controlled integration points.
FHIR-first integration pattern plus audit log coverage for compliance workflows
Oracle Health pairs FHIR-first integration behavior with audit log coverage so user actions can be tracked during enterprise care coordination operations.
Standards-driven integration layer for exchanging orders and results
Veradigm focuses on standards-based interoperability so orders and results move across ambulatory and specialty workflows with less manual reconciliation.
Choose based on workflow spine, configuration governance, and integration automation depth
The second choice axis is how much governance the organization can sustain for templates, workflow states, and interface mappings. Epic and Oracle Health prioritize build governance and operational discipline, while CareCloud, athenahealth, and NextGen Healthcare focus on configurable clinic workflow execution with automation surfaces that still require consistent configuration behavior.
Map the primary clinical-to-operations handoff to the system that owns it
If the core requirement is order-to-medication execution during the visit, CareCloud fits because it connects structured orders to medication steps and e-prescribing within visit documentation. If the core requirement is clinical status triggering revenue cycle follow-up, athenahealth fits because work queues link clinical task outcomes to claim follow-up actions.
Decide whether encounter routing should be configured as ambulatory automation or enterprise build logic
If ambulatory teams need configurable encounter-driven routing and task automation with an external connectivity posture, NextGen Healthcare fits because it ties clinical events to follow-ups using configurable automation. If mid-size to enterprise clinics need a deeper clinical build model that ties orders, documentation, and reusable decision logic into one governed workflow experience, Epic fits.
Set an integration automation target before comparing interoperability layers
If interoperability should be anchored by standards-driven movement of orders and results, Veradigm fits because it is built as an integration layer that reduces manual reconciliation work around an existing EHR. If integration must be orchestrated with enterprise care coordination flows tied to linked clinical data, Oracle Health fits because it orchestrates configurable automation across integrated systems.
Evaluate governance effort using the organization’s template and workflow discipline
CareCloud requires template governance to keep documentation consistent across providers, which matters when many clinicians share documentation templates. Epic and Oracle Health both require sustained build and integration governance discipline, and complex custom workflow changes should be tested to avoid downstream regressions.
Stress-test inpatient coverage if the deployment includes acute units
If inpatient depth is required for hospital operational standards, MEDITECH fits because it ties inpatient workflow configuration to order logic and documentation behavior across units. If the requirement is mainly outpatient, Greenway Health and Practice Fusion fit because their strengths center on outpatient workflow coverage, and acute breadth is limited versus inpatient-focused EHRs.
Clinic teams matched to workflow execution style
Teams also need to match the deployment to the product’s workflow breadth. Options oriented toward ambulatory execution focus on visit templates and encounter automation, while inpatient-oriented options focus on unit-level order logic and documentation behavior.
Outpatient clinics that want one workflow spine from documentation to e-prescribing
CareCloud supports structured order-to-medication workflows within visit documentation with e-prescribing execution tied to charting so clinicians can keep execution inside the same operational context.
Ambulatory teams that need clinical work queues that drive revenue cycle follow-through
athenahealth routes clinical task outcomes into revenue cycle work queues so staff roles can complete claim follow-up actions from the same clinical trigger stream.
Ambulatory groups that need configurable encounter routing and follow-up automation
NextGen Healthcare provides encounter-driven routing and task automation so clinical events connect to follow-ups while interoperating through HL7 and FHIR interfaces.
Clinics that want deep configurable build logic with governed workflow experience
Epic supports highly configurable workflows that link documentation, orders, and patient context with interoperability interfaces using HL7 and FHIR-based integration patterns.
Hospital groups that prioritize inpatient workflow depth across units
MEDITECH is built around inpatient workflow configuration with facility-specific practice patterns so order logic and documentation behavior align with acute operational standards.
Common procurement and rollout pitfalls for clinic health IT deployments
Another common failure mode comes from choosing the wrong workflow breadth for the deployment scope. Ambulatory-first options can fit outpatient coverage but may fall short on acute workflow depth when hospital units are included.
Selecting a system that automates clinical-to-operations routing but not preparing teams for workflow state configuration discipline
athenahealth work queue behavior depends on consistent configuration and staff adherence, so work queue outcomes can degrade when workflow states are inconsistently followed.
Ignoring governance needs for shared documentation templates and cross-provider consistency
CareCloud requires template governance to keep documentation consistent across providers, which means template drift can create inconsistent chart outputs and downstream workflow behavior.
Assuming deep inpatient workflow coverage when the deployment is primarily outpatient
Greenway Health and Practice Fusion focus on outpatient workflow coverage, and inpatient and acute breadth is limited versus acute-specialized EHRs and inpatient-focused configurations.
Underestimating the testing and change control needed for configurable workflow builds
Epic custom workflow changes need careful testing to avoid downstream regressions, which increases rollout time when workflows are heavily customized.
Buying an integration-focused layer without staffing for real interface work and surrounding middleware alignment
Veradigm full value depends on integration work with the surrounding EHR and middleware components, so expected reconciliation reduction can fail when integration plumbing is not resourced.
How We Selected and Ranked These Tools
We evaluated CareCloud, athenahealth, NextGen Healthcare, Epic, Oracle Health, Veradigm, MEDITECH, Greenway Health, Practice Fusion, and RXNT using workflow execution features, automation behavior, and integration surfaces. Features accounted for 40% of the score because each tool was judged on how clinical changes produce downstream work through order workflows, encounter automation, and work queue behavior.
Ease of use and value each accounted for 30% of the score because rollout friction and operational overhead were measured against the governance burden created by templates, workflow states, and interface mappings. CareCloud earned the top rank based on its structured order-to-medication workflow inside visit documentation with e-prescribing execution and repeatable template-driven provider workflows.
Frequently Asked Questions About health it software
How do Epic and MEDITECH differ in supporting inpatient-to-ambulatory workflow continuity?
Which tools support FHIR-based exchange for integrating an ambulatory EHR with external patient portals and practice systems?
How does order-to-medication automation work in CareCloud compared with Greenway Health?
When clinics need audit visibility and role-based access for multi-department operations, how do Epic and Oracle Health handle admin controls?
What breaks if a clinic expects FHIR access and finds an HL7-first integration path instead?
How do athenahealth and NextGen Healthcare connect clinical workflow changes to revenue-cycle follow-ups?
How does RBAC provisioning and access control typically differ when configuring Epic versus smaller ambulatory-focused platforms like Practice Fusion?
Which systems are better aligned to specialty-template documentation when problem lists and medication workflows must stay consistent?
How should clinics plan data migration when switching from an existing ambulatory EHR to Oracle Health or Veradigm?
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→