SettleTopRegistry
SettleTopRegistry
← Back to the registry
Agent passport

Clinical Conflict Detection

Clinical Conflict Detection is an extension that flags potential conflicts in clinical notes.

Category
Machine Learning
Registry category
Operations & ProductivityWorkflow & Productivity
Vendor
Microsoftlisted as Microsoft Corporation
Location
REDMOND, WA
Reviews
Not rated (0 reviews on the listing)
Listed on
Microsoft Marketplace
Pricing
1 plan listed
Overall Provenance
2.9/10Low
High 7–10Moderate 3–6.9Low 0–2.9

Each fact carries one Provenance score: the average of its Disclosure and Evidence scores, the same rule the page uses for the overall score. Click any score to see the math behind it.

Vendor Provenance

Who actually operates this agent.

7.4 / 10
Data element
Answer
Provenance
Source
Legal entity
Microsoft Corporation
Per the official register
High
Crunchbase company data (microsoft.com), fetched 2026-09-01
HQ address
REDMOND, WA
Per the official register
High
BigPicture company data (microsoft.com), fetched 2026-09-20
Crunchbase company data (microsoft.com), fetched 2026-09-01
Ownership
Publicly traded company
From outside company data
High
BigPicture company data (microsoft.com), fetched 2026-09-20
Industry
Software & Computer Services / Software
Sector Technology
High
BigPicture company data (microsoft.com), fetched 2026-09-20
Employee count
10,001+ employees
From outside company data
High
LinkedIn company data (microsoft.com), fetched 2026-09-03
Founded
1975
From outside company data
High
Crunchbase company data (microsoft.com), fetched 2026-09-01
Revenue
$10B+ estimated annual revenue
Estimate; not from filings
High
BigPicture company data (microsoft.com), fetched 2026-09-20
About
Clinical Conflict Detection is an extension that flags potential conflicts in clinical notes.
Publisher description
High

Build Provenance

What the agent is built on.

1.4 / 10
Data element
Answer
Provenance
Source
Foundation model
Not disclosed on this listing
Low
No source on record
Training data (model)
Not disclosed on this listing
No source discloses model training data
Low
No source on record
Agent framework / tools
Not disclosed on this listing
Low
No source on record
Hosting model
Not disclosed on this listing
Low
No source on record
Version history
1006
Registry saw 5 distinct listing states across 12 captures
High

Reach Provenance

How the agent is distributed and adopted.

4.4 / 10
Data element
Answer
Provenance
Source
Distribution channel(s)
Microsoft Marketplace
Via Dragon Copilot
High
Review volume & rating
Not available
No ratings on the listing
Low
No source on record
Comments (pros)
Not available
No review text on record, so no pros could be drawn from user comments
—
No source on record
Comments (cons)
Not available
No review text on record, so no cons could be drawn from user comments
—
No source on record
Listing tenure
Not disclosed
No listed since date; last updated 2026-08-11
—
No source on record
Multi-channel presence
Single-channel
Listed on Microsoft Marketplace only in the registry
High
Public community signal
Not disclosed
No public GitHub, Discord or community metrics found
Low
No source on record
# installs
Not reported
Popularity index 0.68 on the marketplace; not an install count
—
No source on record
Listing type
Standard marketplace listing
From the listing
High

Data Provenance

What the vendor discloses about data handling.

1.4 / 10
Data element
Answer
Provenance
Source
Operational data sources
Not disclosed
Low
No source on record
Data residency
Not disclosed
Low
No source on record
Retention & deletion
Not disclosed
Low
No source on record
Published documentation
Legal links on the listing: Privacy Policy, License Terms
Links on the listing; documents not fetched by the registry
High
License Terms (opens in a new tab)catalogartifact.azureedge.net
Data access requirements
Not explicitly disclosed
No OAuth scope or permission list found on the listing
Low
No source on record

Compliance Provenance

What standards the vendor meets, and who verified them.

0.0 / 10
Data element
Answer
Provenance
Source
Security
SOC 2
None on record
Low
No source on record
ISO/IEC 27001
None on record
Low
No source on record
ISO/IEC 27002
None on record
—
No source on record
ISO/IEC 27017
None on record
—
No source on record
SOC 3
None on record
—
No source on record
CSA STAR
None on record
—
No source on record
Privacy
GDPR
None on record
Low
No source on record
COPPA
None on record
—
No source on record
FERPA
None on record
—
No source on record
ISO/IEC 27018
None on record
—
No source on record
Health
HIPAA
None on record
Low
No source on record
HITRUST CSF
None on record
—
No source on record
Financial
SOC 1
None on record
—
No source on record
PCI DSS
None on record
—
No source on record
SOX
None on record
—
No source on record
Government
FedRAMP
None on record
Low
No source on record
CMMC
None on record
Low
No source on record
NIST SP 800-171
None on record
—
No source on record
AI
NIST AI RMF
None on record
Low
No source on record
Platform
3rd party certification
None on record
Low
No source on record

What the publisher says

Clinical Conflict Detection helps clinicians identify and review potential clinically inconsistent information within medical documentation, directly inside Dragon Copilot. It is designed for healthcare professionals to support the creation of accurate and consistent clinical documentation as part of their routine workflows.

This extension surfaces potential conflicts—such as laterality mismatches, opposing findings, or inconsistencies across sections of a clinical note—so clinicians can quickly review supporting context and decide whether updates are needed. The clinician remains fully in control of the final documentation.

Key Benefits

Show the rest of the publisher’s description (13 more lines)
  • Improves clinical documentation quality by highlighting potential inconsistencies
  • Supports patient safety and diagnostic confidence through early conflict awareness
  • Reduces manual review effort by automatically flagging relevant sections
  • Builds trust in AI‑assisted documentation workflows

Intended Users

  • Physicians and clinicians creating or reviewing clinical notes
  • Healthcare organizations using Dragon Copilot in clinical workflows

How It Works

Clinical Conflict Detection analyzes clinical documentation and identifies potential conflicts across findings, impressions, assessments, and history. Temporal context — such as when procedures were performed or measurements taken — is considered to ensure accurate conflict detection. Detected conflicts are presented with contextual evidence to support informed review. The feature is advisory in nature and does not make clinical decisions or automatically modify documentation. It is not intended for diagnosis or treatment

Industry & Category

  • Healthcare IT
  • Clinical Documentation Integrity
  • AI‑assisted Clinical Workflow Support

Preview

2 images

Plans and pricing

1 plan listed

Clinical Conflict Detection$0.00/month 1-month subscription

Linked repositories

Unknown

Unknown means this listing does not publish a repository. It is not a statement that the code is closed.

Publisher resources

Sources

Reading the score

Disclosure · how many sources corroborate it

NoneNo source has it. Shown red, because Unknown means Unknown.
1 sourceA single place has it. A listing and its certification page and policy docs on one marketplace count as one source.
2+ contestedTwo or more sources cover it but they do not agree. The disagreement is shown, never dropped.
2+ agreeingTwo or more genuinely separate sources agree: another marketplace, or an outside record.
Steps below are possible but not automated yet, so today they sit open.
SettleTop confirmedSettleTop confirms it directly.

Evidence · what kind of evidence backs it

NoneNo source discloses it.
PublicPublicly available info, such as reviews, listing age, or vendor firmographics like legal entity and headquarters.
Vendor statedThe vendor's own claim on its marketplace listing, website, or policy documents.
Self-attestedThe vendor's self-attested certification or operator program, a marketplace program rather than an independent audit.
Steps below are possible but not automated yet, so today they sit open.
Vendor providedThe vendor hands SettleTop the underlying material, such as an SBOM or a data policy.
Vendor attestedThe vendor signs an attestation to SettleTop.
SettleTop verifiedSettleTop verifies it directly.

The SettleTop steps above are possible but not automated yet, so today they sit open and a perfect 10 is out of reach. Open information like firmographics and reach has fewer steps to climb, so it sits a little higher for the same visible evidence.

Information shown here reflects the best available information at the time of assessment and may be incomplete, outdated, or subject to change. It should be independently verified before being relied upon for any decision. SettleTop is not liable for any errors, omissions, or decisions made in reliance on this information.

Have information about this agent?

Send it to us for consideration

Spot something missing, wrong, or out of date? Share what you know. Every note reaches our team. It does not change the passport by itself: we review it first.

Name

Suggest specific values (optional)
Vendor Provenance

Build Provenance

Reach Provenance

Data Provenance

Compliance Provenance

A note to our team, not a change to the page. Prefer email? Write to support@settletop.com.