Clinic identity
A PlatformTenant represents a clinic or hospital, including its primary domain and configuration.
FertPro EMR is the umbrella brand. FertPro Clinical is the underlying platform: a shared Core, a specialty catalogue and a clinic-level configuration model.
The Core’s intended scope covers identity, encounters, documents, finance, quality management and reporting. Specialty modules extend that foundation with their own clinical requirements.
The catalogue foundation is additive: the architecture explicitly preserves existing IVF and Cryobank records while the tenant migration is prepared.
Understand readiness and safeguards ↗Identity · Encounters · Documents
Finance · Quality · Reporting
Conceptual architecture · Clinical readiness varies by module
The current foundation defines clinics, memberships and module entitlements. Enforcement across the application is a subsequent implementation phase.
A PlatformTenant represents a clinic or hospital, including its primary domain and configuration.
TenantModule records define which catalogue modules are enabled for each clinic.
TenantMembership models the user-to-clinic relationship. Host resolution and permission enforcement must be completed and verified.
The proposed address strategy separates public information, synthetic demonstrations and live clinical environments. The marketing domain is registered. Demonstration and clinic addresses below are proposed until individually configured and verified.
fertproemr.com/fertility · /aesthetics · /geriatricsdemo-fertility.fertproemr.com
demo-aesthetics.fertproemr.comclinicname.fertproemr.comDifferent addresses alone do not isolate data. Each clinical installation needs verified access controls, data boundaries and operational safeguards before live use.
Explore the right specialty, scope and rollout for your team.