GITNUXSOFTWARE ADVICE
Healthcare MedicineTop 10 Best Emr Medical Records Software of 2026
Top 10 ranking of emr medical records software for clinics, comparing Epic, athenaOne, and Tebra on features, pricing, and usability.
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
Epic is the best fit for large hospitals and health systems that need governed, cross-department workflows with deep interoperability, whereas Tebra suits outpatient teams that want configurable documentation and strong HL7 v2 and FHIR integration.
Editor’s top 3 picks
Three quick recommendations before you dive into the full comparison below — each one leads on a different dimension.
Epic
Epic’s enterprise governance model combines role-based clinical access with comprehensive audit log trails across configured workflows.
Built for fits when large health systems need governed workflows plus deep interoperability across departments..
athenaOne
Editor pickRules-based charting and workflow actions that apply automatically during encounter documentation based on configurable triggers.
Built for fits when multi-clinic practices need automated visit workflows tied to documentation and downstream billing..
Tebra
Editor pickAudit logging with role-based clinical access tracks who viewed or changed chart data during outpatient encounters.
Built for fits when outpatient practices need configurable documentation plus HL7 v2 and FHIR integration..
Related reading
Comparison Table
Epic
enterpriseEpic provides enterprise electronic medical records for hospitals, health systems, and large medical groups.
Epic’s enterprise governance model combines role-based clinical access with comprehensive audit log trails across configured workflows.
Epic runs clinical documentation and ordering workflows at the point of care, including encounter note capture, structured orders, and medication-related documentation used during inpatient and outpatient episodes. Enterprise teams also rely on Epic’s built-in analytics and reporting features to support operational monitoring and quality measurement across sites. For interoperability, Epic supports FHIR APIs and also supports document-style exchange for clinical summaries and records transfers.
Epic’s main tradeoff is the configuration and change-management effort required to tailor workflows and interfaces for each organization. Epic fits environments that expect heavy integration work with radiology, labs, and identity systems, and where governance teams can manage RBAC, audit log review, and ongoing release updates. Epic is also a strong fit for hospitals with complex inpatient workflows plus ambulatory scheduling and documentation needs.
- +Enterprise workflow depth for inpatient and ambulatory documentation
- +FHIR API and document exchange support for multi-vendor interoperability
- +Configurable clinical processes with governed access controls
- +Audit log coverage for traceability across clinical and admin actions
- –High implementation and change-management workload for workflow tailoring
- –Customization often depends on coordinated build and testing cycles
- –Interface projects can require specialized integration resources
- –User experience can vary by configured workflows and templates
Inpatient care teams
Manage orders and documentation daily
Fewer order transcription errors
Ambulatory operations
Standardize documentation across clinics
More consistent clinical capture
Show 2 more scenarios
Integration teams
Connect labs and imaging systems
Faster data exchange
Epic supports FHIR API integrations and interface configuration for external system connectivity.
Compliance and governance
Track actions across users
Better traceability for audits
Epic provides audit log trails that support internal review of clinical and administrative changes.
Best for: Fits when large health systems need governed workflows plus deep interoperability across departments.
More related reading
athenaOne
enterpriseathenaOne combines electronic health records, practice management, and medical billing.
Rules-based charting and workflow actions that apply automatically during encounter documentation based on configurable triggers.
athenaOne is built for outpatient settings that need tight coordination between front desk operations, clinical documentation, and downstream claim and billing tasks. The system supports structured encounter workflows, configurable forms, and extensive charting shortcuts for visit types that repeat across providers and locations. Automation features like rules-based actions and guided documentation help standardize outcomes across teams.
A tradeoff is that a strong configuration and governance process is needed to keep templates, prompts, and automated rules consistent across sites and provider groups. athenaOne fits best when a practice can dedicate analysts or administrators to workflow design and ongoing content maintenance.
- +Rules-driven documentation tools reduce repeated charting during visits
- +Shared workflows connect scheduling, documentation, and billing tasks
- +Interoperability interfaces support clinical data exchange with outside systems
- +Cross-team automation supports consistent care processes across locations
- –Advanced automation requires ongoing configuration discipline
- –Template and workflow setup can be time-consuming during initial rollout
- –Clinical workflow depth can feel complex for teams needing minimal configuration
- –Reporting and analytics depend on well-maintained documentation structures
Practice operations leaders
Standardize visit workflows across clinics
Fewer documentation variations
Physician documentation teams
Speed up encounter note creation
Shorter charting time
Show 2 more scenarios
Revenue cycle teams
Coordinate clinical and billing handoffs
Cleaner handoffs
Shared workflows connect encounter completion to downstream billing work.
Integration and IT teams
Connect external clinical and reporting systems
Lower integration friction
Interoperability interfaces support data exchange for labs, referrals, and reporting systems.
Best for: Fits when multi-clinic practices need automated visit workflows tied to documentation and downstream billing.
Tebra
SMBTebra provides electronic health records, practice operations, billing, and patient acquisition tools.
Audit logging with role-based clinical access tracks who viewed or changed chart data during outpatient encounters.
Tebra is built to support routine outpatient charting and care coordination with encounter notes that can be shaped to local documentation needs. Practices can operationalize front office work through scheduling and task workflows that tie into the clinical day. Data exchange options include HL7 v2 messaging and FHIR APIs for integration with downstream systems and health information exchange.
A tradeoff appears in deeper specialty workflows where configuration effort can be higher than expected, especially when documentation and orders need tight alignment to local policies. Tebra fits best for outpatient groups that want a single record system plus integration options for messaging and API-based data movement.
- +FHIR APIs support integration with external clinical and administrative systems
- +Role-based clinical access and audit logging support governance for chart changes
- +Configurable encounter note documentation supports specialty-specific templates
- +HL7 v2 messaging supports common interoperability patterns for health systems
- –Specialty documentation models may require more configuration than typical outpatient workflows
- –Complex integrations can demand IT resources to handle mapping and timing
- –Some workflow automation depends on how practices structure tasks and queues
- –Limited visibility into edge-case integration issues without dedicated support
Outpatient practice managers
Standardize documentation across clinicians
More consistent visit documentation
Health IT integration teams
Connect scheduling and clinical systems
Reduced manual data transfer
Show 2 more scenarios
Compliance and governance leads
Control access to patient records
Clear accountability for chart activity
Apply role-based clinical access and audit logging to support internal review and incident response.
Clinician documentation leads
Support specialty documentation standards
Fewer missing chart elements
Adapt encounter note structure to capture consistent clinical documentation for the practice’s specialty mix.
Best for: Fits when outpatient practices need configurable documentation plus HL7 v2 and FHIR integration.
OpenEMR
SMBOpenEMR is an open-source electronic medical record and practice management platform.
Configurable encounter templates that standardize documentation across providers without changing the core application.
OpenEMR is an open source EMR that focuses on practical ambulatory charting and repeatable documentation workflows. It provides encounter templates, configurable clinical modules, and longitudinal patient records with structured problem lists and medication tracking.
OpenEMR supports interoperability through standards-based exports and integrations that can connect to external lab, imaging, and exchange paths. Admin and clinicians get audit-friendly history of clinical actions alongside role-based access controls for day-to-day governance.
- +Strong ambulatory documentation with encounter templates and customizable forms
- +Longitudinal medication and problem tracking supports continuity across visits
- +Interoperability options for external clinical data flows and document exchange
- +Audit trails and role-based access controls support internal governance
- –FHIR API and SMART on FHIR support is limited versus modern EMR stacks
- –Customization can require careful configuration to keep data capture consistent
- –Workflow automation options depend heavily on local configuration choices
- –Upgrade and maintenance effort is higher for teams without Linux administration
Best for: Fits when ambulatory practices need configurable documentation and controllable local deployments.
Practice Fusion
SMBPractice Fusion provides cloud-based electronic health records for ambulatory medical practices.
Audit trail tied to clinical document edits provides traceability for chart changes across users.
Practice Fusion provides a cloud-hosted EMR workflow for ambulatory practices, centered on clinical documentation and patient charting. It includes templates for encounter notes and structured problem list and medication tracking to support day-to-day documentation and follow-up.
The system supports integrations through an API and healthcare interoperability formats used for data exchange with other applications. For governance, it offers role-based access controls and an audit trail for user activity tied to chart changes.
- +Encounter note templates reduce repeat documentation work
- +API support supports data exchange with third-party applications
- +Role-based access controls limit who can view and edit charts
- +Audit trail records user actions on clinical content
- –FHIR and HL7 mapping depth can require integration engineering
- –Advanced automation is less granular than workflow-first EMR products
- –EHR customization can rely on template changes that need governance
- –Reporting depth for complex quality measures may need external tooling
Best for: Fits when ambulatory teams need charting templates plus API-driven interoperability for outside systems.
Canvas Medical
API-firstCanvas Medical provides an API-first clinical records platform for healthcare technology teams.
Visit note and order capture are designed to stay linked during the same encounter flow.
Canvas Medical is an EMR built for ambulatory practices that need structured clinical documentation, encounter capture, and day-to-day chart workflow in one system. The product emphasizes configurable documentation templates, order entry workflows, and medication tracking so clinicians can complete notes and care actions during visits.
Integration support matters for Canvas Medical, and evaluation should focus on its interoperability formats, data exchange approach, and how appointments and clinical data move between systems. Admin review should also cover audit visibility, role-based clinical access, and governance controls that manage who can view or change patient data.
- +Configurable visit documentation templates for consistent encounter notes
- +Order entry workflows reduce handoffs between charting and ordering
- +Medication tracking supports continuity across follow-ups
- +Role-based access supports controlled clinical viewing and editing
- –Interoperability evaluation needs early testing for each integration
- –Advanced automation requires more configuration effort than basic setups
- –Complex workflows may need template tuning to avoid extra clicks
- –Data migration and cutover planning can be labor-intensive
Best for: Fits when ambulatory teams want configurable clinical documentation and tight in-visit workflows with clear access controls.
Medplum
API-firstMedplum is an open-source healthcare platform for building compliant clinical applications and medical records.
FHIR subscriptions and webhooks let external systems react to clinical changes in near real time.
Medplum pairs an ambulatory clinic EMR workflow with an API-first clinical data layer built around FHIR resources and subscriptions. It emphasizes programmable charting and automation through server-side rules, outbound webhooks, and granular access controls that govern which users can see and change specific clinical records.
Medplum also supports interoperability pathways for exchanging structured clinical data and documents that align with common healthcare formats. For teams that need custom integrations and configurable workflows, Medplum focuses more on extensibility and governance than on fixed templates.
- +FHIR-native data access with real-time subscriptions via API
- +Server-side automation rules for clinical workflows
- +Fine-grained RBAC controls tied to record-level access
- +Audit trail coverage for clinical record changes
- –More setup needed to map custom workflows to data resources
- –Advanced integrations depend on developer work for stable throughput
- –Some common admin tasks feel less wizard-driven than larger suites
- –Reporting requires careful configuration to match specific queries
Best for: Fits when ambulatory teams want an API-driven EMR with workflow automation and strong record-level governance.
MEDITECH Expanse
enterpriseMEDITECH Expanse is a hospital information system with electronic medical record capabilities.
End-to-end inpatient workflow support with CPOE tightly linked to medication and charting documentation flows.
MEDITECH Expanse is an EMR used in hospital and health system settings where MEDITECH focuses on clinical documentation, medication workflows, and order entry. The solution supports CPOE and day-to-day charting with structured clinical content and configurable forms.
Integration is built around FHIR-based interfaces for patient, clinical, and operational data exchange with external systems. Administration centers on role-based clinical access and audit logging so organizations can govern who can view or change record data.
- +Strong order entry workflows with consistent medication handling
- +FHIR-based interfaces for patient and clinical data exchange
- +Configurable clinical documentation templates for repeatable charting
- +Role-based access model with audit log coverage for record changes
- –Workflow configuration depth increases implementation governance needs
- –Limited guidance for complex ambulatory customization without additional work
- –User experience can feel slower for highly granular charting teams
- –Some integrations may require dedicated build time for edge cases
Best for: Fits when a hospital needs structured documentation plus order entry workflows and governed clinical access.
ModMed
vertical specialistModMed delivers specialty-specific electronic health records and practice management software.
ModMed’s specialty-focused documentation workflow links encounter templates to coded problem tracking for consistent clinical and billing alignment.
ModMed performs clinical documentation and scheduling for ambulatory and specialty practices that need structured visit workflows mapped to coded diagnoses and billing-ready problem tracking. The system supports order entry workflows and medication documentation so encounters can document assessments, plans, and active medications in one record context.
ModMed focuses on interoperability for exchanging clinical documents and data with external systems through established health IT standards and integration points. Admin controls cover user access boundaries, audit visibility, and operational settings that govern how staff can document, view, and update patient information.
- +Structured visit templates reduce variation across encounter notes and follow-ups
- +Order entry and medication documentation stay within the same encounter workflow
- +Integration options support external clinical data exchange and document continuity
- +Role-based clinical access helps restrict who can view or edit specific records
- –Complex specialty workflows may require configuration time before day-to-day use
- –Some interoperability scenarios depend on additional interfaces built by integrators
- –Advanced reporting requires setup to match specialty documentation patterns
- –Data migration effort can be significant when mapping existing documentation histories
Best for: Fits when specialty clinics need structured documentation workflows plus interoperable record exchange.
CharmHealth
SMBCharmHealth provides electronic health records, practice management, and patient engagement tools.
Visit documentation is organized around reusable encounter sections that speed repeat patient charting without custom development.
CharmHealth is an ambulatory-focused EMR that centers clinical documentation workflows for outpatient practices. It provides appointment-to-encounter record building, problem list maintenance, and encounter note tooling designed for day-to-day charting.
Practice teams can coordinate common documentation needs through structured sections and reusable visit elements. Administrative handling of patient identity, chart access, and data export supports ongoing operations beyond note entry.
- +Outpatient charting workflows map to visit documentation steps
- +Reusable documentation elements reduce repetitive typing across visits
- +Clinical record navigation supports quick review during encounters
- +Exportable record content supports downstream data handling needs
- –Automation depth for population workflows appears limited versus larger suites
- –Integration surface details for FHIR and HL7-based exchange are unclear
- –Admin governance features are harder to validate without direct documentation
Best for: Fits when outpatient teams need structured encounter documentation with straightforward chart navigation and export.
Conclusion
After evaluating 10 healthcare medicine, Epic 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 emr medical records software
An EMR medical records system is where outpatient or inpatient teams capture encounter notes, manage longitudinal medication and problem tracking, and produce audit trails that document who viewed or changed chart data. This buyer's guide covers Epic, athenaOne, Tebra, OpenEMR, Practice Fusion, Canvas Medical, Medplum, MEDITECH Expanse, ModMed, and CharmHealth based on documented workflow depth, integration surface, and governance controls.
The reviews that follow compare how each product handles encounter documentation throughput, workflow automation via triggers or rules, and interoperability through FHIR or other interface support. The strongest differences show up in how closely order entry and documentation stay linked and how much configuration is required to keep templates, workflows, and integrations aligned.
EMR medical records software for governed clinical documentation, order workflows, and interoperable chart access
EMR medical records software centralizes clinical documentation and chart workflows so care teams can document visits, manage clinical histories, and connect orders to the same encounter context. Epic and MEDITECH Expanse pair governed access with deep workflow tooling that supports both ambulatory documentation and inpatient processes like tightly linked CPOE and medication handling.
Implementation outcomes often depend on the integration and automation surface exposed by each EMR. Medplum emphasizes FHIR-native data access with near real-time automation using FHIR subscriptions and webhooks, while athenaOne uses rules-based charting actions that apply automatically during encounter documentation based on configurable triggers.
Core evaluation points for EMR medical records software workflows, API, and governance
EMR medical records software succeeds when encounter documentation flows connect tightly to the rest of the chart, including orders and downstream billing tasks. The strongest differentiators show up in how automation triggers operate during documentation and how reliably the system exposes data to outside services through an API.
Governed clinical access also determines whether audit logs remain trustworthy during day-to-day charting. The evaluation points below compare Epic, athenaOne, Tebra, OpenEMR, Practice Fusion, Canvas Medical, Medplum, MEDITECH Expanse, ModMed, and CharmHealth on workflow depth, integration surface, and change traceability.
Governed workflow execution with audit log trails
Epic combines role-based clinical access with comprehensive audit log trails across configured workflows. Tebra focuses on audit logging tied to role-based clinical access during outpatient encounters so chart edits remain traceable.
Documentation-time automation via encounter triggers and rules
athenaOne applies rules-based charting and workflow actions during encounter documentation based on configurable triggers. Medplum uses server-side automation rules that run alongside API access to support workflow reactions to clinical changes.
API and integration surface for clinical and administrative systems
Epic provides FHIR API and document exchange support for multi-vendor interoperability across departments. OpenEMR limits FHIR API and SMART on FHIR support versus modern EMR stacks, which can reduce integration options for advanced API consumers.
Encounter template standardization without heavy app customization
OpenEMR uses configurable encounter templates to standardize documentation across providers without changing the core application. CharmHealth organizes visit documentation around reusable encounter sections to speed repeat charting without custom development.
Linkage between visit documentation and order entry
Canvas Medical keeps visit note and order capture linked during the same encounter flow to reduce handoffs between charting and ordering. MEDITECH Expanse links CPOE to inpatient documentation flows so medication handling stays consistent through structured order workflows.
FHIR-native eventing and record-level reactivity
Medplum offers FHIR subscriptions and webhooks so external systems can react to clinical changes in near real time. Practice Fusion pairs API-driven interoperability for outside systems with audit trail traceability for clinical document edits.
How to choose EMR medical records software for workflow fit and integration control
Shortlisting should start with where the workflow must be strict and where it must be flexible. The documentation engine matters most when order entry must remain linked to the same encounter context and when automation must run during documentation rather than after the visit.
Integration and governance should be evaluated as active capabilities, not as checkboxes. Tools with explicit API and automation surfaces reduce mapping delays and help keep audit log trails aligned with real user actions across charting steps.
Map automation requirements to documentation-time trigger behavior
If visit documentation must automatically execute next steps during the encounter, athenaOne applies rules-based charting actions driven by configurable triggers. If external systems must react immediately to clinical changes, Medplum uses FHIR subscriptions and webhooks to push updates.
Check whether orders stay connected to the same encounter workflow
Canvas Medical ties visit note capture to order entry so clinicians do not switch context between documenting and ordering. For inpatient settings with structured medication pathways, MEDITECH Expanse links CPOE tightly to medication and charting documentation flows.
Validate governance depth across user roles and configured workflows
For enterprise governance that spans many departments, Epic combines role-based clinical access with comprehensive audit log trails across configured workflows. For outpatient governance where tracking chart reads and changes is the priority, Tebra pairs role-based clinical access with audit logging during outpatient encounters.
Plan for template standardization versus specialty workflow mapping
If the practice needs consistent documentation across providers through templates, OpenEMR uses configurable encounter templates and customizable forms. If specialty clinics need coded problem tracking linked to encounter templates, ModMed focuses specialty documentation workflows that align clinical and billing follow-ups.
Stress-test interoperability with the integrations that must carry real clinical context
If multi-vendor interoperability requires document exchange and a broad FHIR exposure, Epic is designed for that depth with FHIR API and document exchange support. If the plan relies on simpler exchange and repeat typing reduction, CharmHealth emphasizes reusable encounter sections and clearer chart navigation rather than deep integration surface detail.
Quantify integration workload from mapping complexity and throughput needs
If integrations must support near real-time behavior, Medplum requires mapping custom workflows to data resources and can involve developer work to sustain stable throughput. If integrations depend on outside systems consuming structured clinical documents, Practice Fusion requires integration engineering for deeper FHIR and HL7 mapping depth.
Who needs EMR medical records software with workflow automation and governed charting
Different clinics need different combinations of charting control, automation timing, and interoperability. The tools below separate by where encounter documentation must connect to orders, how audit trails must behave, and how much integration engineering is tolerable.
The audience segments also reflect how much configuration discipline teams must accept when templates and workflows must reflect local practice patterns while remaining audit-ready.
Large health systems standardizing inpatient and ambulatory workflows
Epic fits environments that need governed workflows across multiple departments and rely on comprehensive audit log trails with role-based clinical access.
Multi-clinic practices that want documentation-time automation tied to visit workflows
athenaOne matches practices that need rules-based charting and workflow actions that execute automatically during encounter documentation using configurable triggers.
Outpatient practices that require audit logging for chart reads and changes
Tebra targets outpatient teams that want audit logging with role-based clinical access to track who viewed or changed chart data during encounters.
Ambulatory teams that need tightly linked documentation and order capture
Canvas Medical is designed for visit note and order capture staying linked during the same encounter flow to reduce handoffs.
Specialty clinics aligning structured documentation to coded tracking
ModMed supports specialty documentation workflows that link encounter templates to coded problem tracking for consistent clinical and billing alignment.
Common pitfalls when implementing EMR medical records software workflows and integrations
Many implementation failures come from selecting an EMR based on charting features while underestimating configuration and integration complexity. The mismatch shows up when templates do not map cleanly to specialty documentation or when automation rules require ongoing tuning.
Governance also breaks down when teams assume audit trails will match real workflow actions without aligning configured steps to user roles and documentation edits.
Treating automation triggers as a one-time setup instead of an operating model
athenaOne requires ongoing configuration discipline for advanced automation so rules remain aligned with visit documentation behavior. Medplum also depends on developer and mapping work to translate custom workflows into data resources that sustain stable throughput.
Assuming all EMRs offer modern FHIR integration depth for advanced interoperability
OpenEMR limits FHIR API and SMART on FHIR support versus modern EMR stacks, which can constrain API consumers and integration paths. CharmHealth lists FHIR and HL7 exchange surface details as unclear, so integration planning needs early validation.
Choosing a template approach without validating how consistently data capture stays aligned
OpenEMR customization can require careful configuration to keep data capture consistent across providers and forms. Canvas Medical also needs early integration testing for each integration so document and order workflows remain reliable in real use.
Overlooking the impact of workflow linkage between charting and orders
If order entry must remain tightly tied to encounter context, Canvas Medical provides linked visit note and order capture by design. If the environment is inpatient and requires CPOE tied to medication handling, MEDITECH Expanse supports end-to-end inpatient workflow support rather than just ambulatory charting.
Underestimating specialty workflow configuration time before daily operations
ModMed can require configuration time to make complex specialty workflows usable for day-to-day charting. Epic and MEDITECH Expanse also increase governance workload when tailoring workflows, which can slow go-live if change management is not planned.
How We Selected and Ranked These Tools
We evaluated Epic, athenaOne, Tebra, OpenEMR, Practice Fusion, Canvas Medical, Medplum, MEDITECH Expanse, ModMed, and CharmHealth using feature depth for encounter documentation throughput, workflow automation behavior, and integration surface. Feature coverage counted 40% while ease of implementation and ongoing workflow usability each counted 30% with an emphasis on how many configuration passes are required for templates and automations.
Governance controls and audit log behavior were scored by how consistently role-based clinical access is applied to configured workflow actions. Epic set the benchmark with enterprise workflow governance depth that combines role-based clinical access with comprehensive audit log trails across configured workflows, plus FHIR API and document exchange support for multi-vendor interoperability.
Frequently Asked Questions About emr medical records software
How do EMR integrations differ between FHIR-first platforms and API-based systems?
Which platforms provide near real-time eventing for clinical changes?
When teams need in-visit workflow automation, what differs in athenaOne vs Canvas Medical?
Which EMR supports enterprise-style governed access with audit log trails across configured workflows?
What breaks if the data migration path cannot map local templates to the EMR data model?
How do admin controls and RBAC coverage differ in outpatient EMRs?
Where does interoperability fall short in practice when standards coverage is uneven?
Which systems are built around inpatient order entry workflows rather than ambulatory encounters?
How should teams evaluate extensibility when a practice needs custom workflows beyond templates?
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→