Johns Hopkins operates several digital systems that can appear closely related because the same person may use more than one of them. But myJH, JHED, SIS, Employee Self Service and MyChart are not interchangeable portals.
myJH is the broad Johns Hopkins digital gateway. JHED provides enterprise identity and directory functions. SIS owns important student-record functions. Employee Self Service handles University employee personal and payroll information. Johns Hopkins Medicine MyChart is a patient-facing clinical service.
Understanding this system map is often the quickest way to find the right destination.
myJH: The Digital Gateway
Johns Hopkins describes myJH as its online front door to hundreds of applications and resources.
The portal supports:
- application discovery;
- people and directory searches;
- departmental and topic searches;
- Recommended Tools;
- Favorites;
- access to account-related resources.
Its role is primarily to organize and provide access.
That does not mean myJH stores every underlying record.
JHED: Identity and Enterprise Directory
JHED stands for Johns Hopkins Enterprise Directory.
Johns Hopkins describes it as the comprehensive directory for University and Medical Institutions faculty, staff and students and says it is essential to myJH identification, authentication and personalization.
A JHED Login ID is used across multiple systems.
So:
myJH is where you enter the digital environment.
JHED helps establish who you are within that environment.
That distinction becomes particularly important during first-time setup, password troubleshooting or returning-affiliate identity problems.
SIS: Student Records, Registration and Billing
The Student Information System, or SIS, serves a different audience and purpose.
Johns Hopkins describes SIS as the University’s web-based system of record for:
- student records;
- registration;
- billing;
- course data.
Student-support documentation illustrates the difference further.
Students use SIS Self-Service for tasks including adding or dropping courses, viewing billing information and working with applicable financial-aid functions.
Those are SIS tasks, not general myJH profile functions.
Use SIS When You Need Things Like:
- registration;
- student billing;
- student account balance;
- course enrollment;
- academic-record functions;
- applicable student financial-aid information.
If the problem concerns a student record, reaching myJH successfully does not mean the issue can be corrected in myProfile.
Employee Self Service: Payroll and Employee Data
For Johns Hopkins University employees, Employee Self Service (ESS) has another distinct role.
Current Human Resources guidance says ESS provides employees with secure access to personal and payroll data and allows applicable changes such as:
- home and work addresses;
- direct-deposit information;
- tax withholding;
- pay statements.
ESS also provides a link to the e210 timekeeping system, where employees can review applicable timesheet and leave information.
This is why an employee searching myJH for a paycheck ultimately needs an employee payroll application, not merely the portal homepage.
myProfile vs ESS
This distinction deserves special attention because both can contain personal information.
myProfile concerns the person’s JHED identity and directory information.
ESS concerns the person’s University employee and payroll record.
A phone number appearing in an enterprise directory and a bank account used for payroll are not the same kind of data.
Do not assume changing one profile automatically changes every employment record.
Employee Self Service and Direct Deposit
Johns Hopkins HR explicitly identifies ESS as the location for adding or updating direct-deposit information.
Employment eligibility can also affect access to some employee functions. Current JHU HR guidance says certain new hires cannot update tax or direct-deposit information in ESS until required employment-verification processes are completed.
That is a good example of a workflow issue that can easily be mistaken for a portal malfunction.
The employee may be able to authenticate normally while a specific HR action remains unavailable because another onboarding requirement has not been completed.
MyChart: Patient Healthcare Access
Johns Hopkins Medicine MyChart is substantially different from all the systems above.
It is a patient-facing Epic service.
The current MyChart interface identifies functions including:
- viewing test results;
- communicating with healthcare providers;
- requesting prescription renewals;
- managing appointments;
- accessing another person’s information through authorized proxy arrangements;
- participating in video visits.
A person can simultaneously be:
- a Johns Hopkins employee,
- a JHED user,
- and a Johns Hopkins Medicine patient.
That does not combine the accounts into one system.
myJH vs MyChart
The similar naming is probably the easiest source of confusion.
myJH
Institutional access for Hopkins affiliates.
Typical question:
“Where is the application I use for work or school?”
MyChart
Healthcare access for patients.
Typical question:
“Where are my test results or appointments?”
These are fundamentally different intents.
For actual medical information, use the Johns Hopkins Medicine MyChart service rather than searching myJH for a patient chart.
myJH vs SIS
Students can also confuse myJH with SIS because they may reach student applications through the broader Hopkins digital environment.
The difference is ownership of the record.
myJH helps organize access.
SIS is the system of record for major student academic and financial functions.
A missing SIS application may begin as a myJH navigation issue.
An incorrect course registration or student bill is a SIS/SEAM issue.
Those are different layers.
myJH vs ESS
Employees encounter the same pattern.
myJH can be the gateway.
ESS is where University HR says employees can review and modify applicable personal and payroll data.
If an employee can reach ESS but the pay statement itself is wrong, the problem has progressed beyond myJH navigation.
Where myCloud and VPN Fit
Some systems are better understood as applications reached through the portal rather than separate record systems.
Johns Hopkins IT directs applicable users to myCloud through myJH and similarly routes VPN access through the Technology area of the portal. These services have their own client and MFA requirements.
Their relationship looks like:
myJH → launch resource → resource performs its specialized task.
This model applies to many of the hundreds of applications available through the portal.
A Task-Based Johns Hopkins System Map
If you need to find a Hopkins application:
Use myJH.
If you need to manage parts of your enterprise identity or directory profile:
Use myProfile/JHED.
If you need student registration or billing information:
Use SIS Self-Service.
If you are a JHU employee and need payroll, direct deposit or employee personal data:
Use Employee Self Service.
If you are a patient and need medical results, appointments or provider communication:
Use Johns Hopkins Medicine MyChart.
If you need remote application or network connectivity:
The relevant myCloud or VPN resource may be reached through myJH for applicable users.
Why This Distinction Matters for Troubleshooting
Suppose myJH opens successfully but SIS displays incorrect billing information.
Changing a JHED password is unlikely to correct the bill.
Suppose an employee reaches ESS but cannot make a direct-deposit change during onboarding.
That can involve an HR prerequisite rather than portal navigation.
Suppose a patient cannot see test results.
That belongs in MyChart support, not JHED directory administration.
Good troubleshooting begins by identifying the system that actually owns the data.
Different Support Organizations Exist for a Reason
Because these systems serve different purposes, Johns Hopkins maintains different support structures.
myJH technical problems can be directed to Johns Hopkins IT.
Student record and enrollment problems can involve SEAM and SIS support.
University employee HR and payroll matters can involve Human Resources.
Patient MyChart problems belong to Johns Hopkins Medicine’s patient-support environment.
An independent article should help you choose among those destinations rather than pretending to replace them.
One Hopkins Ecosystem, Multiple Systems
The central lesson is not that Johns Hopkins has “too many portals.”
It is that a large academic and healthcare institution separates different kinds of records and workflows into systems with different responsibilities.
myJH connects the environment.
JHED identifies users.
SIS manages major student records.
ESS manages major employee/payroll functions.
MyChart manages patient-facing healthcare information.
Once the ownership of each task is clear, the entire myJH ecosystem becomes substantially easier to navigate.