Medical module

The medical module is for salon owners who also offer healthcare services (aesthetic clinics, medical cosmetology, plastic surgery, dermatology, physiotherapy). It enables EESZT-compatible visit documentation, BNO-10/OENO codes, and encrypted TAJ number management.

This article describes the manager-side settings and features. The administrative steps for EESZT connection (registration, certificates, etc.) our support team handles individually with you.

Where to find it

The sidebar shows a Medical menu (only if Medical module is enabled on your tenant). Two main sub-pages:

• Visit documentation: patient visit records
• EESZT settings: institution and connection configuration

Visit documentation

After a patient appointment is completed, a "Visit documentation" button appears in the manager (or Manager mobile app). Click to open the document editor.

What the document contains

• Event type: Examination, Intervention, or Consultation
• BNO-10 diagnosis code: searchable from the complete Hungarian BNO-10 table
• OENO procedure code: searchable from the Hungarian procedure-code table
• Clinical notes: anamnesis, physical exam, therapy/treatment plan, other notes
• EESZT status: shows whether the document has been submitted to EESZT (if integration is active)

How to create one

1. Click a completed appointment in the calendar
2. Visit documentation button
3. Pick event type
4. Search and pick a BNO-10 code (if examination/intervention)
5. Pick an OENO code if applicable
6. Write clinical notes in all four sections
7. Save

The document appears on the patient's profile and the visit documentation list.

BNO-10 code search

The complete Hungarian BNO-10 (ICD-10) code table is built in. In any code field:

• Type at least 2 characters
• Search by code (e.g., "B02") or Hungarian name (e.g., "shingles")
• Autocomplete shows matches
• Click the right code

The Hungarian description fills automatically.

OENO code search

Same logic as BNO-10, but for the OENO (Hungarian procedure code) table. Use when documenting an intervention.

TAJ number management

You enter patients with a TAJ number on the customer form. The TAJ is stored AES-256-GCM encrypted, can't be read directly from the database. Compliant with GDPR and Hungarian healthcare data protection.

• Format: XXX XXX XXX (9 digits)
• The system validates the checksum
• Wrong checksum, save fails

EESZT settings (manager side)

Two places hold EESZT-related settings in the manager:

1. Institution data

Settings → Integrations → Medical/EESZT, or sidebar Medical → EESZT settings:

• Institution name
• OGYEI identifier
• ANTSZ license number
• Data controller declaration number

These appear on visit documents and EESZT submissions.

2. Physician data (per staff)

On the Team → individual staff profile, the Medical data section:

• Stamp number
• EESZT user ID
• Medical license number

Used on the visit document for the "performing physician".

3. EESZT connection status

The salon's EESZT connection is a tenant-level setting. When active:

• Documents auto-submit to EESZT Event Log on save
• Submission status shows on the document list (Submitted / Failed / Pending)

When not active:

• All module features work (documentation, BNO/OENO codes, TAJ management)
• The "submit to EESZT" button is inactive, documents stay locally

Use case scenarios

Scenario 1: Aesthetic clinic daily routine

Clinic has 5-10 patient visits a day. After each visit, the doctor opens visit documentation, picks event type, BNO/OENO codes, writes notes, saves. 2-3 minutes per patient, EESZT-compliant.

Scenario 2: Examination only, no intervention

An examination only, no procedure. Leave OENO empty, BNO is required. Document still saves.

Scenario 3: Updating a patient's TAJ

New patient arrives, reception enters TAJ. System validates checksum, saves. Now EESZT-compatible bookings can use this patient.

Scenario 4: Adding a new physician

New physician joins the clinic. Add their profile in Team, fill in Medical data section with stamp number, EESZT ID, license number. They can now be the performing physician on documents.

Scenario 5: Verifying EESZT submission

Filter the visit documentation list by EESZT status. If you find "Failed" entries, the error is in the detail view, and you can resubmit.

Tips

• Document right after the visit: fresh memory, fewer errors.
• Use standard clinical text templates: anamnesis and physical sections largely repeat. Save templates to save time.
• Multiple diagnoses and procedures: one main BNO and any number of secondary BNOs, plus multiple OENOs.
• TAJ encryption is also visible-protected in the manager: only last 4 digits show on the profile. Full TAJ is only in audit views.
• EESZT connection is optional: the module is useful even without EESZT, for local documentation. When ready for EESZT, contact support and we'll guide you through.

FAQ

Q: Can I use the module without EESZT? A: Yes, all features (visit documentation, BNO/OENO codes, TAJ management) work without EESZT connection. EESZT submission is an add-on you can activate later.

Q: How many diagnoses and procedures per document? A: One primary BNO-10 plus any number of secondary diagnoses. Multiple OENO procedures can be entered too.

Q: What if the TAJ is wrong? A: System validates by checksum. Wrong TAJ won't save, error message appears.

Q: Where does my patient data go? A: TAJ stored AES-256-GCM encrypted by Bookinda. With EESZT connection, visit document data goes to the EESZT Event Log (institution, patient TAJ, date, BNO/OENO codes, physician stamp). Other team data (notes, photos) stays local in Bookinda.

Q: How do I enable the medical module? A: The medical module is available in higher Bookinda plans. If interested, email [email protected] and we'll help you activate and roll it out.