About [PUBLICATION NAME]

[PUBLICATION NAME] is an independent editorial resource covering the digital systems people encounter across Johns Hopkins University and Johns Hopkins Medicine.

Our primary subject is myJH, the Johns Hopkins portal used to reach hundreds of institutional applications and resources. Because myJH sits in the middle of a much larger environment, useful coverage also requires explaining related systems such as the Johns Hopkins Enterprise Directory (JHED), myProfile, Student Information System (SIS), Employee Self Service (ESS) and other institutional tools.

Our Editorial Approach

We organize the site around real user tasks rather than keyword variations.

Someone trying to establish a first JHED account has a different problem from someone who can authenticate but cannot find an application. A student looking for tuition information has a different destination from an employee changing direct deposit. A Johns Hopkins Medicine patient trying to view test results has a different need from either of them.

Those distinctions determine our coverage.

We prioritize current first-party documentation from:

• Johns Hopkins Information Technology;
• myJH Support;
• Johns Hopkins University;
• Johns Hopkins Human Resources;
• Johns Hopkins student services;
• Johns Hopkins Medicine.

When official documentation does not establish a fact, we do not present speculation as if it were an institutional process.

What We Do Not Do

[PUBLICATION NAME] is not a Johns Hopkins login service.

We do not reproduce institutional authentication forms, process account recovery, request MFA codes or collect payroll, student or medical credentials.

We also avoid treating every Johns Hopkins application as a variation of “the myJH portal.” Accurate system boundaries are central to our editorial approach.

For example, JHED is an identity and directory system closely tied to myJH, while SIS is the system of record for student registration, billing and course data. Employee Self Service performs payroll and employee-data functions, and MyChart serves Johns Hopkins Medicine patients.

Understanding those relationships is often more useful than another generic login walkthrough.

Independence

[PUBLICATION NAME] is operated independently by [OPERATOR NAME].

Unless explicitly stated otherwise, this publication is not affiliated with, endorsed by or operated by Johns Hopkins University, Johns Hopkins Medicine, Johns Hopkins Health System or any related institution discussed in our coverage.

Johns Hopkins controls its official systems, authentication procedures, employee records, student records and patient services.

Our role is editorial: explain the landscape, identify the appropriate official destination and help readers understand which system owns which task.