Page de réservation fièvre et première visite avec Claude Code: documents, assurance et créneaux

Cet article aide les cliniques à vérifier une page de réservation fièvre et première visite avant publication.

Clinics do not need a longer booking page when patients are already tired, feverish, or anxious. They need four clear lines before the booking button: which slot to choose, what to bring, what to do before arrival, and which information should not be typed into the first form.

Primary sources used for the Japanese article include Japan’s Ministry of Health, Labour and Welfare page on My Number health insurance card use, its page on medical advertising regulation, its COVID-era note that designated outpatient institutions stopped being publicly designated from April 2024 in the general care transition page, and Japan’s Personal Information Protection Commission guidance for medical and care providers. This article does not make clinical or legal decisions. It shows a Claude Code workflow for page inventory and human review.

Points clés

• Put fever booking slots, belongings, arrival notes, insurance guidance, and privacy boundaries before the form.
• Ask Claude Code to inventory the page, booking slot names, FAQ, form fields, old wording, and after-submit email.
• Humans keep clinical triage, infection control, medical advertising, insurance guidance, personal data, booking operations, and publish approval.
• Track phone repeat questions, wrong booking slot choices, missing belongings, form start rate, form submit rate, and reception time.
• The 30-minute action is to add four lines above the booking button: slot, belongings, arrival notes, and insurance confirmation.

Où les pages de réservation échouent

Clinic booking pages often use internal wording. Patients see “general outpatient”, “fever slot”, “same-day slot”, or “first visit”, but they do not know which one matches their situation. A patient with fever may wonder whether online booking is allowed, whether to enter the reception area, whether to wait in a car, and what insurance document to bring.

The problem is not only copywriting. Old fever-clinic language, old insurance-card language, and broad medical claims can remain on a page long after operations change. Claude Code should help find these mismatches. It should not decide clinical triage.

Workflow: quatre lignes avant le bouton

Before the booking button, make the patient path visible.

Place	What to show	Human review
Booking button area	fever slot, normal slot, when to call	clinic operation
Belongings	My Number insurance card, qualification certificate, medication notebook, referral letter	reception workflow
Arrival notes	mask, waiting place, companion, late arrival contact	infection-control flow
Form	contact, symptom start date, fever, preferred slot	privacy and over-collection
After submit	reply timing, arrival flow, urgent contact	next patient action

Now the prompt becomes specific. Instead of “improve the clinic page”, ask: “check whether the booking page shows slot choice, belongings, arrival notes, insurance confirmation, and privacy boundaries before the form.”

Périmètre de Claude Code et périmètre humain

Claude Code can inspect headings, booking slot names, belongings, FAQs, form fields, old health-insurance wording, old fever-clinic wording, CTA count, and confirmation email drafts. Use masked examples, field names, and receptionist question counts.

Humans decide clinical triage, urgent guidance, infection control, medical advertising wording, insurance instructions, personal data handling, booking slot operation, and publication. Claude Code can say “needs review”; it should not say who may be treated or whether symptoms are urgent.

Personal data also needs boundaries. The first form often needs name, contact, age band, symptom start date, fever status, and preferred date. It usually does not need insurance card images, full medical history, diagnostic assumptions, or test result images before a storage policy is decided.

3 cas d’utilisation

Use case 1: Rewrite fever slot names for patients

• Input: current booking page, booking-system slot names, common receptionist questions, fever-flow memo.
• Output: a short table for online booking, when to call, and arrival waiting place.
• Human review: clinical capacity, infection-control flow, call conditions, urgent guidance, slot operation.

Use case 2: Update belongings and insurance guidance

• Input: belongings page, FAQ, reception notice, confirmation email, official insurance guidance.
• Output: a table for My Number insurance card, qualification certificate, medication notebook, referral letter, and medical certificates.
• Human review: latest reception process, identity confirmation, insurance handling, exception wording.

Use case 3: Move excessive form fields to later steps

• Input: form fields, required settings, confirmation email, receptionist memo, privacy wording.
• Output: first form, after booking, do not collect, and needs review columns.
• Human review: privacy, storage location, purpose of use, clinical necessity, third-party form provider handling.

Prompt à copier

Act as the pre-publish reviewer for a clinic fever and first-visit booking page.
Do not make clinical decisions. Organize the information patients need before booking.

Inputs:
- current booking page copy
- booking system slot names
- belongings page
- FAQ
- common receptionist questions
- form fields
- confirmation email

Check:
1. whether fever slots, normal slots, and call-needed cases appear above the booking button
2. whether belongings mention My Number insurance card, qualification certificate, medication notebook, referral letter, and medical certificates
3. whether arrival notes mention waiting place, mask, companion, and late-arrival contact
4. personal data asked too early in the first form
5. old insurance wording, old fever-clinic wording, and medical claims needing review
6. human gates: clinical triage, infection control, medical advertising, insurance, privacy, publish approval
7. one change to make in the next 30 minutes

Constraints:
- Do not diagnose or promise outcomes
- Do not decide urgent triage alone
- Do not paste real patient names, phone numbers, chart numbers, insurance images, or test images
- Mark unclear items as "needs review"

Code de vérification

const bookingPage = {
  aboveForm: ["fever booking slot", "normal booking slot", "what to bring", "arrival notes"],
  belongings: ["mynahokensho", "qualification certificate", "medication notebook", "referral letter"],
  formFields: ["name", "phone", "symptom_start_date", "has_fever", "preferred_time"],
  pageCopy: ["Bring My Number insurance card or qualification certificate.", "Guaranteed recovery"],
  humanReview: ["clinical triage", "infection control", "medical advertising", "insurance guidance", "privacy"]
};

const requiredAboveForm = ["fever booking slot", "what to bring", "arrival notes"];
const requiredBelongings = ["mynahokensho", "qualification certificate", "medication notebook"];
const riskyMedicalClaims = ["Guaranteed recovery", "always cured", "no side effects", "safe for everyone"];
const sensitiveFields = ["insurance_card_image", "my_number", "medical_record_photo", "full_medical_history"];

const findings = [];

for (const item of requiredAboveForm) {
  if (!bookingPage.aboveForm.includes(item)) findings.push({ area: "above form", fix: `add ${item} before booking` });
}
for (const item of requiredBelongings) {
  if (!bookingPage.belongings.includes(item)) findings.push({ area: "belongings", fix: `check ${item}` });
}
for (const copy of bookingPage.pageCopy) {
  for (const claim of riskyMedicalClaims) {
    if (copy.includes(claim)) findings.push({ area: "medical claim", fix: `human review for ${claim}` });
  }
}
for (const field of bookingPage.formFields) {
  if (sensitiveFields.includes(field)) findings.push({ area: "form", fix: `remove ${field} from first form` });
}

console.table(findings);
if (findings.length > 0) process.exitCode = 1;

Pitfall: pièges courants

Cause: old fever-clinic language remains while the current booking operation changed. Fix: write the current clinic rule for online booking, phone contact, and arrival waiting place.

Cause: insurance wording is outdated. Fix: review current official guidance and the reception process before changing the page.

Cause: the first form asks for too much medical detail. Fix: keep the first form light and move detailed documents to a later reviewed step.

Cause: AI writes outcome claims. Fix: replace them with “we will confirm”, “the clinician will decide”, or “we will guide you if needed”.

Cause: booking slots use internal clinic names. Fix: use patient-facing labels such as fever/cold symptoms, standard visit, and call for same-day questions.

Questions fréquentes

Q. Can fever patients use online booking?

A. The clinic must decide based on its current operation. Claude Code can clarify the page; people confirm the rule.

Q. Should insurance guidance be on the page?

A. If reception receives repeat questions, put the guidance on the booking page or confirmation email.

Q. Should the form ask detailed symptoms?

A. Keep it to what is needed before booking. Store more sensitive details only after purpose and retention are clear.

Q. Which metrics matter?

A. Repeat phone questions, wrong slot choices, missing belongings, form start rate, form submit rate, and reception time.

Chemin vers la consultation

For clinic teams, this work touches the website, booking system, reception, insurance confirmation, medical advertising, privacy, and patient flow. ClaudeCodeLab training can help separate what Claude Code inventories from what clinicians and staff must approve.

Ce que j’ai vérifié

I checked the official source links used in the Japanese article, internal links, external links, CTA, frontmatter, and the JavaScript review code. The next concrete action is to put booking slot, belongings, arrival notes, and insurance confirmation above the booking button.