GITNUXSOFTWARE ADVICE
Healthcare MedicineTop 10 Best Release Of Information Services of 2026
Top 10 Release Of Information Services providers ranked by workflow, security, and speed, with notes for hospitals and medical records teams.
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
Editor’s top 3 picks
Three quick recommendations before you dive into the full comparison below — each one leads on a different dimension.
ReleasePoint
Audit log tied to authorization and release actions across the full request lifecycle.
Built for fits when release operations need governed automation across multiple source systems..
Summit Medical Records
Editor pickAudit log per request record that captures staff actions and authorization handling.
Built for fits when health systems need controlled ROI automation and audit-ready governance..
ChartSpan
Editor pickWorkflow automation that ties request state transitions to auditable delivery events.
Built for fits when regulated records teams need governed automation and integration across RoI systems..
Related reading
Comparison Table
This comparison table contrasts Release Of Information Services providers across integration depth, including supported API and data schema alignment. It also maps automation and provisioning options, plus admin and governance controls such as RBAC and audit log coverage to show where configuration effort and throughput constraints appear.
ReleasePoint
specialistMedical records release of information services that manage ROI requests and fulfillment workflows for healthcare organizations.
Audit log tied to authorization and release actions across the full request lifecycle.
ReleasePoint supports release intake and request status lifecycle management that can be tied to external systems through API integrations. The data model centers on authorization artifacts, release actions, document inventory, and status fields that enable schema-aligned provisioning and consistent state transitions. Automation can be applied at workflow points like receipt validation, routing decisions, and fulfillment handoffs to reduce manual touchpoints. Governance controls include RBAC and audit log retention features that support internal oversight and traceability.
A tradeoff appears in how heavily the workflow configuration and schema mapping depend on upfront setup of authorization rules and destination behaviors. Teams with highly custom release logic often need stronger engineering involvement to keep integration and automation rules consistent across endpoints. ReleasePoint fits best when operational throughput and auditability matter, such as when clinical operations coordinate daily requests across multiple business units and systems.
- +Workflow lifecycle tracking from intake to fulfillment with auditable state changes
- +API surface supports automation and system-to-system provisioning
- +RBAC and audit log enable governed release operations across teams
- +Configuration supports rule-based routing and exception handling
- –Schema mapping and workflow rule setup require upfront integration effort
- –Highly bespoke release policies may need engineering work to stay consistent
Health information management teams
Automate authorization validation and routing
Faster release processing
Integration engineers
Provision requests via API
Lower manual reconciliation
Show 2 more scenarios
Compliance and privacy teams
Audit release decisions end to end
Stronger traceability
Audit log visibility ties actions to authorization inputs and release outcomes.
Operations managers
Control throughput with automation
More predictable throughput
Automated routing and fulfillment reduce bottlenecks during peak intake.
Best for: Fits when release operations need governed automation across multiple source systems.
More related reading
Summit Medical Records
specialistMedical records retrieval and ROI processing firm that fulfills request workloads using documented handling and release procedures.
Audit log per request record that captures staff actions and authorization handling.
Summit Medical Records fits organizations that need tighter control over request intake, validation, authorization capture, and fulfillment. The service emphasizes an explicit data model for patient identifiers, request metadata, consent artifacts, and delivery records, which supports deterministic automation. Integration depth matters for environments that already have EHR, health information exchange, or case-management systems, because the automation surface targets state changes and document events. Governance is built around RBAC-style permissions and audit log coverage that ties actions back to specific request records and staff roles.
A tradeoff appears when internal systems require custom schema extensions beyond the provider’s established mapping, because extensibility often depends on change configuration cycles and integration scoping. Summit Medical Records performs best when request throughput and exception handling need consistent rules for authorization, redaction, and delivery logging. One strong usage situation is a multi-site health system coordinating ROI across clinics while keeping a single audit trail per request.
- +Request lifecycle automation tied to status and document events
- +Clear data model for identifiers, authorizations, and delivery logs
- +RBAC-style governance with auditable staff actions
- +Integration mapping targets deterministic schema alignment
- –Custom schema extensions require formal integration scoping
- –Complex exception workflows may need configuration time
Health information management teams
Audit-ready ROI fulfillment with staff traceability
Fewer audit gaps
EHR integration engineers
Automate intake and release status updates
Lower manual rework
Show 2 more scenarios
Compliance and privacy operations
RBAC governance for ROI authorization
Stronger access control
Restricts access by role and records who performed authorization and release steps per request.
Multi-site operations teams
Consistent ROI rules across locations
More consistent processing
Applies standardized request lifecycle and delivery logging across sites for higher throughput handling.
Best for: Fits when health systems need controlled ROI automation and audit-ready governance.
ChartSpan
enterprise_vendorMedical records fulfillment and release of information services that process ROI requests through structured intake, tracking, and delivery operations.
Workflow automation that ties request state transitions to auditable delivery events.
ChartSpan fits teams that need integration depth across intake sources and downstream fulfillment targets for ROI requests. The data model centers on consistent entities for request, identity, authorization, documents, and delivery events, which reduces schema drift during provisioning. The automation and API surface enables configuration of intake fields, workflow routing rules, and status transitions to match internal governance.
One tradeoff is that deeper customization requires agreeing on a stable request schema and workflow mapping before high-throughput automation runs. ChartSpan works well when throughput spikes during audit windows or legal holds because automation can keep request state transitions and audit logging aligned to policy. Integration and governance controls reduce admin load by constraining access and recording operational events during each release step.
- +API-driven provisioning for request and document entities
- +Automation supports intake to fulfillment status transitions
- +RBAC-style governance and audit log alignment for releases
- +Configuration reduces manual handling during throughput spikes
- –Schema mapping work increases upfront integration effort
- –Workflow customization depends on stable policy definitions
- –Advanced routing changes require coordinated admin configuration
Health system compliance teams
Release requests synchronized to EHR records
Fewer delays, consistent audits
Legal operations teams
Holds-aware authorization checks
Controlled releases during holds
Show 2 more scenarios
Records management administrators
RBAC access for request workflows
Tighter access control
Admin controls limit who can provision, approve, and export release artifacts.
IT integration teams
API integration with fulfillment systems
Higher integration throughput
Extensibility via automation and API supports schema-aligned mapping into downstream delivery targets.
Best for: Fits when regulated records teams need governed automation and integration across RoI systems.
Crestline Services
agencyRelease of information services provider that performs medical record retrieval and ROI fulfillment with operational governance controls.
RBAC-governed workflow automation with audit log traceability across request intake and release fulfillment.
Release of Information services from Crestline Services center on integration and governed workflows for privacy-bound data exchange. Crestline Services supports configuration of request intake, status tracking, and records preparation aligned to a defined data model for releases.
Automation and API surface support provisioning, consistent data mapping, and higher-throughput handoffs across systems. Admin and governance controls focus on RBAC, audit logging, and controlled access to ensure traceability from request to disclosure.
- +Defined data model for ROI records reduces mapping drift across sources
- +Automation around intake, status, and fulfillment supports higher request throughput
- +API and extensibility support controlled integrations into existing systems
- +RBAC plus audit log coverage improves traceability for each release action
- –Integration work can require detailed schema alignment across parties
- –Automation configuration depth may slow initial rollout for small teams
- –Complex governance requirements can add admin overhead for every workflow variant
Best for: Fits when HIPAA-bound ROI workflows need API-driven integration, RBAC, and audit log governance.
Medsouth
specialistMedical records retrieval and ROI fulfillment services for healthcare organizations that coordinate authorization intake and document release operations.
Audit-ready disclosure documentation tied to request lifecycle status and staff actions.
Medsouth delivers release of information workflows that manage request intake, identity matching, and outbound fulfillment across covered entities. Core capabilities focus on configurable data handling steps, staff-facing tracking, and audit-ready documentation for disclosures.
Integration depth centers on connecting Medsouth workflows to healthcare data sources using defined interfaces and operational schemas. Automation and API surface are the key differentiators for teams that need consistent throughput, change-managed provisioning, and governance controls.
- +Configurable release workflows reduce manual variance across request types.
- +Audit-ready request tracking supports defensible disclosure documentation.
- +Admin controls support RBAC-style access separation for request handling.
- +Integration-oriented approach supports automated intake to fulfillment routing.
- –API automation coverage needs mapping per client workflow and schema.
- –Data model alignment can be nontrivial for custom request attributes.
- –Governance controls require up-front configuration of roles and permissions.
- –Throughput depends on queue design and operational handoff rules.
Best for: Fits when health systems need controlled, audited ROI processing with integration and automation.
CureMD Health Systems
enterprise_vendorProvides healthcare release of information workflows, chart retrieval coordination, and HIPAA-compliant authorization handling for provider organizations through staffed records and compliance operations.
Configurable RBAC with audit log tied to release request status changes and processing actions.
CureMD Health Systems fits organizations needing release of information workflows tied to EHR-grade identity, record retrieval, and structured case handling. The service supports integration paths that translate authorization metadata into a release workflow, with emphasis on audit trail and staff-controlled processing.
Admin governance typically centers on role-based permissions, case ownership rules, and configurable retention behavior across requests. CureMD Health Systems also supports automation and extensibility for throughput-sensitive teams that need consistent handling of documents and status events.
- +Release-of-information workflow modeled around authorization, case status, and document handling
- +RBAC-aligned access patterns for request processing and staff role separation
- +Audit log coverage supports traceability for request lifecycle changes
- +Integration surface supports API-driven data mapping for authorization to release processing
- –Complex data model mapping can require schema work for existing doc repositories
- –Automation coverage depends on event granularity for status updates
- –Governance configuration can be time-consuming for multi-department teams
Best for: Fits when teams need controlled, auditable ROI case workflows integrated into existing EHR and document systems.
Health Information Management Services Group
agencyOffers healthcare HIM outsourcing that includes release of information request processing, document preparation, and controlled disclosure operations.
Audit-focused release workflow that tracks identity, request metadata, and fulfillment actions.
Health Information Management Services Group pairs release of information operations with integration-first workflows for providers and health systems. The service emphasizes controlled data handling through governed request intake, identity checks, and repeatable fulfillment steps tied to a defined data model.
Integration depth is supported through handoff patterns that map request metadata to downstream release tasks. Automation and operational controls focus on audit-ready processing, RBAC-aligned access patterns for internal users, and configuration-driven governance of release rules.
- +Integration-first request routing with consistent metadata-to-task mapping
- +Governed handling steps for identity verification and release compliance
- +Audit-ready processing workflow designed for traceable outcomes
- +Configuration-driven release rules reduce manual exception handling
- –API surface details are not clearly documented for deep automation scenarios
- –Extensibility relies on operational workflow changes more than schema-level customization
- –Throughput gains depend on request complexity and staffing coverage
Best for: Fits when health organizations need managed release workflows with strong governance and traceability.
Axia Health
enterprise_vendorRuns outsourced healthcare documentation and HIM operations that support release of information workflows with standardized intake and release governance.
Audit-log coverage for release actions tied to role-based access controls.
Release of Information services from Axia Health fit organizations that need controlled workflow for record access requests. Delivery focuses on intake-to-response processing with documented operational handoffs, which reduces variation across request types.
Integration depth matters most for teams that must align Axia’s data model and request routing with existing systems of record. Automation capability is evaluated through the available API surface and provisioning patterns that support RBAC, audit log retention, and throughput during request spikes.
- +Request workflow management with consistent intake, routing, and response handling.
- +Documented data handling steps that support reproducible outcomes.
- +Integration support centered on request records and consistent identifiers.
- +Governance controls include access controls and traceable activity records.
- –API automation scope may lag teams needing custom schemas for every record type.
- –Provisioning and schema changes can require service-side coordination.
- –Limited visibility into processing throughput metrics for each request stage.
Best for: Fits when teams need managed ROI workflows with governance and audit traceability requirements.
Records Management Services, Inc.
specialistDelivers healthcare records management and release of information services with controlled intake, tracking, and authorized disclosure operations.
Audit-oriented release workflow that preserves request and disclosure traceability through structured handling steps.
Records Management Services, Inc. delivers Release Of Information Services built around jurisdiction-ready request intake, identity verification, and document disclosure workflows. The delivery model emphasizes controlled release execution with staff oversight, structured status updates, and auditable handling of request artifacts.
Integration depth is typically centered on case and records systems through configuration and operational handoffs rather than a public data model designed for broad API automation. Admin governance relies on role separation, documented procedures, and traceability via audit-style records for request and disclosure events.
- +Staff-supervised ROI workflow with consistent request-to-disclosure execution
- +Document handling focused on auditability across intake, review, and release steps
- +Operational reporting covers request status and disclosure outcomes
- +Governance through RBAC-style role separation and procedural controls
- –API automation surface is limited compared with fully programmable ROI vendors
- –Data model extensibility is constrained without published schema contracts
- –Integration throughput depends on manual or semi-automated handoffs
- –Sandbox-style configuration testing and API governance tooling are not clearly documented
Best for: Fits when governed ROI delivery and audit traceability matter more than API-first automation.
How to Choose the Right Release Of Information Services
This buyer’s guide covers how to evaluate Release Of Information Services providers that run intake, authorization handling, tracking, and disclosure fulfillment for regulated medical records exchange. It references ReleasePoint, Summit Medical Records, ChartSpan, Crestline Services, Medsouth, CureMD Health Systems, Health Information Management Services Group, Axia Health, and Records Management Services, Inc.
The guide focuses on integration depth, data model fit, automation and API surface, and admin and governance controls that directly affect auditability, throughput, and change management.
Release Of Information workflow outsourcing for governed record exchange
Release Of Information Services providers coordinate request intake, identity and authorization handling, request tracking, document preparation, and authorized disclosure delivery with auditable workflow state transitions. These services reduce manual handling variance by running configurable steps that map request metadata to records and disclosure outputs.
Organizations use these workflows to satisfy HIPAA-bound disclosure obligations with traceability from authorization events through fulfillment actions. Providers such as ReleasePoint and ChartSpan show what API-driven provisioning and workflow automation can look like when request entities and delivery events are treated as a governed data model.
Evaluation criteria that map to auditability and automation control
Release Of Information Services creates risk when request metadata, authorization actions, and disclosure outputs do not follow a consistent schema and governance model. The evaluation criteria below tie directly to operational control depth and the integration work required to keep state changes auditable.
The strongest providers expose automation and API surfaces for provisioning request and document entities while keeping RBAC access rules and audit logs aligned to release actions across the lifecycle.
Integration depth across intake, authorization, tracking, and fulfillment
Integration depth determines how reliably the provider connects request intake events to authorization checks, workflow tracking, and disclosure fulfillment across existing systems. ReleasePoint and ChartSpan emphasize lifecycle coverage with API-driven provisioning for request and document entities, while Crestline Services pairs intake, status, and fulfillment automation with controlled data mapping.
Governed data model for request and disclosure entities
A stable data model reduces mapping drift when multiple sources feed ROI requests and when downstream systems consume disclosure outputs. ReleasePoint highlights a governed data model that maps authorization, tracking, and fulfillment rules, and Crestline Services cites a defined data model for ROI records that reduces mapping drift across sources.
Automation coverage tied to workflow state transitions
Automation that binds state changes to auditable delivery events reduces manual variance during spikes. ChartSpan ties request state transitions to auditable delivery events, and Summit Medical Records ties request lifecycle automation to status and document events.
API-driven provisioning and a documented automation surface
An automation and API surface enables system-to-system provisioning of request and document entities and supports operational throughput for high-volume workflows. ReleasePoint supports API-driven provisioning and system-to-system automation, while ChartSpan also emphasizes API-driven provisioning for request and document entities.
RBAC and audit log traceability across the full lifecycle
Role-based access control and audit logs must cover authorization handling and release actions so internal teams can demonstrate traceability. ReleasePoint provides an audit log tied to authorization and release actions across the full request lifecycle, and CureMD Health Systems ties configurable RBAC to audit log coverage across request status changes and processing actions.
Rule-based configuration for routing and exceptions
Configurable routing rules and exception handling reduce manual handling for atypical request types. ReleasePoint supports configuration of rules that govern releases and exceptions, and Summit Medical Records uses documented integration pathways for provisioning, data mapping, and automation triggers tied to request status changes.
Pick a Release Of Information provider by mapping workflow states to schema, controls, and APIs
A provider choice should start with how request and authorization events become governed workflow state transitions in the provider’s system. The best fit is the provider whose integration path and data model minimize schema remapping while keeping audit logs and RBAC tied to release actions.
The steps below focus on integration depth, data model contracts, automation and API surface, and admin and governance controls so operational teams can maintain throughput and defensible traceability.
Verify lifecycle coverage from authorization to fulfillment
Ask how request intake events trigger authorization handling, then how authorization outcomes map into tracking states and disclosure fulfillment. ReleasePoint ties audit logging to authorization and release actions across the full request lifecycle, and ChartSpan ties workflow automation to auditable delivery state transitions.
Confirm the data model fit for identifiers, authorizations, and delivery logs
Require a concrete explanation of how identifiers, authorization attributes, request status, and delivery documentation are represented as fields or entities. Summit Medical Records highlights a clear data model for identifiers, authorizations, and delivery logs, and Crestline Services emphasizes a defined data model that reduces mapping drift across sources.
Evaluate the automation surface and API-driven provisioning depth
Check whether the provider can provision request and document entities through API-driven workflows instead of relying on manual handoffs. ReleasePoint and ChartSpan both emphasize API-driven provisioning for request and document entities, while Records Management Services, Inc. centers integration on case and records systems through configuration and operational handoffs rather than broad API-first automation.
Test governance controls for RBAC and auditable actions
Confirm that RBAC governs who can perform request handling actions and that audit logs capture staff actions tied to authorization and release actions. CureMD Health Systems configures RBAC and ties audit log coverage to release request status changes and processing actions, while Axia Health provides audit-log coverage for release actions tied to role-based access controls.
Assess rule configuration for routing and exceptions without breaking schema consistency
Identify how routing rules and exception handling are configured and how that configuration stays consistent with schema mappings. ReleasePoint supports rule-based routing and exception handling, and Medsouth positions configurable release workflows that reduce manual variance across request types while requiring mapping per client workflow.
Which teams benefit from specific ROI automation and governance profiles
Different organizations need different tradeoffs between API-driven automation, schema governance, and staff-supervised handling. The best fit depends on whether request volume requires throughput automation or whether auditability is the primary driver.
The segments below map to the providers that best match those operational constraints.
Health systems coordinating RoI across multiple source systems
Teams that must govern releases across intake, authorization, tracking, and fulfillment benefit from ReleasePoint because it emphasizes integration depth across the full workflow lifecycle with API surface automation. ChartSpan is also a strong fit when regulated records teams need governed automation integrated across RoI systems.
Organizations that require audit-ready governance tied to authorization and staff actions
Providers with audit log traceability bound to authorization handling reduce defensibility risk during requests and disclosures. ReleasePoint delivers an audit log tied to authorization and release actions across the full lifecycle, and Summit Medical Records captures staff actions and authorization handling in an audit log per request record.
Teams pushing throughput with workflow automation tied to state transitions
When request status changes must trigger automated steps while maintaining auditable delivery events, ChartSpan fits because workflow automation ties request state transitions to auditable delivery events. Summit Medical Records supports request lifecycle automation tied to status and document events, which supports higher-volume operations.
Organizations integrating HIPAA-bound workflows with strict RBAC and traceability
HIPAA-bound operations that need controlled access and audit log coverage match Crestline Services because it pairs RBAC with audit log traceability across request intake and release fulfillment. CureMD Health Systems also fits teams that want configurable RBAC tied to audit log coverage for release request status changes and processing actions.
Organizations prioritizing governed, staff-supervised ROI execution over API-first automation
When operational handoffs and structured staff handling are the priority, Records Management Services, Inc. is a fit because its delivery model emphasizes staff oversight with traceability through structured handling steps. Medsouth also fits when configurable release workflows and audit-ready disclosure documentation matter more than broad API automation for custom schema-heavy request attributes.
Where ROI programs fail when controls, schema, and automation are not aligned
Release Of Information projects commonly fail when governance controls and workflow state transitions do not map cleanly to a stable data model. Manual handoffs increase variability when the provider’s automation surface is not deep enough for throughput targets.
The pitfalls below reflect the recurring integration and governance constraints described across the reviewed providers.
Choosing a provider with insufficient API-driven provisioning for the target throughput
Providers like Records Management Services, Inc. emphasize configuration and operational handoffs over a broad programmable ROI API surface, which can limit automation for high-volume integration scenarios. ReleasePoint and ChartSpan explicitly support API-driven provisioning for request and document entities to support higher-throughput workflows.
Treating schema mapping as a one-time exercise instead of ongoing governance work
Several providers note upfront schema mapping effort, and CureMD Health Systems and ChartSpan both describe schema work needed for existing repositories and workflow customization. ReleasePoint, Crestline Services, and Summit Medical Records reduce mapping drift by emphasizing governed data models for request and disclosure records.
Assuming audit logs will cover release actions without RBAC alignment
Auditability breaks when role permissions do not tie to staff actions captured in audit logs across authorization and fulfillment steps. ReleasePoint ties audit logs to authorization and release actions across the lifecycle, and Axia Health ties audit-log coverage to role-based access controls.
Underestimating configuration time for exception routing and governance variants
Workflow variants increase admin overhead when governance configuration and routing rules require careful setup. ReleasePoint supports configuration of release and exception rules, while Crestline Services notes that complex governance requirements can add admin overhead for every workflow variant.
Expecting highly bespoke policies to work without engineering alignment to workflow rules
Highly bespoke release policies can require engineering work to stay consistent, which is a constraint highlighted for ReleasePoint when policy complexity increases. ChartSpan and Summit Medical Records also tie workflow customization to stable policy definitions and status-to-document triggers.
How We Selected and Ranked These Providers
We evaluated ReleasePoint, Summit Medical Records, ChartSpan, Crestline Services, Medsouth, CureMD Health Systems, Health Information Management Services Group, Axia Health, and Records Management Services, Inc. On capabilities, ease of use, and value using the capability coverage and operational governance descriptions provided for each provider. Each overall rating is a weighted average where capabilities carries the most weight at 40% while ease of use and value each account for 30%. This editorial scoring reflects criteria-based comparisons grounded in automation depth, integration pathways, and governance controls rather than hands-on lab testing.
ReleasePoint set the top of the list because it combines an audit log tied to authorization and release actions across the full request lifecycle with an API surface designed for automation and system-to-system provisioning, which directly raised both the capabilities score and the operational control score.
Frequently Asked Questions About Release Of Information Services
Which Release Of Information services provide the strongest API-driven provisioning for governed workflows?
How do different providers implement RBAC and audit log coverage for disclosure actions?
What onboarding steps are typical when an organization must align intake schemas and request routing to existing systems?
Which provider best supports identity matching and authorization metadata translation into a release workflow?
How do providers handle data model governance for regulated record exchange and exception scenarios?
What are the most common failure points in Release Of Information workflows, and how do providers mitigate them?
Which providers are better aligned to clinician-facing document handling and request lifecycle tracking?
Which providers support extensibility for throughput-sensitive teams that need configurable automation steps?
How do delivery models differ across providers when the organization needs staff oversight versus API-first automation?
Conclusion
After evaluating 9 healthcare medicine, ReleasePoint 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.
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→FOR SOFTWARE VENDORS
Not on this list? Let’s fix that.
Our best-of pages are how many teams discover and compare tools in this space. If you think your product belongs in this lineup, we’d like to hear from you—we’ll walk you through fit and what an editorial entry looks like.
Apply for a ListingWHAT THIS INCLUDES
Where buyers compare
Readers come to these pages to shortlist software—your product shows up in that moment, not in a random sidebar.
Editorial write-up
We describe your product in our own words and check the facts before anything goes live.
On-page brand presence
You appear in the roundup the same way as other tools we cover: name, positioning, and a clear next step for readers who want to learn more.
Kept up to date
We refresh lists on a regular rhythm so the category page stays useful as products and pricing change.