Новая страница
Ниже — твой документ с встроенными скрин-плейсхолдерами в правильных местах (Action → Expected result → Screenshot). Формат уже готов для Confluence / Wiki.
Outpatient Physician Workflow: Patient Search and Consultation Management
1. Purpose of the Scenario
This scenario describes the full workflow of an outpatient physician:
- patient search
- opening the medical record
- working with consultations
- filling in and signing a consultation
2. System Login
Preconditions
- The user is authenticated under an outpatient physician account
Result
After successful login, the mainMain system workspace is displayed.
3. Patient Search
3.1 AvailableFast Search Parameters
PatientAction:
searchEnter ispatient performeddata viain the Fast Search window.
Available fields:panel:
- Ambulatory card number
- Case number
- Last name
- / First name
- / Middle name
- Date of birth (
dd.mm.yyyy) - Document
Expected result: System displays matching patients in the results table.
Screenshot: 📷 Figure 1 — Fast Search panel with available search fields
3.2 Search Results
AfterAction:
executingReview athe search,search aresults tabletable.
Expected result: A list of patients is displayed with the following columns:
- Time
- Code
- Full name
- Date of birth
- Attachment
- Residential address
- Registration address
- Additional information
- Doctor
Expected
Screenshot:
result📷
AFigure list2 of— patients matching thePatient search criteriaresults istable displayed.with highlighted row
3.3 No DataResults Scenario
IfAction:
Perform a search with no patientmatching is found:patients.
Expected theresult:
systemSystem displays themessage:
Data not found
Expected result
TheScreenshot:
user📷 understandsFigure that3 the— Empty search returnedresult nostate results(Data andnot canfound adjust search parameters.message)
4. Opening the Medical Record
4.1 ActionOpen Patient Record
ToAction:
openDouble-click a medical record:
Expected result: Patient medical record opens.
Screenshot: 📷 Figure 4 — Medical record header with patient context
4.2 Result
The patient medical record is opened.
4.3 Medical Record Header
TheDisplayed top section of the medical record displays:information:
- Patient full name
- Date of birth and age
- Ambulatory case number
- Search context
(Search patient / from / by)
Example:
- Patient: Artamonova Vlada
Date of birth:DOB: 04.05.1995 (31)AmbulatoryCasecase No.:No: 104197/2024
Expected result
TheScreenshot:
user📷 canFigure clearly5 identify— theMedical selectedrecord header (patient andidentification verify correctness.block)
5. Medical Record Structure
TheAvailable following tabs are available:tabs:
- Consultations
- Radiological Diagnostics
- Laboratory investigations
- Dentistry
- Referrals
- Medical history
- Visits
- Other
Screenshot: 📷 Figure 6 — Medical record tab navigation panel
5.1 Common Tab Actions
Each tab supports the following actions:supports:
- Print
— print data - Create
— create a new record - Create based on
— create based on an existing record - Edit
— edit a record
Screenshot:
5.2📷 AccessFigure Rights7 Rule
— 6. Consultations Section
6.1 PurposeConsultation List View
TheAction:
Open Consultations tab contains all patient consultation records.tab.
Expected
6.2 Consultationresult:
List Displayed fields:
- Consultation number
- Consultation date
- Payment type
Doctor’sDoctor name- Specialty
- Service name
- Visit / illness
- ICD-10 diagnosis
Document signedSigned status
Screenshot: 📷 Figure 8 — Consultations list with multiple records
6.2 No Previous Versions Rule
System limitation:
6.3 Expected result
The user sees a list of all patient consultations with summary medical and administrative data.
6.4 Limitations
6.5 Opening aOpen Consultation
Action
Action:
Expected resultresult:
The selected consultationConsultation form opensopens.
Screenshot:
📷 Figure 9 — Consultation form opened (latestoverview available version of the record).layout)
7. Consultation Form
7.1 General LogicPurpose
The consultation form is usedUsed for:
enteringfilling medical data- ordering
examinationsservices andservicesreferrals formingdiagnosisa diagnosiscreation- signing
theconsultation
7.2 Action Panel
- Save
— save changes - Save the
template — save astemplate - Upload a template
— load template - Sign
— sign consultation - Print
— print form - Close
Screenshot:
📷 Figure 10 — closeConsultation formaction panel (Save / Sign / Print)
7.3 Saving Rules
Action:
Click Save.Expected result:
Consultation can beis saved inas draftdraft.
Screenshot:
7.4 Signing Rules (Sign)
Conditions
Action:
forClick signingSign.
SigningSystem isrule:
allowed only if:
Restriction
Expected resultresult:
- If valid → consultation is signed
successfully - If invalid →
system preventssigningandisshows validation errorsblocked
Screenshot: 📷 Figure 12 — Mandatory fields highlighted in yellow + Sign validation
7.5 Editing Rules
Access control
- Users with
extendedsufficient permissions can edit consultations - Regular users may have read-only access
depending on role configuration
Screenshot: 📷 Figure 13 — Read-only vs editable consultation state
7.6 Consultation FormClinical Sections Overview
General
Sections Informationinclude:
paymentGeneraltypeinformationexamination type
Clinical Data
Conclusion
Statistical
Screenshot:
Information📷
7.7 Bottom Panel
Displays:Contains:
system version
doctor
informationinfospecialty
actions:
- Download Manual
- Exit
Screenshot:
📷 Figure 15 — Bottom system panel with Exit button7.8 Completing Work
AfterAction:
completingSave work:and/or sign consultation, then exit system.
Expected result: Session is safely closed.
Screenshot: 📷 Figure 16 — Exit button location in consultation form
Если хочешь, следующий шаг — я могу:
theпривестиconsultationэтоmustкbeConfluencesavedмакетуand/or(withsignedanchors + auto-numbering)theилиuser must exit the system using theсделатьExitединый шаблон для всех модулей (Consultations / Labs / Radiology),buttonчтобы дальше ты просто подставлял данные без переписывания структуры.