Add Patient flow docs for 3.1 - #40
Conversation
Replace the single create-patient flow with nine Patient flows covering search, registration, profile, updates, identifiers, tags, deceased status, users, and appointments. Update the 3.1 Patient concept and reference, the sidebar, and every link that pointed at create-patient (intro, homepage quick links, HMIS and palliative playbooks, and the Malayalam translations). Also fix devLocaleWarning to read i18n from @generated/i18n.
Deploying coredocs with
|
| Latest commit: |
4d8f40e
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://6274a878.coredocs.pages.dev |
| Branch Preview URL: | https://docs-patient-flows.coredocs.pages.dev |
# Conflicts: # versioned_docs/version-3.1/concepts/clinical/patient.mdx
Nest flow docs by concept so each clinical concept owns a folder. Adds a Patient category to the 3.1 sidebar and repoints every link to the new /flows/clinical/patient/... routes.
There was a problem hiding this comment.
Review summary
Reviewed the changed .mdx/sidebar files against the concept/flow/reference skills and shared conventions.
The nine new Patient flow docs (search-patient, register-patient, view-patient-profile, update-patient-details, manage-patient-identifiers, manage-patient-tags, mark-patient-deceased, manage-patient-users, view-patient-appointments) are strong: strictly user-facing, no code/API/payload leakage, correct ### N. <imperative> step structure, :::info Prerequisite blocks, field tables with plain-language display labels, and no stray { } or heading-id issues. The old create-patient.mdx (with its ## API equivalent section — a hard layer violation per the flow skill) was correctly removed rather than kept. The new sidebar items array is correctly populated with all nine flows in the Patient category, so the flows are not orphaned in version-3.1.
Four real issues found, flagged inline:
- Broken links —
versioned_docs/version-3.1/intro.mdx(and the mirroredi18n/mlcopy) link to./flows/clinical/patient/register-patientwithout the.mdxextension. Per the conventions, extensionless links are reserved only for the translated docs (patient,create-patient);register-patientisn't translated, so this needs.mdxor it risks a broken/ambiguous resolution. - FHIR narration — the new
## FHIR referencesection in the concept doc narrates specific endpoints (GET /Patient,POST /Patient) instead of just linking the resource, which the concept-doc skill explicitly disallows. - Dead commented-out content — a large block (blood group, patient tags, volunteer contact, profile sections) is wrapped in
{/* ... */}and left in the shipped concept doc instead of being finished or deleted. - Version drift — this PR only touches
version-3.1. The shared conventions requireversion-3.0andversion-3.1to stay byte-identical; the new flows, concept/reference rewrites, and sidebar restructuring were not mirrored intoversion-3.0, so the two versions now diverge (3.0 still has only the oldcreate-patientflow).
No corruption (antml:/<invoke> leakage), no {#...} heading-id issues, and the HMIS/palliative playbook and homepage link updates are all consistent and correctly repointed. Could not independently verify the new permission names, blood-group enum values, or field labels (e.g. "Can Update a Patient's data") against ohcnetwork/care/care_fe source in this pass — worth a spot-check before merge if not already sourced from the locale file and permission definitions.> Generated by Docs Reviewer for #40 · auto · 117.9 AIC · ⌖ 2.46 AIC · ⊞ 10.5K
| **Flows answer: _How do I…?_** | ||
|
|
||
| Step-by-step guides for tasks in Care — for example, [how to create a patient](./flows/clinical/create-patient). Flows describe the happy path in the product UI and API; they stay deployment-agnostic unless noted. | ||
| Step-by-step guides for tasks in Care — for example, [how to register a patient](./flows/clinical/patient/register-patient). Flows describe the happy path in the product UI and API; they stay deployment-agnostic unless noted. |
There was a problem hiding this comment.
Broken-link risk: ./flows/clinical/patient/register-patient is missing the .mdx extension. Per the shared conventions, extensionless links are reserved only for the translated docs (patient, create-patient); every other internal link keeps .mdx. register-patient is not translated, so this should be ./flows/clinical/patient/register-patient.mdx. Same issue on line 23 and line 46, and in the mirrored i18n/ml/.../intro.mdx.
|
|
||
| You enter either a date of birth or an age, not both. | ||
|
|
||
| {/* |
There was a problem hiding this comment.
This entire block (lines 34–72) is wrapped in an MDX comment ({/* ... */}) and left in the file as dead/commented-out content — it renders nothing on the site. Either restore it as real content (it looks like useful "Types/Classification" material per the concept-doc skill's page structure) or remove it entirely; leaving commented blocks in a shipped doc looks like leftover authoring scaffolding.
| - Flow: [Create a patient](../../flows/clinical/create-patient) | ||
| - Playbook: [Outpatient registration](/deployments/hmis/playbooks/outpatient-registration) (HMIS) | ||
|
|
||
| ## FHIR reference |
There was a problem hiding this comment.
## FHIR reference narrates the mapping ("See your deployment's API base URL for GET /Patient and POST /Patient") instead of just linking the FHIR resource. Per the care-concept-doc skill, "Linking the FHIR resource page is good. Narrating the mapping is not." The FHIR link is already in the opening sentence — this section can be dropped or reduced to a one-line pointer without the endpoint narration.
| "flows/clinical/patient/manage-patient-users", | ||
| "flows/clinical/patient/view-patient-appointments" | ||
| ] | ||
| } |
There was a problem hiding this comment.
This PR only updates the version-3.1 sidebar (and only version-3.1 docs/flows). Per the shared conventions, version-3.0 and version-3.1 are kept byte-identical — the new Patient flow files, the reworked concept/reference docs, and this sidebar restructuring should all be mirrored into versioned_docs/version-3.0/ and versioned_sidebars/version-3.0-sidebars.json as well. Right now version-3.0/flows/clinical/ still only has create-patient.mdx, and its sidebar still points at the old single flow, so the two versions have diverged.
Regenerate the Patient concept and the nine flows from the care_docs markdown with publish.mjs, which now only handles frontmatter, link rewriting and MDX safety. Section structure, headings and wording are those of the authored source.
There was a problem hiding this comment.
Generated by Docs Reviewer for #40 · opus50 · 154.1 AIC · ⌖ 2.32 AIC · ⊞ 10.5K
|
|
||
| Note: You enter either a date of birth or an age, not both. | ||
|
|
||
| {/* |
There was a problem hiding this comment.
This large {/* ... */} block (lines 36-74) hides real content — Blood Group values, Patient Tags, Volunteer Contact, Profile Sections — from the rendered page. Commented-out drafts are leftover placeholders; either publish the sections or delete them. The same applies to the ## Configuration block at lines 93-100.
| Questionnaire Updates. Your permissions control which of these tabs you see. | ||
| */} | ||
|
|
||
| ## Patient Identifiers |
There was a problem hiding this comment.
## Patient Identifiers duplicates the identical paragraph still sitting inside the commented block at line 42. Keep one copy. Also add a blank line after the heading — the paragraph is glued to it.
| - Reference: [Patient (technical)](../../references/clinical/patient) | ||
| - Flow: [Create a patient](../../flows/clinical/create-patient) | ||
| - Playbook: [Outpatient registration](/deployments/hmis/playbooks/outpatient-registration) (HMIS) | ||
| - Flow: [Search for a patient](../../flows/clinical/patient/search-patient.mdx) |
There was a problem hiding this comment.
The ## Related list drops the reference link that was here before (- Reference: [Patient (technical)](../../references/clinical/patient)) and the HMIS playbook link. Concept↔reference cross-links are part of the concept page structure; please restore both.
| - Reference: [Patient (technical)](../../references/clinical/patient) | ||
| - Flow: [Create a patient](../../flows/clinical/create-patient) | ||
| - Playbook: [Outpatient registration](/deployments/hmis/playbooks/outpatient-registration) (HMIS) | ||
| - Flow: [Search for a patient](../../flows/clinical/patient/search-patient.mdx) |
There was a problem hiding this comment.
These flow links use .mdx, but per the shared conventions the flow docs are only extensionless when translated. create-patient.mdx was translated under i18n/ml/; its nine replacements are not, so .mdx is correct here — just confirm npm run build passes for the ml locale, since the Malayalam concept page now links ../../flows/clinical/patient/register-patient extensionlessly to a doc that has no ml source file.
|
|
||
| ### 4. Verify | ||
|
|
||
| If date of birth validation is added to verify patient's identity. The page shows the message "Please enter the patient's year of birth to verify their identity." |
There was a problem hiding this comment.
This sentence is a fragment and reads as a condition with no main clause. Suggested: "If your deployment configures date-of-birth verification, the page shows the message "Please enter the patient's year of birth to verify their identity."" (STE: one instruction per sentence, condition first).
|
|
||
| Enter the identifiers that your facility configures, for example a national identity number. | ||
|
|
||
| Identifiers that are configured as auto generated gets generated once patient registration is completed |
There was a problem hiding this comment.
Grammar and trailing space. Suggested: "Care generates the auto-generated identifiers after you complete the registration." Use the hyphenated "auto-generated" consistently — the identifiers flow already uses that form.
|
|
||
| ## Pre-requisites | ||
|
|
||
| - An administrator of a facility. |
There was a problem hiding this comment.
"An administrator of a facility." is not a prerequisite sentence about the reader's situation. Use the conventions' phrasing, e.g. "You are an administrator of the facility." (see the flow skill: write the user's situation).
|
|
||
| 1. Register the patient. See [Register a patient](./register-patient.mdx). | ||
| 2. Enter a value for every required identifier. | ||
| 4. Skip the identifiers that Care generates. You cannot enter these values. |
There was a problem hiding this comment.
The numbered list skips 3: it goes 1., 2., 4.. Renumber to 1, 2, 3.
|
|
||
| ### 4. View the patient's tokens | ||
|
|
||
| Token view on Patient's Home displays all the existing tokens for the patients |
There was a problem hiding this comment.
This step is descriptive, not an instruction, and has a trailing space and no full stop. Suggested: "Open the token view on Patient Home. Care shows the patient's existing queue tokens." (STE: steps are commands).
|
|
||
| Patient Home offers quick actions for the patient. Your permissions control which | ||
| quick actions appear. | ||
|
|
There was a problem hiding this comment.
The Expected Outcome claims tokens and appointments show "for all facilities or for one facility", but no step describes a facility filter. Please confirm this against care_fe or drop the qualifier — unverified UI behaviour should not go in a flow.
What
Moves the newly authored Clinical / Patient documentation into the docs site (version 3.1).
create-patientflow:version-3.1sidebar with the new flow ordering.create-patientlink: intro, homepage quick links, HMIS and palliative playbooks, and the Malayalam translations.create-patientflow.devLocaleWarningto readi18nfrom@generated/i18n(it is not onsiteConfigat runtime).Verification
npm run buildpasses for bothenandmllocales.