rss.livelink.threads-in-node

Healthcare Claims: Finding Rework and Hidden Process Paths with Threadseer

JasonWittenauer — Thu, 17 Sep 2026 22:05:54 GMT

What happens between receiving a claim and resolving it?
A final status tells us whether a claim was paid or denied. It doesn’t show how many reviews it passed through, whether activities repeated, or whether a denial was followed by an appeal. This report uses Threadseer in Power BI to explore those journeys and connect process-level patterns to individual cases.

About the data
The sample contains 12,200 events across 1,880 claims, 12 activities, and 10 distinct process paths. All data is synthetic. The findings illustrate an investigation workflow; they do not represent an actual healthcare organization or industry benchmark.

1. The most common path accounts for less than a third of claims
The largest group (600 claims, or 31.9%) follows this sequence:

Claim Received → Eligibility Check → Coding Review → Adjudication → Payment Approved → Paid

The remaining 68.1% follow other routes. Those variations include additional reviews, a shorter payment path, requests for information, corrections, denials, and appeals. The most common route provides a useful comparison point, but a different route does not automatically indicate a problem. For example, 250 claims include Medical Review before continuing to payment, without repeating an activity.

2. More than one in four claims repeats an activity
Across the sample, 500 claims (26.6%) contain rework, identified by repeated activities within a case. Three paths account for these cases:

220 claims repeat Eligibility Check after Need More Info.
180 claims repeat Coding Review after Provider Correction.
100 claims return to Adjudication after a denial and Appeal Review.

These are different investigation targets. Information requests, coding corrections, and appeals should be examined separately because they may have different causes and operational requirements. Repetition alone does not establish that the work was unnecessary or preventable.

3. A denial is not always the final outcome
The sample includes 100 claims that are denied, pass through Appeal Review, and ultimately reach Paid. Another 280 claims end at Denied.

That distinction matters when interpreting outcomes. Counting every claim that encountered a denial would answer a different question from counting claims whose final recorded outcome was denial. Following the full sequence makes that difference visible.

From patterns to investigation
The eligibility and coding loops are useful starting points for a closer review. In a real setting, I would investigate what information prompted the return, whether it could have been available earlier, and how elapsed time compares with claims that did not repeat those activities. The event log identifies where to look; additional operational evidence is needed to explain why it happened.

To reproduce the exploration, open the attached PBIX in Power BI Desktop, select Analyze if prompted, and explore:

Process Map and Variants to compare the routes claims follow.
Rework to locate repeated activities.
Bottlenecks to investigate timing along those routes.
Cases to trace the individual sequences behind each pattern.

About Threadseer
I built Threadseer to bring interactive process mining into Power BI. Analysis runs inside the visual runtime without sending event data to an external service. This post uses the same synthetic sample shared in QuickViz, with a closer look at interpreting the claims workflow.

Find Threadseer on Microsoft Marketplace, or visit the getting-started guide to explore it with your own event data.

Veterans Affairs (Standardized Design.VA.gov)

KCoderVA — Thu, 17 Sep 2026 22:00:37 GMT

A Power BI theme aligned to the current U.S. Department of Veterans Affairs Design System (VADS), which builds on the U.S. Web Design System (USWDS). Colors are mapped to VADS semantic tokens, typography, palettes, and styles to allow reports to closely match modern VA.gov digital styling standards.

What's included: the full VADS-derived data color sequences, semantic good/neutral/bad mapping for conditional formatting, and per-visual defaults for cards, tables, matrices, slicers, KPIs, gauges, charts (bar, column, line, area, scatter, waterfall, pie/donut, treemap, funnel, ribbon, etc.), reference/trend/error lines, tooltips, and the filter pane. Titles, axes, gridlines, and legends are pre-styled defaults to ensure a clean, consistent look, with white canvas backgrounds and a very subtle tint on visuals to separate them from the page, while font sizing favors readability. Designed for VA analysts, programmers, designers, or employees who want VADS/USWDS-consistent Power BI reports.

Notes: Licensed under Apache-2.0. & based on the VADS color palette as published on https://design.va.gov. A colorblind-friendly companion theme is available separately in the Microsoft Fabric theme gallery.

FabCon and SQLCon Barcelona 2026 Badges

FabricMau — Thu, 17 Sep 2026 21:53:55 GMT

FabCon and SQLCon Barcelona 2026

Unlock Your Exclusive Conference Badge

Add the exclusive FabCon/SQLCon EU 2026 badge to your Fabric Community profile.

How to get the badge:

Make sure you are signed in to your Fabric Community account.
Like or comment on this post using the community profile where you would like to receive the badge.
Complete this action by October 5, 2026.

Badges will be added to eligible community profiles after the conference once participation has been reviewed.

Community Lounge hours

Tuesday, September 29
11:30 AM to 5:00 PM

Wednesday, September 30
9:00 AM to 4:00 PM

Thursday, October 1
9:00 AM to 2:00 PM

Explore the Community Lounge

During the conference, the Community Lounge will include:

Community theater sessions
Meetups and community conversations
Certification and learning conversations
The Giveback Activity
Game Hour and community activations
SQL Kicks raffles

Session and activity times may change. Please review the final schedule displayed in the Community Lounge and included in the official event materials.

Ready to participate?

Like or comment on this post while signed in to your Fabric Community profile by October 5, 2026.

Storing and parsing HL7 data

ipkus — Thu, 17 Sep 2026 21:38:05 GMT

Any healthcare folks can share what best practices they have found around storing HL7 data for analytics ?

Viewer Role Authorities Changed

doorguy — Thu, 17 Sep 2026 21:18:23 GMT

Users in the 'Viewer' role are now exposed to the semantic models.

Prior to this change, our users had a much cleaner and more intuitive experience. They were presented with the reports and dashboards that we intended for them to consume, without being exposed to the underlying Semantic Models. Now that the Semantic Models are visible, users are seeing additional objects that they do not understand, do not need to interact with, and in many cases may mistake for reports, datasets, or other content they are expected to use.

Organizations have very different Power BI governance models and user populations. A change that intentionally alters what users see within a workspace should, in our opinion, provide administrators with the ability to determine whether that behavior is appropriate for their environment. At a minimum, there should be a supported way to preserve the previous user experience for organizations that do not want to expose these additional objects.

Are any other organizations as frustrated by this change as we are??

It has been explained by support as an "enhancement intended to align the user experience with the documented behavior."

We believe the documentation should have been updated to reflect how the Viewer role is intended to work in practice — not the other way around.

There is no practical use case for Viewer-role users accessing semantic models. This change represents a meaningful degradation in user experience, and we strongly encourage the team to incorporate real-world usage patterns of Power BI Service into future decision-making before changes like this are implemented.

Upcoming changes to legacy Teams and Outlook activities in Fabric Data Factory pipelines

conxu-ms — Thu, 17 Sep 2026 21:00:00 GMT

Beginning October 30, 2026, users will no longer be able to add new legacy Teams or legacy Outlook activities to pipelines.

These legacy activities will no longer appear as options when users add new activities to a pipeline. Existing legacy activity instances can still be edited and used in existing pipelines. New notification scenarios should instead use the modern Microsoft Teams and Outlook 365 Email activities.

Support Managed Private Endpoint for Azure DocumentDB (with MongoDB compatibility)

morten-gn — Thu, 17 Sep 2026 19:42:37 GMT

Fabric does not offer a secure way to connect to Azure DocumentDB (with MongoDB compatibility).

It is currently only supporting the Azure Cosmos DB for MongoDB

From SAP, FSM and SharePoint silos to a Fabric Lakehouse: Medallion + Direct Lake

KavikaRoy26 — Thu, 17 Sep 2026 19:38:09 GMT

We recently moved a building-services client at DataToBiz off a reporting setup where data sat across SAP S/4HANA, SAP FSM, SharePoint, and flat files. Pulling together a single report meant manual extraction and reconciliation, with some reporting cycles taking up to two weeks.

We rebuilt this on Microsoft Fabric. Dataflows Gen2, Pipelines, and Notebooks handle ingestion from the four source types through automated batch workflows, landing in a single Lakehouse on OneLake with a Bronze/Silver/Gold structure. Spark notebooks and pipelines handle large-scale transformation, cleansing, and KPI standardization across the source systems.

Power BI semantic models with DAX and RLS handle role-based access. Reports use Direct Lake mode to work with data in OneLake without the traditional import-based refresh approach.

Result: reporting went from 10–14 days to under a day, with 20+ reports automated across roughly 60 users.

The interesting part wasn't just bringing the data into Fabric. It was standardizing KPIs when different enterprise systems represented the same metric differently.

Question for the group: how are you handling KPI standardization when multiple enterprise systems define the same metric differently? If anyone has a scalable, metadata-driven approach for that, please share.

Enable Analyze in Excel / live connection for external (cross-tenant) users

mholtmailctpcom — Thu, 17 Sep 2026 19:26:54 GMT

Enable Analyze in Excel / live connection for external (cross-tenant) users

Hide visuals when a page is navigated away from

ACraig08 — Thu, 17 Sep 2026 19:03:25 GMT

Hello, I have kind of an odd question. I was wanting to create a custom page navigator using buttons and bookmarks. I know there is a page navigator button that creates one for you, but it just takes up too much space on the page, so I need to create something that can be hidden and opened with a button. I put a menu button in the top right of my page that has a bookmark action so when it is selected it opens up a custom page navigation that is made from a shape, the buttons for the pages, and another menu button. I grouped those together and called it Menu Group for ease.

The menu button shown in that Menu Group is connected to another bookmark that hides the Menu Group.

All of that works great. However, the bump I have run in to now is that when you select a page button, it takes you to the page no problem, but it leaves the Menu Group visible on the page you just navigated away from.

Is there a way to make it so that when I navigate away from a page, it hides the Menu group? Or defaults to a specific bookmark where the menu is hidden.

It would be nice if the page navigation could be a dropdown or something, but I don't think that is possible.

Export data from Power BI

hchava5292 — Thu, 17 Sep 2026 18:55:24 GMT

Hello All,
I am aware that exporting data directly from a Power BI visual is subject to row limitations. CSV exports are limited to approximately 30,000 rows, while Excel exports can support up to approximately 150,000 rows.

My data is stored in Microsoft Fabric OneLake, and the Power BI report uses a live connection to a published semantic model.

We have a data-export requirement where users need to:

Apply filters within the Power BI report.
Select the fields they want to include through a simple checkbox or slicer.
Dynamically add selected fields to a table visual.
Remove fields from the table when they are unchecked.
Export the resulting filtered dataset to Excel or CSV.
Export more data than the standard Power BI visual export limits allow.

Field parameters can address the dynamic column-selection requirement, but the standard visual export limits are still a concern.

I am looking for the best possible solution that allows users to export large datasets while preserving:

The filters applied in the Power BI report
The fields selected by the user
Semantic model security and business logic
A straightforward user experience
Support for Excel or CSV output

Thanks in Advance

Power BI Sentence Template Tooltip – How to Display Measure Values on Separate Rows?

PrasadRP — Thu, 17 Sep 2026 18:48:44 GMT

Hi Everyone,

I am trying to replicate the default Power BI tooltip using the Sentence Template tooltip because of a business requirement.

I have created a DAX measure that performs the required calculations and concatenates multiple values into a single text output. I am trying to use UNICHAR(10) to display each value on a separate line/row.

However, UNICHAR(10) does not appear to create a line break when the measure is displayed in the Sentence Template tooltip. All the values are displayed on the same line.

Example

I have a measure similar to the following:

Tooltip Text =

"Sales: " & FORMAT([Sales], "#,##0")

& UNICHAR(10) &

"Profit: " & FORMAT([Profit], "#,##0")

& UNICHAR(10) &

"Margin: " & FORMAT([Margin], "0.0%")

I would like the tooltip to display something like:

Sales: 1,250,000

Profit: 350,000

Margin: 28.0%

Instead, the Sentence Template tooltip displays it approximately like this:

Sales: 1,250,000 Profit: 350,000 Margin: 28.0%

What I am looking for

Is there any way to create line breaks / separate rows within a Sentence Template tooltip using a DAX measure?

More specifically:

Does Sentence Template support UNICHAR(10) or any other Unicode character for line breaks?
Is there another DAX approach that can force the concatenated measure values onto separate rows?
Is it possible to replicate the default Power BI tooltip layout using Sentence Template while keeping the values dynamically calculated?
If Sentence Template does not support this, is there any workaround that allows us to achieve the same result without creating a separate tooltip page?

Any guidance or alternative approach would be greatly appreciated.

Thanks in advance!

Threadseer: Interactive Process Mining in Power BI

JasonWittenauer — Thu, 17 Sep 2026 18:35:06 GMT

Discover how a process actually works from the event data already in Power BI.
Threadseer is a custom visual I built to bring process mining directly into Power BI. This interactive example explores a synthetic healthcare-claims workflow, showing how claims move from intake to resolution, where paths diverge, and where work repeats.

About the sample
The attached report contains 12,200 events across 1,880 cases and 10 process variants. All data is synthetic, so you can freely explore the report without exposing patient or business information.

With Threadseer, you can:
• Follow the process: Explore an interactive map of activities and transitions.
• Compare paths: Select variants to see common and alternative routes.
• Investigate bottlenecks: Examine delays between activities and inspect the contributing cases.
• Trace rework: Find repeated activities and follow individual case timelines.

To use Threadseer with your own event log, start with three required fields: Case ID, Activity, and Timestamp. Analysis runs inside the Power BI visual runtime, without sending event data to an external service.

Explore Threadseer
Find Threadseer on Microsoft Marketplace to use it in your own Power BI reports, or visit the getting-started guide for setup instructions.

Support Encrypted Sensitivity-Labeled Excel Files in Power Query

ewarstdhyjugkhi — Thu, 17 Sep 2026 17:19:28 GMT

Description

Currently, Power Query Online and Power Query in Excel are unable to access encrypted Excel files. Excel files with sensitivity types other than Public or Non-Business can be encrypted and therefore cannot be accessed through Power Query Online or Power Query in Excel.

We would like to request support for accessing and processing sensitivity-labeled encrypted Excel files through Power Query while honoring the security and access permissions associated with the sensitivity label.

Business Impact

Organizations increasingly use sensitivity labels and encryption to protect business-critical and confidential information. At the same time, these Excel files may need to be used as data sources for reporting, analytics, and data transformation scenarios.

The current limitation can prevent customers from using protected Excel files directly with Power Query Online or Power Query in Excel, requiring them to reconsider either their data protection approach or their Power Query workflow.

Feature Request

Please consider enabling Power Query Online and Power Query in Excel to:

Authenticate authorized users when accessing sensitivity-labeled encrypted Excel files.
Access encrypted Excel files when the signed-in user has appropriate permissions.
Honor the sensitivity label, encryption, and associated access controls while processing the workbook.
Provide Power Query functionality without requiring customers to remove or downgrade the sensitivity protection applied to the source Excel file.

This enhancement would help organizations maintain their information protection requirements while continuing to use Power Query for their data transformation and analytics needs.

Soft delete for On-premises data gateways in Microsoft Fabric (Preview)

goupadhy — Thu, 17 Sep 2026 17:00:00 GMT

Deleting a gateway is currently permanent, so administrators must recreate it if it is removed accidentally. With soft delete, supported gateways are retained for 30 days after deletion, giving authorized administrators time to restore them before permanent deletion.

Soft delete feature currently is only available for standard mode of on-premises data gateways in Microsoft Fabric (Preview). Personal mode gateways and virtual network data gateways are not currently supported.

What’s new

Soft delete introduces a recoverable deletion lifecycle for supported gateway types. When a supported gateway is deleted, it is retained for 30 days by default rather than being removed immediately and permanently. During the retention period, tenant admins and gateway admins can recover from it.

The gateway management page includes the Deleted gateways section which shows Deleted clusters and Deleted members. Gateway admins can view gateway clusters deleted within the 30-day retention window. Each entry in Deleted Clusters can show the gateway name, type, deletion timestamp and available actions, including Restore. Similarly, gateway admins can restore the deleted gateway members together in the Deleted member section. Where enabled, tenant admins may also permanently delete a gateway cluster or gateway members before the retention period ends.

Safer recovery for accidental deletion

Recovery is intended for accidental deletion. An authorized admin can select a deleted gateway and choose Recover. The gateway is then restored at the cluster level with its previous metadata and permissions.

Recovery is not a backup and restore system. It does not recover individual gateway nodes, individual data sources, or partial permission sets as separate objects. Instead, the gateway is recovered as a gateway resource within the soft delete retention window.

This distinction keeps the experience focused: if a gateway is deleted by mistake, admins have a clear path to bring it back without rebuilding the resource from scratch.

Governance and retention controls

Soft delete also gives organizations a clearer lifecycle model for gateway deletion. Deleted gateways are retained for 30 days by default. After the retention period ends, the gateway is automatically and permanently deleted, and recovery is no longer available.

Visibility and recovery are permission aware. Tenant admins and gateway admins can delete and recover gateways and, where supported, permanently delete them. Non-admin users cannot recover deleted gateways. If a user encounters a deleted gateway, the experience can direct them to contact a gateway admin for recovery.

API and audit support

API and audit logs aren't supported in the preview for soft delete.

Gateway soft delete is also planned for automation scenarios. Fabric and gateway APIs could expose soft-delete and recovery actions, helping admins include gateway lifecycle operations in existing workflows.

In the future, audit logs for deletion and recovery actions could help organizations track who deleted a gateway, when it was deleted, and when it was recovered. This information could support governance reviews and operational troubleshooting.

Get started

Gateway admins can remove and recover a supported gateway cluster.

Figure: Option to remove a gateway cluster.

To use gateway soft delete, select the gateway management page in Microsoft Fabric and select Deleted gateways

Figure:List of data gateways with options to manage deleted gateways.

Review gateways deleted within the retention window, confirm that you have the required admin permissions, and choose Restore for the gateway you want to restore.

Figure: Deleted gateway clusters and nodes with an option to restore a deleted gateway.

Accidental deletions shouldn't require rebuilding critical gateway resources from scratch. With gateway soft delete, administrators have a straightforward way to recover supported gateways and maintain operational continuity. Explore the feature in your Fabric environment and review the gateway soft delete documentation to understand recovery, retention, and administration options.

Especial SQL Con 2026 Barcelona

SoyDBA — Thu, 17 Sep 2026 16:30:15 GMT

Del 28 de septiembre al 1 de octubre Barcelona acogió la European SQL Conference 2026, uno de los principales puntos de encuentro de la comunidad SQL Server en Europa.

En esta sesión queremos compartir lo que vivimos durante esos días: las novedades y anuncios que se presentaron, las sesiones y temas que más nos llamaron la atención y, sobre todo, qué creemos que merece la pena seguir de cerca durante los próximos meses.

No será únicamente un repaso de novedades. Hablaremos también de nuestra experiencia en el evento, de las conversaciones con otros profesionales de la comunidad y de aquellas ideas que nos hemos traído de Barcelona y que pueden terminar afectando a nuestro trabajo diario con SQL Server, Azure SQL y el resto del ecosistema de datos de Microsoft.

Una sesión abierta y distendida para ponernos al día después de SQL Con 2026 y comentar entre todos qué nos ha dejado esta edición.

Mirroring for Google BigQuery in Microsoft Fabric (Generally Available)

MichaelaIsaacs — Thu, 17 Sep 2026 16:24:38 GMT

Mirroring for Google BigQuery in Microsoft Fabric is now generally available. For organizations running critical workloads on BigQuery, this means a simpler, faster, and lower-cost path to bringing your data into the rest of your analytics estate — with production support, an enterprise SLA, and no pipelines to build or maintain.

Power BI Data Modeling Question

RajiKarthik — Thu, 17 Sep 2026 16:20:52 GMT

I have 2 questions on my data modeling:

For my Power BI report requirement I had to integrate 2 data sources of different grain

Student Data Source(176 columns) - Student identifier, term, program,major, major school, major department, student level, type ,demograhics - ethnicity,citizenship,country origin, sex - Min 1 row/per student to a max of 3 rows based on the major count and program count for each term

Course Data Source(315 columns) - Student identifier, term, course attributes - course number, course section, instructor, active course details,credit hours - Min of 4 row/student to 6 rows for each term

Additionaly, both the datasources have snapshots captured everyday. So for example for each snapshot, the student data source has 9000 records and course data source has 45000 records roughly. Both the tables has 3 years of data and roughly the data count is around 35 million.

Due to the nature of the grain if I combine these flattened tables, it becomes a cartesian join and the performance would be worse. So following are the steps taken:

1. Removed the unwanted columns from the silver layer and moved the refined tables to gold layer:

Student Data Source(81 columns)

Course Data Source (119 Columns)

2. Created bridge tables as below to filter both the data sources on a common slicer

Dim School - union of distinct schools from both the data source

Dim Department - Union of distinct department from both the data sources

Dim Student Level - Union of distinct Student Levels from both the data sources

Dim Term - union of distinct terms from both the data sources

I used the onelake mode semantic model instead of import or Direct query, due to the number of columns and the multiple snapshots.

Earlier, when I tried with import mode, I had delay issues in rendering the data to the report, whenever I made any changes to the datatype/renaming the values,

etc.

It took 45 minutes per change. So I opted for the Directlake mode, which helped in quick data rendering.

Question 1 - Is my approach correct?

Question 2 -

2.1 The dims I created are having blanks, but if I ignore the blanks, my totals match.

2.2 Although it is a union, I see some values missing.

Example: Student Data Source has an additional department Healthcare Management offering a Major, but that department is not in Course Data Source, as they don't offer any courses

when I list the department in a separate slicer, I see the Healthcare Management, but if I add them in a matrix adding school(from dim_school) and the department(from dim_department), and select the Student enrollment metric(built using student data source), healthcare management is missing. What could be the reason?

Manage semantic model settings in context with the default settings pane (Preview)

kayu — Thu, 17 Sep 2026 16:00:00 GMT

The semantic model settings pane is becoming the default way to configure semantic models in the Power BI service. The pane opens alongside your workspace, so you can review and change settings without leaving the current page. It provides the same settings as the full semantic model settings page while keeping the surrounding context visible. The classic settings page remains available during this transition, but it no longer opens first. This change builds on the settings pane preview and provides a more focused experience for managing semantic models.

Why it matters

The pane helps you stay in context while you manage a semantic model. It opens on the right side of the browser window and keeps your workspace visible. Settings are organized into expandable sections and tabs, including refresh, data access, performance, and OneDrive and SharePoint. You can use the search box at the top of the pane to find a setting across all sections and tabs. For example, enter "re" and select View refresh history to go directly to refresh history instead of opening sections one at a time. This organization is especially useful for semantic models with several connection, refresh, or performance settings. You can review a setting, make a change, and return to your work without navigating to a separate page.

What's changing

The settings pane was an optional experience earlier in the preview. As this change rolls out, the pane opens by default when you open settings for a semantic model. The rollout is gradual, so the timing can vary by environment.

The pane includes the settings available on the full settings page. Its main area groups related settings into expandable sections, and the tabs at the top organize settings by category. Use the search box when you know the setting you want or browse the sections to review related options together.

If you prefer the full-page experience, select Open settings page at the bottom of the pane. The classic page opens in the same browser window. This option can help when you want to compare settings across semantic models or continue using a familiar workflow during the transition.

The classic settings page will be retired over time, so the switchback option is intended to support the transition. We're also working to consolidate related settings, including scheduled refresh and data connections. These planned improvements apply to the settings pane. The preview experience and behavior might change before general availability.

Figure: Switch from the semantic model settings pane to the classic settings page.

Next steps

Understand Semantic model permissions in Power BI.
Learn how to use the pane in Manage semantic model settings in the settings pane.
Open the settings for one of your semantic models and explore the grouped sections and search.
Share feature suggestions through Fabric Community Ideas.
Share feedback about the preview in the comments.

"How to translate elements per user language, alongside RLS by country"

ario0991 — Thu, 17 Sep 2026 15:52:49 GMT

I am working on a project to consolidate two Business Intelligence solutions into one, using Row-Level Security (RLS) based on the data's country of origin (Spain and Italy); I have a clear understanding of how RLS works. However, I am unsure about the translation aspect: how can I ensure that text boxes are translated according to the user accessing the report? The same applies to chart axes, titles, and report pages—how can I manage the translation of these various elements?