Skip to main content Scroll Top

AI Diagnostics Software: How Diagnostic AI Is Built, Validated and Deployed

Updated November 2026 · Written and maintained by the Progression Agency strategy team

AI diagnostics software is judged on one sentence before anyone looks at the model: the intended use. Whether the output moves a study up a reading list, measures something on an image or suggests a diagnosis decides who acts on it, what evidence it needs and which FDA path fits. FDA’s list of AI-enabled medical devices held 1,614 entries at its September 4, 2026 update, and 1,230 of them name radiology as the lead panel. This page follows a diagnostic model from that sentence through data, labels, validation, regulatory files, deployment and monitoring. Progression’s own developers build the software, and the team is based in New York.

On this page · 14 sections
  1. Two sentences, one chest X-ray model
  2. AI diagnostics starts with the intended use sentence
  3. Where AI in diagnostics is already authorized
  4. Data for AI medical diagnosis models
  5. Labels and the reference standard
  6. Validating AI in diagnostics before anyone relies on it
  7. The FDA path for diagnostic software
  8. Change control plans for model updates
  9. Generative AI and healthcare ChatGPT tools near the diagnosis
  10. Fitting the model into the reading workflow
  11. Monitoring after launch
  12. What AI diagnostics software costs to build
  13. How Progression’s developers build diagnostic AI
  14. Before the first line of code

Building health software without a model? Patient portals, EHR connections and clinical workflow tools that carry no diagnostic model are covered on our healthcare software development page.

Examples marked “Illustrative example.” are hypothetical; no real patient, device, hospital or company is shown.

Two sentences, one chest X-ray model

Picture a hypothetical team with a model that looks at adult chest X-rays. Described one way, it flags studies with a suspected finding so a radiologist reads them sooner. Described another way, it tells a patient whether the image shows pneumonia.

Two drawn boxes. Sentence A says the hypothetical model flags adult chest X-rays so a radiologist reads them sooner, with the radiologist still reading every study. Sentence B says the same model tells a patient whether the X-ray shows pneumonia, with no specialist in between.Two drawn boxes. Sentence A says the hypothetical model flags adult chest X-rays so a radiologist reads them sooner, with the radiologist still reading every study. Sentence B says the same model tells a patient whether the X-ray shows pneumonia, with no specialist in between.
Illustrative example. The same hypothetical model described by two intended use sentences.

The weights are identical, yet the two descriptions make two different products. The first keeps a specialist between the software and every result; the second puts the software’s answer in front of a person with no one to interpret it. The user, the evidence, the labeling and the regulatory questions all change with one sentence, which is why it gets written first.

  • Write the intended use before choosing data.
  • Name the first person who sees the output.
  • Name the setting: emergency department, outpatient clinic, home.
  • Let every later stage answer to that sentence.

AI diagnostics starts with the intended use sentence

Most diagnostic models fall into a handful of jobs. The table sets each job beside example wording, the person who acts on the output and the questions the sentence raises for the build.

Six jobs a diagnostic model can do, and what each sentence raises
What the output doesExample wordingWho acts on itWhat the sentence raises
PrioritizeMoves suspected cases up a reading listThe specialist who reads every studyTime to read, missed flags, the order of the list
Detect and markDraws a box or a heat map on a possible findingThe reader, who accepts or dismisses each markFalse marks per study, marks a reader ignores
MeasureReports a volume, a length or a ratioThe clinician who signs the reportAgreement with manual measurement across scanners
Suggest a diagnosisNames a likely condition with a scoreThe clinician making the diagnosisEvidence for each condition named, and subgroup results
Give a patient a resultTells a person what a test showsThe patient, possibly aloneReadability, follow up instructions, a much higher bar
Draft text for a clinicianWrites a first draft of a report or summaryThe clinician who edits and signs itErrors of omission, invented findings, review time

Who reads the output first?

A specialist who reads every study can catch a wrong flag, so a triage tool’s errors cost time rather than a missed diagnosis. A patient reading a result alone has no such check, so a sentence that reaches patients needs far more evidence, plainer words and clear next steps.

Words that widen a claim

Small verbs change what a team must prove. Keep them out of the sentence, the screens and the sales copy unless the evidence covers them.

  • “Diagnoses” where the software actually flags.
  • “Rules out” where the test only measured detection.
  • “Replaces” where a reader still signs.
  • “All” or “every” in front of a finding.
  • A setting or age range the test data never covered.
1,614: Entries on FDA's list. AI-enabled devices authorized for US marketing, at the September 4, 2026 update.
1,230: Radiology as lead panel. The largest share of the list by far.
1,553: Numbers beginning with K. Most entries reached the market through a 510(k).
18: Safe harbor identifiers. Removed from data under 45 CFR 164.514(b)(2).
10: GMLP guiding principles. In IMDRF's final document from January 2025.
3: Parts of a change control plan. Planned changes, the method and an impact assessment.

Where AI in diagnostics is already authorized

FDA keeps a list of AI-enabled medical devices authorized for marketing in the United States. Each device on it met the applicable premarket requirements, and each entry links to the database record with its public summary. At the September 4, 2026 update the list held 1,614 entries, with final decisions running from September 1995 to June 29, 2026.

A horizontal bar chart of entries on FDA's AI-enabled device list by lead panel: radiology 1,230, cardiovascular 154, neurology 73, anesthesiology 30, gastroenterology and urology 27, hematology 22 and all other panels 78.A horizontal bar chart of entries on FDA's AI-enabled device list by lead panel: radiology 1,230, cardiovascular 154, neurology 73, anesthesiology 30, gastroenterology and urology 27, hematology 22 and all other panels 78.
Radiology is the lead panel for 1,230 of the 1,614 entries on FDA’s list.

By submission number, 1,553 entries begin with K, the 510(k) prefix; 40 begin with DEN for De Novo; and 21 begin with P for premarket approval. Radiology is the lead panel for 1,230 entries, cardiovascular for 154 and neurology for 73.

A bar chart of entries on FDA's AI-enabled device list by year of final decision: 65 in 2018, 80 in 2019, 114 in 2020, 129 in 2021, 162 in 2022, 226 in 2023, 235 in 2024 and 335 in 2025.A bar chart of entries on FDA's AI-enabled device list by year of final decision: 65 in 2018, 80 in 2019, 114 in 2020, 129 in 2021, 162 in 2022, 226 in 2023, 235 in 2024 and 335 in 2025.
Entries on FDA’s AI-enabled device list rose from 65 in 2018 to 335 in 2025.

What does the list leave out?

FDA says the list is not comprehensive. Devices were identified mainly from AI terms in the summary descriptions of their marketing authorizations and from their classification, and devices whose decision summaries were not yet published wait for a later update. FDA also says it will explore ways to tag devices built on foundation models, from large language models to multimodal designs.

Why imaging leads the count

Images are already digital, stored in standard formats and read by specialists who can check a model’s output. That makes imaging a natural first home for diagnostic software, and it means a new imaging model meets an established set of products and reviewers’ expectations.

  • Search the list by product code to find devices with a similar intended use.
  • Read the public summaries for how others described their testing.
  • Note which entries mention a change control plan.
  • Check the update date before quoting any count.

Data for AI medical diagnosis models

Training data usually comes from a hospital’s imaging archive, lab system or EHR, or from other hospitals under a data use agreement. Before it reaches a training run, the data is de-identified under HIPAA’s standard in 45 CFR 164.514, which offers two routes.

The first is expert determination: a person with appropriate statistical and scientific knowledge finds the risk of identifying anyone very small and documents the methods and results. The second removes 18 listed identifiers of the individual and of relatives, employers or household members, and the covered entity has no actual knowledge that what remains could identify someone. A re-identification code is allowed if it is not derived from the person’s information and its mechanism is not disclosed.

Identifiers in the rule and where they hide in diagnostic data
Identifier type in the ruleWhere it hides in diagnostic dataWhat the pipeline does
NamesImage headers, report text, scanned requisitionsStrip or replace with a study code
Dates except the yearStudy, birth, admission and discharge dates in headers and reportsKeep the year or shift dates consistently by patient
Medical record and account numbersHeader fields and report footersReplace with a code not derived from the number
Device identifiers and serial numbersScanner serials in image headersRemove, keeping only the scanner model where needed
Full face photographs and comparable imagesClinical photos, some head and neck studiesExclude, crop or review case by case
Geographic subdivisions smaller than a stateAddresses and ZIP codes in reportsRemove, with the rule’s three digit ZIP exception only where it applies
Any other unique codeText burned into pixels, free text notesScan pixels and text, and remove what is found

Pixels and headers carry identifiers

Image files carry text fields with names, dates, record numbers and scanner serials, and some images have text burned into the pixels themselves. A pipeline that cleans the fields but never scans the pixels can leave a name on the image. Head and neck studies need a separate look under the rule’s line on full face photographs and comparable images.

Split by patient, then by site

Split training, tuning and test data by patient, never by image, so no person appears on both sides. Then hold one or more sites out entirely, so the final test shows how the model behaves on scanners, protocols and populations it has never met.

  • Record which archive and date range each study came from.
  • Log the de-identification method used for each batch.
  • Keep the code key, if any, away from the training environment.
  • Freeze the test set before model work begins.

Labels and the reference standard

A model learns whatever the labels say, so the definition of the right answer is a design decision. The reference standard might be a specialist read, a consensus of several readers, a pathology result or a later clinical outcome, and each choice costs different time and money.

Write the labeling guide first

The guide says what counts as present, absent and uncertain, how to mark location, and what to do with poor quality studies. Readers label a pilot batch, the team compares their answers, and the guide is revised before the full set is labeled.

When two readers disagree

Disagreement is information. Send split cases to an adjudicator, record both original answers, and track agreement rates by reader and by finding, because a finding readers cannot agree on is one a model cannot learn cleanly.

  • Define present, absent and uncertain in writing.
  • Pilot the guide on a small batch.
  • Adjudicate disagreements and keep the original reads.
  • Track agreement by finding.

Validating AI in diagnostics before anyone relies on it

Validation answers whether the intended use sentence holds on data the model never saw. Each measure answers a different question, and each can mislead on its own, so a report shows several together with the counts behind them.

Validation measures for a diagnostic model and where each misleads
MeasureThe question it answersWhere it misleads
SensitivityOf the cases that have the finding, how many did the model catch?Looks high when the hard cases were left out of the test set
SpecificityOf the cases without it, how many did the model leave alone?Hides the daily burden when the finding is rare
Positive predictive valueWhen the model flags a case, how often is it right?Changes with prevalence, so it shifts from site to site
Negative predictive valueWhen the model stays quiet, how often is that right?Can look reassuring simply because the finding is rare
Area under the ROC curveHow well scores separate positive from negative cases overallSays nothing about the threshold the product will actually use
CalibrationDoes a score of 0.8 mean right about 80 percent of the time?Ignored when only a yes or no is shown, then trusted anyway
Time to readDid flagged studies reach a reader sooner?Measured in a lab instead of the real worklist

Test sets from sites the model never saw

A model tested only on data from its training hospitals carries that hospital’s scanners, protocols and patient mix into its score. Hold out whole sites, report results per site and per scanner model, and treat a large gap between sites as a finding to explain before launch.

A drawn checklist with seven rows. Five are ticked: intended use written, split by patient, a site held out, reference standard defined and results by scanner. Two are open: subgroup results by age and sex, and reading time in the real worklist.A drawn checklist with seven rows. Five are ticked: intended use written, split by patient, a site held out, reference standard defined and results by scanner. Two are open: subgroup results by age and sex, and reading time in the real worklist.
Illustrative example. A hypothetical validation plan with two open items.

Does the nondiscrimination rule reach decision support tools?

It reaches covered entities that use them. Under 45 CFR 92.210 a covered entity must not discriminate on the basis of race, color, national origin, sex, age or disability through patient care decision support tools, has an ongoing duty to make reasonable efforts to identify tools whose input variables measure those traits, and must make reasonable efforts to mitigate the risk. Subgroup results in the validation report give a hospital what it needs for that review.

  • Report results by age band and sex at minimum.
  • List every input variable the model uses.
  • Flag any input that measures a listed trait.
  • Repeat the subgroup report after each update.

Have a model idea and a data archive?Tell us the intended use sentence you have in mind and where the data sits. You get a free proposal for the build, the records and the price.

Get a free proposalTell us about a project you’d like help with.

The FDA path for diagnostic software

FDA uses the IMDRF definition of Software as a Medical Device: software intended for one or more medical purposes that performs them without being part of a hardware medical device. It is one of three types of device related software, beside software in a medical device and software used to make or maintain one.

FDA premarket submissions a diagnostic model team weighs
FDA submissionHow FDA describes itWhen a diagnostic model team looks at it
Premarket Notification 510(k)For Class I and II devices that are not exempt from premarket review or subject to another submissionA predicate device with the same intended use already exists
De Novo Classification RequestFor novel low to moderate risk devices with no predicate deviceThe model is new and the risk is low to moderate
Premarket Approval (PMA)For Class III devicesThe output carries the highest risk
Investigational Device Exemption (IDE)For investigational devices used in a clinical study to collect safety and effectiveness dataA clinical study is needed before a submission
Predetermined change control planReviewed inside a 510(k), De Novo or PMA for an AI-enabled deviceUpdates after launch are already foreseeable

FDA’s premarket submissions page describes each route. For AI-enabled devices, FDA has also published a draft guidance from January 2025 on lifecycle management and marketing submission recommendations, which it labels not for implementation, and its Good Machine Learning Practice page points to IMDRF’s final document of January 2025 with 10 guiding principles, building on principles FDA, Health Canada and the UK’s MHRA released in October 2021. The wider device software process sits on our medical device software development page.

Which submission fits a model with no predicate?

FDA describes the De Novo request as the route for novel low to moderate risk devices with no predicate device, while the 510(k) serves Class I and II devices that are not exempt. The intended use sentence and the risk of the output drive that choice, and the manufacturer’s regulatory team makes it.

Change control plans for model updates

Models improve with new data, and each change used to raise the question of a new submission. FDA’s final guidance of August 2025 on predetermined change control plans for AI-enabled device software functions gives another route.

A plan describes the planned modifications, the method to develop, validate and put them in place, and an assessment of their impact. FDA reviews it as part of the marketing submission, so modifications the plan describes can be implemented without a new submission for each one. The guidance applies to AI-enabled devices reviewed through the 510(k), De Novo and PMA pathways.

A six step flow: describe the change, set the method, assess the impact, submit the plan with the device, release changes within the plan, and keep the record.A six step flow: describe the change, set the method, assess the impact, submit the plan with the device, release changes within the plan, and keep the record.
A change control plan in six steps, from the planned change to the release record.

What belongs in the modification list?

Changes the team can already foresee: retraining on data from new sites, a new scanner model, a threshold adjustment, or a performance improvement measured the same way as the original. Changes to the intended use itself sit outside that kind of list.

  • Retraining on new sites, with the same test method.
  • Support for an added scanner model.
  • Threshold tuning inside stated limits.
  • A versioned record of every release.

Generative AI and healthcare ChatGPT tools near the diagnosis

The applications of generative AI in healthcare closest to diagnosis are drafting: a first version of a report, a summary of a long history before a visit, a patient message that explains a result in plain words. In each, a clinician reads, edits and signs.

Where a chat assistant stops

A general chat assistant was not built or tested for a diagnostic intended use, so it drafts and summarizes while the diagnosis stays with the clinician and any regulated software. Keep patient data out of tools that lack the agreements HIPAA requires; our HIPAA compliant software development page covers model provider agreements.

  • Drafts carry a visible label until a clinician signs.
  • Summaries link each statement to the record it came from.
  • Patient messages are reviewed before sending.
  • Every prompt and output is logged with the model version.

Assistants and chat features built for clinical teams are covered on our AI chatbot development page.

Fitting the model into the reading workflow

A diagnostic model earns its keep only where a clinician already looks. That might be the priority order of a worklist, an overlay in the image viewer, a field in a structured report or a note in the EHR. Each placement changes what the reader sees and when.

  • Worklist priority for triage models.
  • Viewer overlays for detection models.
  • Structured report fields for measurement models.
  • EHR notes for results a care team acts on.
  • A clear way to dismiss or correct the output.

Run it silently first

Before go live, run the model on live studies without showing anyone the output, and compare its answers with the readers’ reports. Silent mode shows site specific gaps, integration bugs and timing problems while no patient depends on the result.

Mobile and patient facing pieces of the product are covered on our healthcare app development page, and image pipelines outside medicine on our computer vision development page.

Monitoring after launch

Scanners are replaced, protocols change and patient mix shifts, and the model meets all of it after launch. Monitoring keeps the evidence current. The reports and data feeds that track a model after launch are covered in our guide to healthcare data analytics.

  • Override rate: how often readers dismiss the output.
  • Flag rate by site and scanner model.
  • Input checks for image types the model was not built for.
  • Complaint and error reports routed to the product team.
  • A version log tying each output to the model that produced it.

What should trigger a retraining review?

A sustained rise in overrides, a new scanner or protocol at a site, a shift in flag rate, or a subgroup result that moves. A review decides whether the change fits an existing change control plan or needs the regulatory team’s attention.

What AI diagnostics software costs to build

Diagnostic software is priced by the data work, the integrations and the records the product needs. The bands below run from the typical low to the published high in the US market for software builds; clinical studies and regulatory fees sit outside them.

Diagnostic AI software builds: published US price bands (market ranges only)
BuildTypical low to published highNotes
AI proof of concept$15,000 to $40,000One question tested on retrospective data
AI feature in existing software$15,000 to $60,000A model added to a viewer, portal or EHR tool already in use
Integration or internal tool$30,000 to $100,000Worklist, viewer or report connections
AI MVP$40,000 to $120,000A first product with the model at its center
Platform or portal$75,000 to $400,000Multi site, multi role software around one or more models
US agency or contract development rate$100 to $200 an hourBill rates, not employee wages
Horizontal range bars for an AI proof of concept, an AI feature in existing software, an integration or internal tool, an AI MVP and a platform or portal.Horizontal range bars for an AI proof of concept, an AI feature in existing software, an integration or internal tool, an AI MVP and a platform or portal.
Published US price bands (market ranges only) for five kinds of software build, typical low to published high.

Progression’s price is set in the written proposal after scope and is subject to change. Our AI app development page shows how model features fit into a wider product budget.

What moves the price?

The number of sites and archives, how much labeling and adjudication the reference standard needs, the depth of integration with viewers and the EHR, and the records the regulatory team needs from the software.

Pricing depends on scope and is confirmed in a written proposal. Published prices are subject to change.

How Progression’s developers build diagnostic AI

Progression’s own developers build the software around a diagnostic model: data extraction and de-identification, labeling tools, training and versioning, evaluation, integration and monitoring. The team works from New York and meets clinical and regulatory leads on site when asked.

Five bands. Data: archive extraction, de-identification, patient level splits and data use logs. Labels: labeling guide, reader tools and adjudication queue. Model: training runs, version registry and locked test sets. Evaluation: measures by site, subgroup reports and silent mode logs. Workflow: worklist priority, viewer overlays, report fields and a monitoring dashboard.Five bands. Data: archive extraction, de-identification, patient level splits and data use logs. Labels: labeling guide, reader tools and adjudication queue. Model: training runs, version registry and locked test sets. Evaluation: measures by site, subgroup reports and silent mode logs. Workflow: worklist priority, viewer overlays, report fields and a monitoring dashboard.
The five layers Progression’s developers build around a diagnostic model.
  1. Write the intended use sentence with the clinical and regulatory leads.
  2. Map the archives, agreements and de-identification method.
  3. Build the labeling guide and reader tools.
  4. Train, version and lock the test sets.
  5. Validate by site, scanner and subgroup.
  6. Integrate, run silently, then go live with monitoring.

Who files with FDA?

The manufacturer. Progression’s developers build the software and keep the design, data and test records its regulatory team files from. For strategy before a build, see AI consulting services.

Before the first line of code

Eight answers decide most of what follows. Get them in writing before any model work starts.

A drawn card with eight rows: intended use, user, data, de-identification, reference standard, test sites, regulatory team and change plan. A closing line says the first sprint then builds toward evidence instead of a demo.A drawn card with eight rows: intended use, user, data, de-identification, reference standard, test sites, regulatory team and change plan. A closing line says the first sprint then builds toward evidence instead of a demo.
A drawn checklist card with eight items to settle before building diagnostic AI.
  • The intended use sentence, signed by the clinical lead.
  • The first user of the output.
  • Data sources, access owners and agreements.
  • The de-identification method for each source.
  • The reference standard and who adjudicates.
  • The sites held out for testing.
  • The regulatory team and the likely submission.
  • The updates you expect in the first two years.

What this page leaves out: the Progression Method, proprietary and reserved for clients. Reach out to learn more

Frequently asked questions

What is AI diagnostics software?
It is software that uses a trained model to help detect, measure, prioritize or characterize a medical condition from images, signals or lab data. Its intended use sentence says what the output does and who acts on it.
Who makes the call when AI medical diagnosis software is in the loop?
The person named in the intended use, which in most designs is a clinician who reviews the output before it affects care. A product that gives patients a result directly carries a much heavier evidence load.
How many AI-enabled devices are on FDA’s list?
1,614 entries at the September 4, 2026 update, with final decisions from 1995 to June 29, 2026. FDA notes the list is not comprehensive and is updated periodically.
Which specialty leads AI in diagnostics?
Radiology. It is the lead review panel for 1,230 of the 1,614 entries on FDA’s list, followed by cardiovascular with 154 and neurology with 73.
What is an intended use statement for a model?
It is one sentence saying what the software’s output does, for whom and in which setting. It shapes the data, the validation, the labeling and the regulatory route.
Which FDA submission fits a new diagnostic algorithm?
That depends on risk and on whether a predicate exists. FDA describes the 510(k) for non exempt Class I and II devices, De Novo for novel low to moderate risk devices with no predicate, and PMA for Class III devices.
What is a predetermined change control plan?
It is a plan reviewed with the marketing submission that describes planned model changes, the method to develop, validate and implement them, and an impact assessment, so those changes can ship without a new submission each time.
Can a cleared diagnostic model be retrained?
Yes, within limits. Changes described in an authorized change control plan can be implemented under it; changes outside the plan go back to the regulatory team.
How much data does a diagnostic model need?
Enough positive cases of each finding, from enough sites and scanners, to train the model and still hold out a test set the model never saw. Rare findings, not total volume, usually set the target.
Can patient images train a model under HIPAA?
Yes, once de-identified under 45 CFR 164.514 or used under another permission the rule allows. De-identified data is no longer individually identifiable health information.
What are the two HIPAA de-identification methods?
Expert determination, where a qualified person finds and documents a very small risk of identification, and safe harbor, which removes 18 listed identifiers with no actual knowledge that what remains identifies anyone.
Where do identifiers hide in imaging files?
In header fields such as names, dates, record numbers and scanner serials, and sometimes in text burned into the pixels. Some head and neck images also need review under the rule’s line on full face and comparable images.
What is a reference standard?
It is the agreed definition of the right answer for each case, such as a specialist read, a consensus of readers, a pathology result or a later outcome. The model is trained and tested against it.
Which validation numbers should a buyer ask for?
Sensitivity and specificity with their counts, predictive values at the buyer’s own prevalence, results per site and scanner, and subgroup results by age and sex. One headline number is never enough.
Does the decision support nondiscrimination rule apply to diagnostic AI?
It applies to covered entities that use patient care decision support tools. Under 45 CFR 92.210 they must not discriminate through those tools and must make reasonable efforts to identify and mitigate the risk.
Can generative AI draft radiology reports?
It can produce a first draft that a radiologist edits and signs. The draft is labeled until signed, and every output is logged with the model version.
Can a general chatbot diagnose patients?
A general chatbot was not built or validated for a diagnostic intended use. It can draft and summarize, while diagnosis stays with clinicians and with software built and tested for that job.
What is Good Machine Learning Practice?
It is a set of 10 guiding principles for developing AI and machine learning medical devices, in a final IMDRF document from January 2025 that builds on principles FDA, Health Canada and the UK MHRA released in 2021.
How should a hospital test an AI tool before go live?
Run it in silent mode on live studies, compare its output with the readers’ reports, and check results by scanner and subgroup before anyone sees a flag.
What does AI diagnostics software cost to build?
Published US bands run from $15,000 to $40,000 for a proof of concept and $40,000 to $120,000 for an AI MVP, up to $400,000 for a platform. Progression sets its price in the written proposal.
Does Progression build AI diagnostics software?
Yes. Progression’s own developers build the data pipelines, labeling tools, models, evaluation, integrations and monitoring, and the team is based in New York with on-site sessions on request.

Have a model idea and a data archive?Tell us the intended use sentence you have in mind and where the data sits. You get a free proposal for the build, the records and the price.

Get a free proposalTell us about a project you’d like help with.

Get a free marketing proposal

Tell us what you are trying to grow and we will come back with a plan, not a pitch deck. Same-day reply on weekdays.

Privacy Preferences
When you visit our website, it may store information through your browser from specific services, usually in form of cookies. Here you can change your privacy preferences. Please note that blocking some types of cookies may impact your experience on our website and the services we offer.
Contact Us