医療機関AI検索ラボMEDICAL AI SEARCH LAB

Update Policy

The update policy of Medical AI Search Lab. It defines article update frequency, last-review criteria, the error-correction flow, and archiving decisions.

This policy defines the update frequency of articles, the last-review criteria, error correction, and the rules for archiving decisions.

Effective: 2026-05-19

1. Update Frequency

Because the field of AI search and LLMO changes rapidly, this medium adopts the following update cycle as a baseline.

  • Pillar articles: editorial review once per quarter
  • Support articles: editorial review once every six months
  • Verification logs: fixed as records of the point of observation, with subsequent observations added as separate records
  • Policies: reviewed once a year or when a significant event occurs

2. Meaning of Published Date / Updated Date / Last Reviewed Date

  • Published date (publishedAt): the date of first publication (immutable)
  • Updated date (updatedAt): the date on which a meaningful change was made to the body text or sources
  • Last reviewed date (lastReviewedAt): the date on which an editorial review was completed, even without any change to the content

3. Distinguishing Minor Corrections from Meaningful Changes

  • Minor (does not move updatedAt): typos, fixing broken links, decorative changes
  • Meaningful (updates updatedAt): adding or correcting facts, adding sources, changing conclusions

4. Error-Correction Flow

  1. Receive the report of an error
  2. Cross-check against primary sources
  3. Correct the relevant passage
  4. Where necessary, leave a correction history at the end of the article
  5. Update updatedAt unless the change is minor

5. Archiving Decisions

Articles that fall under the following are switched to noindex or to an archived display.

  • When the specifications or guidelines that underlie the article change significantly, and the current version raises a concern of misleading readers
  • When there has been no update for more than a year and doubts arise about the reliability of the content

6. Handling of Verification Logs

Verification logs are treated as "records of the point of observation." Later re-tests and re-observations are published as separate verification logs and linked to one another. Conclusions are not rewritten retroactively.