Home / Companies / Memgraph / Blog / July 2026

July 2026 Summaries

5 posts from Memgraph

Filter
Month: Year:
Post Summaries Back to Blog
The Previsant Insights platform leverages Memgraph to address the complexity of payment integrity by transforming unstructured payment rules into structured, queryable data for explainable claims review. Through the ingestion and extraction of source documents, the platform identifies rule entities and their relationships, which are then stored in Memgraph, allowing analysts to query and apply rule knowledge to claims with supporting evidence. The system incorporates various querying modes, including RAG, graph, and hybrid, to address different aspects of the workflow, and emphasizes the importance of a well-defined graph model for effective rule application. Human oversight remains crucial in the rule management process to ensure accuracy and relevance, preventing errors that could lead to incorrect claims denial. This methodology, demonstrated in a Medicare Supplement payment scenario, is applicable beyond healthcare, proving beneficial in any domain where decisions are contingent on complex rule sets embedded in documents.
Jul 30, 2026 1,706 words in the original blog post.
Fraud operations are hampered by the fragmented data context, which leads to inefficiencies and delays in detecting risky patterns, contributing significantly to global financial losses, as evidenced by the $485.6 billion lost to fraud scams in 2023. Despite having vast data resources, fraud teams struggle because critical contextual information is dispersed across various disconnected systems, requiring analysts to manually piece together necessary insights. The challenge lies not in the volume of data but in the lack of integration and the ability to identify connections and relationships across data points, which are crucial for understanding the full scope of potential fraud. Traditional systems are ill-equipped for network analysis, which is essential for identifying complex fraud patterns that emerge through interconnected entities. Leveraging graph technology can enhance fraud detection by enabling relationship-driven data retrieval, allowing analysts to query the network of relationships and identify multi-hop fraud risks more efficiently. This approach shifts the focus from isolated events to connected behaviors, making it easier to detect and investigate fraud, thereby empowering analysts with the necessary context for informed decision-making.
Jul 29, 2026 1,498 words in the original blog post.
In the field of drug discovery, researchers face significant challenges due to the fragmented nature of available data across genomic, proteomic, clinical, and literature sources, resulting in scientists spending 30% to 40% of their time searching for data. This fragmentation hampers the ability to quickly connect relevant information across different domains, thereby slowing down the hypothesis evaluation and refinement process. The problem is not simply one of data scale but rather the lack of a cohesive knowledge layer that can integrate and connect disparate data sources into a coherent whole. A knowledge graph can address this by enabling multi-step retrieval across entities and evidence, allowing researchers to trace findings, compare evidence from multiple sources, and ask complex scientific questions without manually piecing together the context. This approach helps overcome the retrieval bottleneck, enabling faster hypothesis generation, more accurate reasoning, and potentially quicker identification of promising therapeutic directions. The use of knowledge graphs not only streamlines the retrieval process but also supports more connected scientific workflows, crucial for advancing research in pharma and biotech sectors.
Jul 28, 2026 1,268 words in the original blog post.
In a detailed comparison of graph traversal performance between PostgreSQL 19 and Memgraph, the focus is on evaluating the effectiveness of SQL/PGQ support in PostgreSQL for exact hop reachability queries. PostgreSQL 19 introduces SQL/PGQ, allowing property graph queries over relational tables, which is valuable for teams already using Postgres to explore connected data. However, as traversal depth increases, PostgreSQL's performance diminishes, with significant slowdowns evident at four to five hops, where Memgraph, a native graph database built around the property graph model, demonstrates superior efficiency. Memgraph's architecture, which treats nodes and relationships as core data models, enables it to maintain low latency even in deep traversals, making it more suitable for applications that rely heavily on graph-based operations. The benchmark, utilizing the Pokec dataset, highlights the strengths and limitations of each database, suggesting that while PostgreSQL 19's graph query capabilities are beneficial for shallow queries within existing relational data, Memgraph is more advantageous for workloads requiring extensive graph traversal.
Jul 08, 2026 1,242 words in the original blog post.
Memgraph 3.11 enhances multi-tenancy for cross-database graph workloads by simplifying the management and operation of graph data across multiple databases. This release introduces a cross_database module that facilitates querying across databases without external stitching, reducing the complexity of cross-boundary workflows and enabling seamless data migration and environment comparison. To address the need for temporary data views, Memgraph 3.11 offers virtual graph views through derive(), allowing users to explore graph structures without creating permanent data storage. Additionally, the update improves visibility and security in multi-tenant systems with per-database labels for monitoring tools like Prometheus and Grafana, enhanced query logging, and intra-cluster TLS for secure communication. These features collectively make it easier to manage, monitor, and secure multi-tenant graph workloads, providing teams with practical tools to handle the increasing complexity of connected graph data systems while maintaining necessary data isolation and control.
Jul 01, 2026 711 words in the original blog post.