The OMOP Common Data Model allows for the systematic analysis of disparate observational databases. The concept behind this approach is to transform data contained within those databases into a common format (data model) as well as a common representation (terminologies, vocabularies, coding schemes), and then perform systematic analyses using a library of standard analytic routines that have been written based on the common format.

Prefix

omop

Alternative Prefixes

OMOP

Links

Homepage

Contact

Missing Contact

Pattern for Local Unique Identifiers

Local identifiers in Observational Medical Outcomes Partnership should match this regular expression:
^\d+$

Example Local Unique Identifier

1   Resolve

Pattern for CURIES

Compact URIs (CURIEs) constructed from Observational Medical Outcomes Partnership should match this regular expression:
^omop:\d+$

Example CURIE

omop:1

References

• Other https://github.com/callahantiff/OMOP2OBO
• GitHub Issue https://github.com/biopragmatics/bioregistry/issues/599
• GitHub PR https://github.com/biopragmatics/bioregistry/pull/600

Contributors

• submitter Charles Tapley Hoyt   0000-0003-4423-4370   cthoyt
• contributor Nicolas Matentzoglu   0000-0002-7356-1779   matentzn

A provider turns a local unique identifiers from a resource into a URI. Many providers are also resolvable as URLs (i.e., they can be used in a web browser).

The local unique identifier 1 is used to demonstrate the providers available for Observational Medical Outcomes Partnership. A guide for curating additional providers can be found here.

Additional providers curated in the Bioregistry are listed here. These are typically inherited from Identifiers.org or Prefix Commons, and need extra curation.