The scenario

In Vulnverse v2, Hospital Network separates public patient services from internal systems that a healthcare organization would protect differently. Appointments, provider information and research documents form the public surface. EHR integration metadata, imaging records, pharmacy workflow data and device inventory form the private context.

This suits an exercise needing several kinds of sensitive business information rather than a generic customer database. A participant can distinguish a provider directory from an appointment record, or research metadata from an internal imaging reference, and explain why those objects need different access rules.

Public surfaces

Patients, referring providers and researchers reach the hospital through these routes; the configured exercise inventory sets the actual scope.

Public routes declared in the Hospital Network catalog
RouteSurfaceContext
/patient-portalPatient portal facade for appointments and records workflow.
/appointmentsappointments-apiAppointment and referral API simulation.
/providersprovider-directoryPublic provider directory and department listing.
/researchresearch-docsResearch document and trial metadata facade.

Private systems

ehr-integration Private application

Private EHR integration and message queue simulation.

imaging-archive Private data

PACS/imaging metadata store representation.

pharmacy-workflow Private application

Medication order and pharmacy workflow data.

device-inventory Private data

Biomedical and bedside device inventory.

Exercise questions

  • Which information can be public in a provider directory while remaining inappropriate for appointment or patient record views?
  • How should research documents be distinguished from clinical imaging and pharmacy workflow metadata?
  • What evidence shows that a device inventory observation belongs to the represented private context rather than a public patient service?

What to hand in

Create a classification and exposure report separating patient, public directory, research, clinical workflow and device context. Link observations to actual synthetic records and avoid importing real patient information.

Records and evidence

Synthetic patients, appointments, departments, research documents, imaging metadata and device inventory make the exercise specific to healthcare. Organize the findings by intended audience: patients, public directory visitors, researchers and internal clinical or device operations.

  • patients-synthetic
  • appointments
  • departments
  • research-docs
  • imaging-metadata
  • device-inventory

Record each Hospital Network finding with the research method →