Skip to the content
Loading...
inHealth Precision Medicine
inHealth Precision Medicine
Explore REACH Help Center Contact Us
  • Who We Are
  • Platform (PMAP). Sub menu is available. Go to the button next to this link to open sub menu.
    • Patient Insight
  • Data Streams. Sub menu is available. Go to the button next to this link to open sub menu.
    • Epic EMR Clinical Data
    • Genomics & Molecular Data
  • Research Community
Help Desk

Johns Hopkins OMOP Data Sets

Breadcrumb back arrowJH-ADDs Request

IMPORTANT: Please use the proper format of [email protected].
Agreement(Required)

Agreement to not attempt to re-identify any data in this training dataset.

I agree to:

• Not re-distribute this data in any form

• Use this data only on the secure PMAP data platform

• Recognize that while this data is de-identified, it is patient data and should be managed and protected respectfully
× NOTE: Atlas requires SAFE Desktop. Request SAFE Desktop access HERE

NO LONGER ACCEPTING NEW REQUESTS

The JH-ADDs Pilot study is currently at capacity.
Attestation Step 1 of 14(Required)
No attempt will be made to re-identify patients.
Attestation Step 2 of 14(Required)
The data will not be redistributed, including posting on Journal sites that request original data.
Attestation Step 3 of 14(Required)
Projects that involve development of a tool, device, or other intellectual property that requires FDA or other regulatory approval will not use this data access mechanism, but submit an independent JHU IRB application.
Attestation Step 4 of 14(Required)
Data will be analyzed on PMAP or other computing environments approved for HIPAA limited datasets.
Attestation Step 5 of 14(Required)
I confirm that I will respond to an annual survey outlining which computing equipment we have used for analyses and summarizing findings.
Attestation Step 6 of 14(Required)
Report public presentations, posters, and publications in the anniversary survey annually
Attestation Step 7 of 14(Required)
Data linkage, if any, will be restricted to datasets that do not materially increase the risk of re-identification (Classes 3 or 4 in Data Linkage Class Descriptions uploaded to Section 20).
Attestation Step 8 of 14(Required)
Should inadvertent re-identification be discovered, investigators will immediately notify the PI of the IRB approved registry and the PI will formally report to the IRB, and inform the OMOP provisioning team.
Attestation Step 9 of 14(Required)
Recognize that while this data is de-identified, it is patient data and should be managed and protected respectfully and responsibly.
Attestation Step 10 of 14(Required)
No data accessed with this mechanism will be shared with any person, party, or organization outside of JHU. Project that require any kind of data sharing outside of JHU should submit an independent JHU IRB application.
Attestation Step 11 of 14(Required)
Agree that the investigator team will acknowledge the “Johns Hopkins De-identified Patient Repository” in any and all presentations, papers, or other publications.
Attestation Step 12 of 14(Required)
Ensure that all users of the data are under the fidciary responsibilty of the requesting investigator and documented.
Attestation Step 13 of 14(Required)
Ensure that all users of the data have completed IRB specified human subject research training.
Attestation Step 14 of 14(Required)
Ensure that this data is deleted when all analyses are completed (the dataset can be recreated in future for reproducibility purposes).
Name(Required)
Project Type(Required)
Please enter your cohort definition. If you have a Cohort Expression from Atlas, please enter it here.
F X in IG

Copyright © The Johns Hopkins University, The Johns Hopkins Hospital, and Johns Hopkins Health System. All rights reserved.

Contact Us

Thank you for your interest in Johns Hopkins Precision Medicine. Please complete the form below so we can route your request to the appropriate team and respond promptly.

Access Level(Required)
Max. file size: 49 GB.