What is the Medical Records mock data preset useful for?
The Medical Records preset creates entirely synthetic patient, encounter, provider, vital sign, symptom, note, and follow-up data for healthcare UI prototypes and test environments.
Generate API-ready mock data from this preset schema using the hosted mocking.dev faker API.
Edit, reorder, add, or remove fields before generating mock data from this preset.
This preview always requests one generated item from faker.mocking.dev, regardless of the download count.
The Medical Records preset creates entirely synthetic patient, encounter, provider, vital sign, symptom, note, and follow-up data for healthcare UI prototypes and test environments.
The Medical Records preset includes these top-level fields: id, patient, encounter, vitals, symptoms, clinicalNotes, followUpRequired. You can rename, remove, or extend the fields before generating data, including nested objects and arrays where supported.
Use it to test patient summaries, encounter timelines, vital sign ranges, clinical notes, follow-up indicators, nested record layouts, and healthcare dashboard tables without using real patient data.
Customize the fields, row count, seed, and locale in the editor. The preview updates as you make changes, and you can download the generated records as a JSON file when the schema is ready.
Yes. mocking.dev uses Faker.js through its mock data API to generate names, emails, dates, numbers, locations, commerce data, and other realistic values. The seed makes results repeatable, while the locale controls regional data.
No. The records are synthetic and intended for development, demos, fixtures, and automated tests. Generated values can resemble real information by coincidence, so do not treat them as verified identities or use them to contact people.
{
id: string;
name: string;
username: string;
email: string;
avatarUrl: string;
jobTitle: string;
isActive: boolean;
createdAt: string;
}{
id: string;
title: string;
description: string;
startsAt: string;
endsAt: string;
timeZone: string;
isAllDay: boolean;
location: string;
conferenceUrl: string;
organizer: {
name: string;
email: string;
};
attendees: {
id: string;
name: string;
email: string;
hasAccepted: boolean;
}[];
}{
id: string;
employeeNumber: string;
profile: {
fullName: string;
workEmail: string;
avatarUrl: string;
city: string;
country: string;
};
position: {
jobTitle: string;
department: string;
employmentType: string;
managerId: string;
};
compensation: {
annualSalary: string;
currency: string;
};
startedAt: string;
isActive: boolean;
}