Why should you care?

ShopNest corporate wellness partner integrates hospital appointments — separate Patient entity schema from e-commerce Customer.

See it live — copy this example

Paste into a .NET project with EF Core packages, then run with LocalDB/SQL Server (dotnet ef / dotnet run).

public class Patient { public int Id { get; set; } public string Mrn { get; set; } = ""; public string FullName { get; set; } = ""; }
public class Appointment { public int Id { get; set; } public int PatientId { get; set; } public int DoctorId { get; set; } public DateTime ScheduledAt { get; set; } public string Status { get; set; } = "Booked"; }

var today = await db.Appointments
    .Include(a => a.Patient)
    .Where(a => a.ScheduledAt.Date == DateTime.UtcNow.Date && a.Status == "Booked")
    .OrderBy(a => a.ScheduledAt)
    .AsNoTracking()
    .ToListAsync();

What happened?

• Appointment links Patient and Doctor.
• Include loads patient name for reception desk list.
• AsNoTracking for read-only schedule board.

Practice next

1. Use separate bounded context from ShopNest commerce if combining systems.
2. Add audit columns on Patient access — who viewed record.
3. Encrypt sensitive columns or use column encryption for MRN if required.
4. Add Admission entity linked to Patient with discharge date.
5. Soft-delete appointments with HasQueryFilter on Status != Cancelled.

Remember

Hospital schema: Patient, Doctor, Appointment. Schedule query filters date and status. Keep PHI models isolated from retail catalog.

ShopNest wellness portal

Employee wellness module books Appointment with Doctor from ShopNest HR SSO identity mapped to Patient.

Outcome: Schedule API returns today's visits without exposing full medical history.