Aesthetics360

Built AI native rather than retrofitted, by the company's own account, with a multi agent architecture in which every component is model output: Scribe for capture, Notes for documentation, Plan for treatment planning, and an analytics layer above them. No services business or legacy platform underneath.

Two things push this down. A360 Notes is marketed as producing chart ready output without manual edits or post visit work, which sells the absence of review as a benefit rather than describing a review step, and no confidence threshold, acceptance rate or clinician sign off gate was located.

Separately, A360 Plan delivers AI powered treatment recommendations and personalised care plans, which is clinical recommendation rather than documentation, with no oversight model described for it either.

In elective medicine, where the recommended treatment is also the thing being sold, an unreviewed recommendation engine deserves more scrutiny than it would elsewhere, not less.

The pipeline is described with unusual mechanical specificity for this category, naming medical named entity recognition, intent detection and contextual classification as distinct stages, and the domain tuning claim is illustrated concretely rather than asserted: the phrase eleven lines can mean facial anatomy or units of product depending on context, an ambiguity a general transcription model would resolve wrongly. That is a real demonstration of domain understanding.

Graded C nonetheless because nothing is measured: no accuracy figure, model card, named models or evaluation methodology was located, which is the same call applied to DeepCura for a comparably detailed architecture with no numbers behind it.

One architectural commitment does real work on this axis: redaction and encryption performed on the capture device, so identifiers are stripped before transmission rather than after arrival. Where that holds, the parties downstream receive content that has already had identifiers removed, which bounds the chain by design rather than by policy and is the same class of engineered protection this index credits in the local processing and no recording architectures elsewhere in this lane.

It is also verifiable in principle, unlike a retention promise. One structural tension belongs beside it and a buyer should hold both at once. The platform's stated value depends on analysing every transcript for patterns, opportunities and performance feedback, so retention and reuse of conversation content is not incidental here, it is the business model.

Those are not contradictory, since identifiers can be redacted while content is kept and mined, but a buyer should understand that conversations persist and are analysed by design rather than assuming redaction implies disposal. On enumeration there is nothing: no model, model family or provider, no hosting arrangement and no sub processor list was located. Ask what redaction actually removes, who receives the redacted content, and for a sub processor list.

No study, controlled evaluation, accuracy benchmark, third party rating, named customer or deployment count was located. Available testimony is brief and unattributed to a named practice. Claims of significant reductions in documentation time and more consistent notes carry no denominator or method.

One genuinely strong architectural claim, held against one structural tension.

The strong part is on device redaction and encryption at capture, meaning identifiers are stripped before transmission rather than after arrival, which is engineered privacy of the kind this index credits in voize and Veradigm.

The tension is that the platform's stated value depends on analysing every transcript for patterns, opportunities and performance feedback, so retention and reuse of conversation content is not incidental to this product, it is the business model. Those are not contradictory, since identifiers can be redacted while content is kept, but a buyer should understand that conversations are retained and mined by design.

No retention schedule or training use statement was located.

HIPAA compliance is claimed, and the product is described as designed for regulated environments with workflows aligned to HIPAA, PHI and audit requirements.

One inconsistency is worth noting: some materials say fully HIPAA compliant while others describe HIPAA aligned infrastructure, and aligned is a materially weaker word that this index tracks elsewhere as a near attestation. Business associate agreement terms are not published.

A second pass located no named or dated attestation, no SOC 2 report of either type, no HITRUST certification, no ISO 27001 and no trust centre.

Read the compliance language carefully here, because it varies across the vendor's own surfaces and the weaker version sits on the page written for buyers. Marketing copy states the scribe is fully HIPAA compliant, with on device redaction and encryption at capture. The product frequently asked questions state instead that it uses enterprise grade, HIPAA aligned infrastructure. Aligned and compliant are not the same claim, enterprise grade is a marketing phrase rather than a standard, and there is no certification for the health privacy rule in any case, so none of these amounts to an examination by an independent party. On device redaction is the one concrete and checkable technical claim in the set, and it is worth asking about specifically because it would be a real control if implemented as described.

The architecture raises the stakes rather than lowering them. This is a multi tenant platform as a service with white labelling, and it operates an agent exchange through which channel partners, developers and enterprises build and deploy their own agents inside the platform. Code the vendor did not write therefore processes protected health information in a shared environment. Tenant isolation, whatever review is applied to partner authored agents, and what those agents can reach are the questions that matter most on this record, and none of them is publicly answered.

Measured against its own segment an absence is conspicuous rather than merely unstated, since competitors do publish an independently examined posture. The grade reflects what a counterparty can verify before contracting, not a judgement that controls are absent.

No clearance claimed and none required for the documentation component. No United States device pathway attaches to a note a licensed clinician reviews and signs.

What surrounds the scribe is the reason this record matters, and it is the sharpest version of the revenue boundary anywhere in this category. A360 Plan is described as capturing every revenue relevant signal in the consultation and turning it into a structured long term care plan built at the point of care. Third party product material describes the platform as identifying upsell opportunities and tailoring treatment recommendations using sentiment analysis and patient preferences. The company describes itself as an operating layer that turns clinical conversations into measurable revenue outcomes, and markets sales opportunity detection and conversion rate improvement alongside the clinical documentation.

The structural point is specific to elective aesthetic medicine and worth stating plainly. Across the rest of this category the coding boundary matters because documentation shapes reimbursement for care already delivered. Here there is no payer intermediary, and the clinician making the recommendation is the party selling the treatment. A system deriving treatment recommendations from revenue signals and patient sentiment places commercial optimisation inside the clinical recommendation itself rather than downstream of it. That is a different and larger conflict than the coding pattern elsewhere in this index, and it is not mitigated by clinician review in the way a draft note is, because the clinician's own interest runs the same direction as the system's.

None of this is regulated as a device in the United States. What governs it is professional standards on informed consent and on separating clinical judgement from commercial interest, together with advertising and consumer protection law. Ask what distinguishes the clinical recommendation from the sales recommendation inside a generated plan, and whether a patient reading it could tell.

Graded on disclosed design, not on any allegation, and the grade rests on what the vendor markets rather than anything uncovered.

A360 Scribe is stated to capture revenue signals alongside clinical content, specifically patient motivations, timing cues, decision language, financial framing and pricing discussion. A360 Plan is described as capturing every revenue relevant signal in the consultation. The platform then analyses every transcript to surface conversion leaks, revenue, reactivation and campaign opportunities, and to give staff performance feedback that no traditional training can.

Two separate concerns follow, and neither has any published governance framework, patient disclosure or fairness content behind it. First, secondary use: a patient consents to a recording for their clinical record, and the same recording drives a system optimising how to sell them further elective procedures. Second, workforce surveillance: analysing every consultation to score staff performance is employee monitoring conducted through patient conversations, the concern this index tracks elsewhere in workforce analytics.

In fairness, aesthetic medicine is openly commercial, pricing genuinely is discussed in these consultations, and recording what was recommended, deferred or declined is legitimate clinical record keeping. The grade is for the undisclosed secondary use of clinical recordings, not for the specialty being commercial.

Two passes located no accuracy or error figure, no published limitations and no warranty, indemnity or remediation commitment. The technical description is better than most at this size, naming distinct pipeline stages rather than gesturing at artificial intelligence, and it includes a genuinely instructive demonstration of the domain problem: a phrase that can denote facial anatomy or units of injected product depending on context, which a general transcription model would resolve wrongly.

That demonstrates the problem has been understood. It does not measure how often the system resolves it correctly, and in this specialty the difference between those two readings is a dosage, so the ambiguity the vendor uses to illustrate its expertise is also the error with the clearest patient consequence. A vendor that can name its hardest case that precisely is well placed to publish how often it gets that case right, and does not. Ask for accuracy on the specific ambiguous constructions the vendor cites, and for what it commits to when a quantity is transcribed wrongly.

Integration is offered as a capability rather than a list: the product can run standalone or connect to EMRs and other systems through APIs, and the company maintains a dedicated proposition for EMR vendors alongside an agent exchange and studio. No named electronic record integration, architecture or write back mechanism was verified in this pass, so depth cannot be assessed.

Partial. On device redaction and encryption at capture is a real and unusual deployment property, meaningfully stronger than server side redaction because identifiers never leave the device unprotected. Against that, no hosting region, residency option or sub processor detail was located, and the analytics layer implies substantial cloud side retention.

No published rate card, tier structure or pricing model. Enterprise buyers are directed to a consultative assessment. Given the platform spans documentation, treatment planning, analytics and marketing activation, a buyer cannot currently determine which components are licensed together or separately.

Opens a segment nothing else in this index reaches: elective and largely cash pay aesthetic medicine, covering aesthetics, plastics and venous care, sold to medical spas as well as larger clinics, hospitals and networks. That setting has genuinely different documentation needs from insurance funded care, since the note supports consent, expectation setting and product traceability rather than a claim.

The product reflects that, documenting what was recommended, deferred or declined and recording expectation setting in real time to reduce downstream misalignment, which is a defensible medico legal purpose in a specialty with high patient dissatisfaction risk. No specialty count or language coverage published.