FDA-cleared profile

BriefCase

Aidoc Medical, Ltd. · CT/CTA · FDA-cleared (510(k))

Authorized purpose: Notification-only triage of adult head CTA for suspected complete large-vessel and medium-vessel occlusions; compressed previews are informational and the full study remains required for diagnosis.

Clinical role
Triage and notification: AI analyzes head CTA images and flags suspected complete large vessel occlusions and medium vessel occlusions, highlighting cases on a standalone desktop application in parallel to the ongoing standard of care image interpretation.
Images and patients
CT/CTA · Brain/Cerebrovascular
Key limitation
Keep in mind: Head CTA protocol with a 64-slice scanner or higher; scans performed on adults/transitional adults ≥ 18 years of age; slice thickness 0.5 mm – 1.25 mm. All scans that are technically inadequate, including motion artifacts, severe metal artifacts, suboptimal bolus timing or an inadequate field of view.

Overview status: Source-reviewed overview

Report a correction
Clinical details Purpose, workflow fit, evidence, and safety record

Workflow navigation pilot

Workflow role has not yet been reviewed for this navigation pilot.

A tag identifies a documented role; it does not establish compatibility or local acceptance. Methods and sources

  • What does this software do?Authorized purpose: Notification-only triage of adult head CTA for suspected complete large-vessel and medium-vessel occlusions; compressed previews are informational and the full study remains required for diagnosis.
  • Which images or clinical context are in scope?Modality: CT/CTA Anatomy or clinical context: Brain/Cerebrovascular Input: CT/CTA images or data involving Brain/Cerebrovascular; consult the FDA labeling for exact protocol, series, and quality requirements.
  • Who uses it?Intended users: Hospital networks and appropriately trained medical specialists
  • What does the software produce?Output: The AI model flags and sends notifications for suspected positive findings of Large Vessel Occlusion (LVO) and Medium Vessel Occlusions (MeVO) in head CTA images. Notifications include compressed, low-quality, grayscale, unannotated preview images for informational/triage purposes only (not for diagnostic use). The device prioritizes suspect cases on the worklist to facilitate earlier triage.
  • What is its most important limitation?Key limitation: Head CTA protocol with a 64-slice scanner or higher; scans performed on adults/transitional adults ≥ 18 years of age; slice thickness 0.5 mm – 1.25 mm. All scans that are technically inadequate, including motion artifacts, severe metal artifacts, suboptimal bolus timing or an inadequate field of view.

Clinical takeaway. Clinical role: Notification-only triage of adult head CTA for suspected complete large-vessel and medium-vessel occlusions; compressed previews are informational and the full study remains required for diagnosis.

Evidence takeaway. Evidence from the reviewed source record: Aidoc conducted a retrospective, blinded, multicenter study with the BriefCase software to evaluate the software's performance in identifying head CTA images containing Vessel Occlusion (VO) in 342 cases from 5 US-based clinical sites. Ground truth was determined by 3 expert US board certified Neurologists reviewers using majority voting. Sensitivity was 91.3% (95% CI: 83.6%, 96.2%) and specificity was 85.6% (95% CI: 80.6%, 89.7%).

Evidence context

Evidence context not reviewed for this FDA record.

Public-label constraints

Label constraints have not been reviewed for this exact FDA record. Unknown is not all ages or evidence of unsuitability.

Public-label constraints, not patient-level eligibility or a medical recommendation. Training and evaluation populations are separate. Read the original labeling and confirm the exact release and protocol.

Purpose
Notification-only triage of adult head CTA for suspected complete large-vessel and medium-vessel occlusions; compressed previews are informational and the full study remains required for diagnosis.
  • Exact FDA submission
  • Checked 2026-09-08
Workflow role
Triage and notification: AI analyzes head CTA images and flags suspected complete large vessel occlusions and medium vessel occlusions, highlighting cases on a standalone desktop application in parallel to the ongoing standard of care image interpretation.
  • Exact FDA submission
  • Checked 2026-11-14

Packet wording: "head CTA images in adults or transitional adolescents aged 18 and older. The device is intended to assist hospital networks and appropriately trained medical specialists in workflow triage by flagging and communication of suspected positive findings" … "of complete Large Vessel Occlusion (LVO) - MCA-M1, PCA-P1, ACA-A1, ICA, Basilar; and Medium Vessel Occlusions (MeVO)". Read from the exact FDA decision document on 2026-11-14.

Required input
CT/CTA images or data involving Brain/Cerebrovascular; consult the FDA labeling for exact protocol, series, and quality requirements.
  • Exact FDA submission
  • Checked 2026-09-19

Exact FDA decision-summary packet reviewed on 2026-09-19; existing wording is supported without expansion.

Output and clinician action
The AI model flags and sends notifications for suspected positive findings of Large Vessel Occlusion (LVO) and Medium Vessel Occlusions (MeVO) in head CTA images. Notifications include compressed, low-quality, grayscale, unannotated preview images for informational/triage purposes only (not for diagnostic use). The device prioritizes suspect cases on the worklist to facilitate earlier triage.
  • Exact FDA submission
  • Checked 2026-09-19

Exact FDA decision-summary packet reviewed on 2026-09-19; existing wording is supported without expansion.

Care setting
Adult
  • Exact FDA submission
  • Checked 2026-09-01

Patient-population text reported in the exact-submission ACR model card; institutional setting may still require vendor confirmation.

Intended users
Hospital networks and appropriately trained medical specialists
  • Exact FDA submission
  • Checked 2026-09-19

Exact FDA decision-summary packet reviewed on 2026-09-19; existing wording is supported without expansion.

Limitations
Head CTA protocol with a 64-slice scanner or higher; scans performed on adults/transitional adults ≥ 18 years of age; slice thickness 0.5 mm – 1.25 mm. All scans that are technically inadequate, including motion artifacts, severe metal artifacts, suboptimal bolus timing or an inadequate field of view.
  • Exact FDA submission
  • Checked 2026-09-19

The exact packet's comparison table states the inclusion and exclusion boundary and slice thickness for the subject device.

Evidence summary
Aidoc conducted a retrospective, blinded, multicenter study with the BriefCase software to evaluate the software's performance in identifying head CTA images containing Vessel Occlusion (VO) in 342 cases from 5 US-based clinical sites. Ground truth was determined by 3 expert US board certified Neurologists reviewers using majority voting. Sensitivity was 91.3% (95% CI: 83.6%, 96.2%) and specificity was 85.6% (95% CI: 80.6%, 89.7%).
  • Exact FDA submission
  • Checked 2026-09-19

The exact packet reports the retrospective multicenter study, ground-truth review, and primary endpoint metrics.

Evidence

Performance evidence

Metrics are shown only when they are tied to a source, endpoint, population, and tested product version. Candidate literature without exact product and version linkage is not shown as product evidence.

Evidence summary
Aidoc conducted a retrospective, blinded, multicenter study with the BriefCase software to evaluate the software's performance in identifying head CTA images containing Vessel Occlusion (VO) in 342 cases from 5 US-based clinical sites. Ground truth was determined by 3 expert US board certified Neurologists reviewers using majority voting. Sensitivity was 91.3% (95% CI: 83.6%, 96.2%) and specificity was 85.6% (95% CI: 80.6%, 89.7%).
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-19

The exact packet reports the retrospective multicenter study, ground-truth review, and primary endpoint metrics.

Reported sensitivity
91.3% (95% CI: 83.6%, 96.2%)
  • Public source
  • Exact FDA submission
  • Checked 2026-09-01

Model sensitivity reported by ACR AI Central. Review endpoint, threshold, study population, and tested version before comparison.

Reported specificity
85.6% (95% CI: 80.6%, 89.7%)
  • Public source
  • Exact FDA submission
  • Checked 2026-09-01

Model specificity reported by ACR AI Central. Review endpoint, threshold, study population, and tested version before comparison.

No contextualized exact-version metric has completed evidence review. Regulatory-document values, when available, are shown above with their limitations.

BriefCase-Vessel Occlusion LVO & MeVO Triage regulatory performance study summary

  • DesignStand-Alone Performance
  • PopulationAdult
  • Scopeexact submission
  • Tested versionExact product version not reported; regulatory study summarized for FDA submission K220709
  • Samplen=342
  • Sites5
  • IndependenceIndependence not established

K220709

ACR AI Central summarizes the regulatory study; consult the exact FDA materials before comparative use.

Safety and lifecycle

Postmarket record

Recall and adverse-event records are shown only after product matching. Adverse-event reports do not establish incidence or causality.

Postmarket safety review
The exact-identifier FDA recall query returned no native recall record for K220709. This limited result does not establish absence of recalls or other safety information and does not cover later versions, family records, MAUDE reports, corrections, or field notices.
  • Public source
  • Exact FDA submission
  • Checked 2026-09-08
Pricing & contracts Public price, contract terms, and reimbursement

Price not public here; enter your quote

Not verified: Pricing information is recorded but not verified against a resolving source.

Reimbursement

IT implementation Deployment, interfaces, data handling, and support

System and version relationships

Match the AI release, system build, configuration and region. Source documentation does not establish acceptance of an installed system.

No specific system/version pairing has completed review for this FDA record. A broad DICOM or product-family statement does not establish a named viewer build's support.

Review Merge, Visage, Sectra, AGFA and IntelePACS context

Integration chain: evidence at each hop

Public source context, not tested interoperability. Each hop needs its own release/configuration evidence. Missing or unavailable routes are not documented incompatibility. All local tests are planned, not passed; no installed-system acceptance is recorded.

Acquisition/source → routing → AI processing → returned objects → viewer/worklist/report → support owner

No specific route context has been source-reviewed for this record. Obtain both endpoint builds and documents; this is not a finding of incompatibility.

  1. Acquisition/source

    Source context, not route validation: CT/CTA images or data involving Brain/Cerebrovascular; consult the FDA labeling for exact protocol, series, and quality requirements.

    Scope: Exact FDA submission. Exact FDA decision-summary packet reviewed on 2026-09-19; existing wording is supported without expansion.

    Confirm scanner/model, protocol, series completeness and both software builds.

    Field checked 2026-09-19 · FDA K220709: BriefCase

  2. Routing

    Source context, not route validation: The exact FDA package describes DICOM images being received before processing, notifications of suspect cases sent to the desktop application, and use with DICOM 3.0 compliant CT scanners, PACS, and radiology workstations. Interface versions and local compatibility require confirmation.

    Scope: Exact FDA submission. Packet wording: "DICOM images are received, saved, filtered and de-identified before processing." … "The software then flags suspect cases by sending notifications to the desktop application, thereby facilitating triage and prioritization by the user.". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.

    Name gateways, destinations, transfer rules and failure visibility; a DICOM statement does not prove a route.

    Field checked 2026-11-14 · FDA K220709: BriefCase

  3. AI processing

    Source context, not route validation: The exact FDA package describes BriefCase as three modules: an Aidoc Hospital Server for image acquisition, an Aidoc Cloud Server for image processing, and an Aidoc Desktop Application for workflow integration, with de-identified DICOM exams uploaded to the cloud for analysis. Current hosting, data flow, and commercial configuration require vendor confirmation.

    Scope: Exact FDA submission. Packet wording: "The device consists of the following three modules: (1) Aidoc Hospital Server (AHS/Orchestrator) for image acquisition; (2) Aidoc Cloud Server (ACS) for image processing; and (3) Aidoc Desktop Application for workflow integration." … "The BriefCase time-to-notification includes the time to get the DICOM exam, de-identify it, upload it to the cloud, analyze and send a notification on a positive suspect case back to the desktop application.". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.

    Confirm processing location, queue ownership, exclusions and exact AI build.

    Field checked 2026-11-14 · FDA K220709: BriefCase

  4. Returned objects

    Source context, not route validation: The AI model flags and sends notifications for suspected positive findings of Large Vessel Occlusion (LVO) and Medium Vessel Occlusions (MeVO) in head CTA images. Notifications include compressed, low-quality, grayscale, unannotated preview images for informational/triage purposes only (not for diagnostic use). The device prioritizes suspect cases on the worklist to facilitate earlier triage.

    Scope: Exact FDA submission. Exact FDA decision-summary packet reviewed on 2026-09-19; existing wording is supported without expansion.

    Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.

    Field checked 2026-09-19 · FDA K220709: BriefCase

  5. Viewer/worklist/report

    Unresolved route: The AI model flags and sends notifications for suspected positive findings of Large Vessel Occlusion (LVO) and Medium Vessel Occlusions (MeVO) in head CTA images. Notifications include compressed, low-quality, grayscale, unannotated preview images for informational/triage purposes only (not for diagnostic use). The device prioritizes suspect cases on the worklist to facilitate earlier triage.

    Scope: Exact FDA submission. Exact FDA decision-summary packet reviewed on 2026-09-19; existing wording is supported without expansion.

    Confirm the named viewer/worklist/report build, display behavior and report transfer. Output support alone does not establish this endpoint. The displayed source describes output, not validated end-to-end delivery.

    Field checked 2026-09-19 · FDA K220709: BriefCase

  6. Support owner

    Unresolved route: Not established for the exact route.

    Scope: Scope not established.

    Name the local, platform and AI supplier support owners and escalation path.

Planned local route tests

No tests below have been performed or accepted.

  1. Patient/study identity (planned). Use approved non-patient test data to verify identifiers, accession and result-to-study linkage at every hop.
  2. Study completeness (planned). Test missing views/series, partial transfer, late arrivals, priors and unsupported acquisition inputs; confirm explicit refusal or fallback.
  3. Ordering and duplicates (planned). Send out-of-order, repeated and corrected studies; verify worklist order, deduplication and no misleading stale results.
  4. Report transfer (planned). Verify output object types, annotations, units, report content, destination and availability of original images.
  5. Access (planned). Verify authorized roles, audit trail, denied access and support ownership at each destination.
  6. Latency and failures (planned). Agree a workload and turnaround target; test queues, timeouts, missing results and fallback reading.
  7. Updates and rollback (planned). Define version change control, revalidation triggers, stop-use criteria and a tested rollback route.

Local implementation checklist

Agree the evidence and acceptance owner with your team and suppliers. Checkmarks apply to this page only and are not acceptance receipts.

Open the printable evaluation checklist

Deployment
The exact FDA package describes BriefCase as three modules: an Aidoc Hospital Server for image acquisition, an Aidoc Cloud Server for image processing, and an Aidoc Desktop Application for workflow integration, with de-identified DICOM exams uploaded to the cloud for analysis. Current hosting, data flow, and commercial configuration require vendor confirmation.
  • Exact FDA submission
  • Checked 2026-11-14

Packet wording: "The device consists of the following three modules: (1) Aidoc Hospital Server (AHS/Orchestrator) for image acquisition; (2) Aidoc Cloud Server (ACS) for image processing; and (3) Aidoc Desktop Application for workflow integration." … "The BriefCase time-to-notification includes the time to get the DICOM exam, de-identify it, upload it to the cloud, analyze and send a notification on a positive suspect case back to the desktop application.". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.

Integration
The exact FDA package describes DICOM images being received before processing, notifications of suspect cases sent to the desktop application, and use with DICOM 3.0 compliant CT scanners, PACS, and radiology workstations. Interface versions and local compatibility require confirmation.
  • Exact FDA submission
  • Checked 2026-11-14

Packet wording: "DICOM images are received, saved, filtered and de-identified before processing." … "The software then flags suspect cases by sending notifications to the desktop application, thereby facilitating triage and prioritization by the user.". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.

Security
Aidoc's current public Security & Privacy page says its security work is led by a CISO and security team, that it has adopted the NIST Cybersecurity Framework, and that its platform runs on AWS and Azure using EDR, encryption, SIEM and CSPM tooling. The page's list of standards and certifications did not load as readable text, so no certification is stated here.
  • Vendor-wide
  • Checked 2026-10-25

Vendor-wide marketing statement, not an independent attestation. It does not establish certificate scope or expiry, the controls of this exact release, data location, retention, identity and access, or incident-response terms for a deployed configuration. Obtain these from the vendor.

Monitoring
Aidoc's security page states that its platform runs on AWS and Azure and that customer data protection is achieved with the use of EDR, encryption, SIEM, CSPM and other technologies.
  • Vendor-wide
  • Checked 2026-10-27

Vendor statement, not an attestation. The page names Aidoc's platform generally and does not scope these capabilities to any specific product release; exact-release scope is not established. The page lists technology categories in use; it states no uptime, alerting or response-time SLAs.

Supported acquisition environment

Scanner manufacturers: All

exact submission · checked 2026-09-01

Confirm currently supported software versions, protocols, and site-specific acquisition configurations.

ACR exact-submission catalog context

ACR AI Central provides an exact-submission model card for BriefCase; FDA labeling remains controlling for clinical use, limitations, and performance.

exact submission · checked 2026-09-08
Sources & review details FDA identity, research record, source ledger, and history

Regulatory identity

FDA record and catalog context

The FDA listing establishes the regulatory identity. It does not by itself establish local workflow fit, pricing, security, or performance in your environment.

FDA submission
K220709
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31
Modality
CT/CTA
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-19

Exact FDA decision-summary packet reviewed on 2026-09-19; existing wording is supported without expansion.

Anatomy
Brain/Cerebrovascular
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-19

Exact FDA decision-summary packet reviewed on 2026-09-19; existing wording is supported without expansion.

Clearance type
510(k)
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31
Decision date
2022-10-07
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31
FDA status
FDA-cleared
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31

Research record

What has been checked

This audit distinguishes completed source review from fields that have not yet been researched.

Exact FDA record reviewedStatus
2026-09-20Last searched
27Fields reviewed
11Source classes checked
20Screened PubMed leads
6Screened trial leads
0Unreviewed FDA recall leads

The refreshed discovery snapshot contains 20 PubMed and 6 ClinicalTrials.gov candidate records. Discovery metadata alone does not establish exact tested-product, version, population, and endpoint applicability, so all candidates remain quarantined and none was promoted. The current discovery snapshot contains 20 PubMed and 6 ClinicalTrials.gov candidate records; its dated, count-matched human screening remains current. Unlinked candidates remain quarantined. Native FDA recall identifiers produced 0 postmarket candidate records; 0 have been reviewed (0 published, 0 rejected) and 0 remain unreviewed.

Candidate leads were screened against the exact product and tested version. Unlinked records remain quarantined.

Source classes: fda ai list, fda decision summary, acr ai central product, vendor product page, fda device recall, literature index, trial registry, fda decision summary packet, pubmed, clinical trials, openfda device recall

Field review details

Recorded state, verification date, notes and sources for fields without a publishable value. Conflicting records stay explicitly unsettled here; no plain settled value is shown for them.

  • Public pricing: Not verified - checked 2026-09-08 - Exact FDA submission

    No public price or quote for the exact K220709 configuration was established in this review.

  • Pricing model: Not yet reviewed
  • Setup and integration fees: Not yet reviewed
  • Recurring fees: Not yet reviewed
  • Minimum commitment: Not yet reviewed
  • Contract duration: Not yet reviewed
  • Renewal terms: Not yet reviewed
  • Cancellation terms: Not yet reviewed
  • Support and service terms: Not yet reviewed
  • Trial or pilot terms: Not yet reviewed
  • Reimbursement: Not publicly available - checked 2026-09-08 - Exact FDA submission

    No exact-product payer policy, coding instruction, or payment determination was established; eligibility must be evaluated by payer, site of service, and use case.

  • Data hosting location: Not yet reviewed
  • Data retention: Not yet reviewed
  • Documented data use: Not yet reviewed
  • Hardware requirements: Not yet reviewed
  • Network requirements: Not yet reviewed
  • Identity and access: Not yet reviewed
  • Installation timeline: Not yet reviewed
  • Training: Not verified - checked 2026-09-08 - Exact FDA submission

    Current training prerequisites, competency checks, and support commitments for the exact configuration require vendor confirmation.

8 sources - 3 history items

Source ledger

  1. FDA K220709: BriefCase

    U.S. Food and Drug Administration - Published 2022-10-07 - Accessed 2026-09-19

    Scope: identity, clinicalUse, modality, anatomy, workflow, evidence, implementation, purpose, intendedUsers, input, output, limitations, evidenceSummary, deployment, integration

  2. Artificial Intelligence-Enabled Medical Devices

    U.S. Food and Drug Administration - Accessed 2026-08-31

    Scope: regulatoryIdentity, modalityContext

  3. BriefCase-Vessel Occlusion LVO & MeVO Triage model card (K220709)

    American College of Radiology - Published 2026-06-26 - Accessed 2026-09-01

    Scope: intendedUsers, careSetting, output, limitations, reportedSensitivity, reportedSpecificity, evidenceSummary, anatomy, evidenceStudies, implementationCapabilities

  4. PubMed biomedical literature index

    U.S. National Library of Medicine - Accessed 2026-09-01

    Scope: evidenceDiscovery

  5. ClinicalTrials.gov study registry

    U.S. National Library of Medicine - Accessed 2026-09-01

    Scope: evidenceDiscovery, studyStatus

  6. openFDA Device Recall API

    U.S. Food and Drug Administration - Accessed 2026-09-02

    Scope: recallDiscovery, nativeSubmissionMatching

  7. openFDA exact recall query for K220709

    U.S. Food and Drug Administration - Accessed 2026-09-08

    Scope: postmarketSafety

  8. Aidoc Security & Privacy

    Aidoc Medical - Accessed 2026-10-25

    Scope: security

Research history

  1. K220709 FDA decision

    Regulatory record

    510(k)

  2. Source-review record updated

    Research record

    fda record reviewed

  3. Reader overview source-reviewed

    Editorial review

    Source-reviewed editorial overlay

Alternatives

Related tools to compare

FDA-cleared K221314

BriefCase

Aidoc Medical, Ltd.

Authorized purpose: BriefCase is a radiological computer aided triage and notification software indicated for use in the analysis of head CTA images in adults or transitional adolescents aged 18 and older. The device is intended to assist hospital networks and appropriately trained medical specialists in workflow triage by flagging and communication of M1 Large Vessel Occlusion (M1-LVO) pathologies. Briefcase uses an artificial intelligence algorithm to analyze images and highlight cases with detected findings on a Stand-Alone Performance desktop application in parallel to the ongoing standard of care image interpretation. The user is presented with notifications for cases with suspected findings. Notifications include compressed preview images that are meant for informational purposes only and not intended for diagnostic use beyond notification. The device does not alter the original medical image and is not intended to be used as a diagnostic device. The results of BriefCase are intended to be used in conjunction with other patient information and based on their professional judgment, to assist with triage/prioritization of medical images. Notified clinicians are responsible for viewing full images per the standard of care.

Modality
CT/CTA
Anatomy
Brain/Cerebrovascular
Decision
2022-06-03
FDA-cleared K192383

BriefCase

Aidoc Medical, Ltd.

Authorized purpose: BriefCase is a radiological computer aided triage and notification software indicated for use in the analysis of head CTA images. The device is intended to assist hospital networks and trained radiologists in workflow triage by flagging and communication of suspected positive findings of Large Vessel Occlusion (LVO) pathologies.

Modality
CT/CTA
Anatomy
Brain/Cerebrovascular
Decision
2019-12-20
FDA-cleared K260729

Vascular Assist Occlusion Triage (VAOT) (v1.0)

GuideAI Health

Authorized purpose: Passive workflow prioritization for studies with imaging patterns consistent with possible total arterial occlusion in the specified vessels; not primary diagnosis, screening, disease detection, or patient-management decision support

Modality
CT/CTA
Anatomy
Aorta and lower-extremity arteries: common iliac, external iliac, common femoral, superficial femoral, and popliteal arteries
Decision
2026-06-18
FDA-cleared K261317

BriefCase-Triage

Aidoc Medical, Ltd.

Authorized purpose: Adult head CTA or mCTA triage for suspected complete large-vessel and medium-vessel occlusion.

Modality
CT/CTA
Anatomy
Head/Brain
Decision
2026-05-14

Correct this exact record

Copy this public context and add the field, proposed wording and original source before sending. Nothing here is submitted automatically. Form-specific prefill has not been verified.

Open existing correction destination

Permission to display a submission is not evidence verification. A submission enters editorial review; it does not approve a public change. Form availability, data entry, receipt, review and publication are separate steps. Data entry and receipt remain unverified.

Accepted repository change history

No entry has been added to this scoped change history for this record. This is not proof that the record never changed.

Correction policy and limits · Public repository change history