A hospital with five hundred consultants does not have a content problem on its doctor pages. It has a data problem. A profile that shows a surgeon who left in March, a qualification typed three different ways, or "available today" for a clinic that was cancelled is worse than no profile, because the patient acts on it.
This post is for hospital web teams, digital heads and CMOs who own or are about to build a doctor directory. It sets out a field model, the schema.org markup that should sit on top of it, and an update workflow that keeps registration number, qualifications and availability accurate without relying on someone remembering to edit pages. It is a checklist-style build guide, not a design brief.
One boundary first. Every clinical and credential statement on a profile must come from the doctor and be confirmed by your credentialing or medical-affairs team. Marketing owns the template and the workflow; it does not own the facts. Your NMC-related wording rules are covered in the NMC compliance handbook.
Treat the profile as a record, not a page
The first design decision is where the truth lives. If each profile is a free-text page in a CMS, you have 500 places for errors. If each profile is rendered from a structured record, you have one place per field and one validation step.
A workable record has four groups of fields.
| Group | Fields | Owner | Public? |
|---|---|---|---|
| Identity | full name as registered, display name, photo, gender (optional), languages | Doctor, HR | Yes |
| Credentials | registration number, registering council, qualifications with institution and year, designation | Credentialing office | Yes, after verification |
| Practice | specialty, sub-specialty interests, conditions and procedures treated, department, hospital and location | Department head | Yes |
| Availability | OPD days and times by location, appointment link, accepting new patients, last-confirmed timestamp | Scheduling team or HIS feed | Yes, with timestamp |
Keep two further groups that are not public but drive the workflow: a verification block (who checked, when, against what) and an editorial block (status, last clinical review date, next review due).
Use structured values wherever possible. Qualifications should be a list of objects (degree code, institution, year), not a string like "MBBS MD (Med) DM Card AIIMS". Registration should be two fields, number and council, never one. Specialty should come from a controlled list so that "Cardiology", "Cardiologist" and "Heart Specialist" cannot coexist as three different filters.
Registration number: display it, verify it, date it
Showing the registration number helps patients and referrers check a doctor, and it is the field most likely to be wrong, because it is copied by hand from certificates.
A sensible rule set:
- Store the number and the council exactly as they appear on the registration certificate. Do not normalise or reformat on the way in.
- Verify each new number against a public register before the profile goes live. The National Medical Register is the NMC-maintained register of registered doctors, and state medical council registers remain the other check. Check what each register currently shows and record the check.
- Where the doctor has an ABDM Healthcare Professionals Registry ID, the Healthcare Professionals Registry is another place to cross-check. Treat it as optional metadata, not a replacement for the council number.
- Record the verification as data: verified by, verified on, source checked. A profile with no verification date should not publish.
- Re-verify on a schedule and on events, such as a change of name or a new qualification, not only at onboarding.
Do not publish a number you could not verify "temporarily". The temporary state is the one that becomes permanent.
Schema: Physician, with the right restraint
For individual doctors, the natural type is Physician. It sits under MedicalOrganization and LocalBusiness, which is why it can carry address, telephone and opening hours as well as medical properties. The Physician type itself adds availableService, hospitalAffiliation and medicalSpecialty, and isAcceptingNewPatients comes from MedicalOrganization. The usNPI property is US-specific; leave it out.
A practical mapping from the record to markup:
| Record field | schema.org property | Note |
|---|---|---|
| Display name | name | Match the visible heading |
| Photo | image | Same image as on the page |
| Specialty | medicalSpecialty | Use the schema.org enumeration where a value exists |
| Hospital | hospitalAffiliation | Point to the Hospital entity defined once on the site |
| Procedures treated | availableService | Only those the doctor performs |
| OPD hours | openingHoursSpecification | Per location; omit if not maintained |
| Accepting patients | isAcceptingNewPatients | Only if the source is current |
| External profiles | sameAs | Council register page, if it has a stable public URL |
| Registration | identifier as a PropertyValue | name: council, value: number |
Three rules keep this honest. First, Google's structured data policies say not to mark up content that is not visible to readers, and to provide up-to-date information, so every property above should correspond to something a visitor can see. Second, define the Hospital and the departments once, with stable @id values, and reference them from every doctor; do not re-describe the hospital 500 times. Third, there is no rich result promised for a Physician type in itself, so the value is clarity for search and AI systems, not a badge. The wider approach to medical markup is in our advanced medical schema guide and the schema markup service page.
Do not add review or aggregateRating markup copied from third-party platforms. If you display your own patient feedback, handle it under its own rules and keep it separate from the credential block.




