Skip to content
This repository was archived by the owner on Aug 11, 2021. It is now read-only.

About OCL

Jonathan Payne edited this page Dec 14, 2017 · 15 revisions

OCL is an open-source, cloud-based platform for collaborative terminology management.

Use OCL to harmonize your health data across platforms and to enable interoperability, so that you can better use your health information to improve health.

The aim of OCL is to increase liquidity of data across organizational boundaries by improving the usability of your data. Curated terminology resources. It gives users access to the most commonly used sources of health informatics codes. The platform allows users to map local concepts/codes to internationally standardized terminology, which makes data interoperable with more reporting systems.

Users can use OCL to facilitate dictionary harmonization, information exchange, and reuse of analytics tools and approaches.

By managing and sharing this information, communities of practice can to accelerate convergence on best practices for data and data dictionary harmonization, information exchange, and reuse of analytics tools and approaches. This toolset includes innovative features that provide essential benefits to users at the facility and government level.

Concepts are the building blocks of health informatics.

  • Concepts represent unique ideas.
  • Codes uniquely identify concepts. They are numerical codes that identify clinical terms, organized in hierarchies.
  • Concepts and Codes are stored in Sources
  • Sources are created and owned by organization and groups (ICD-10, SNOMED, country-specific health terminology sets)
  • Relationships between Concepts from different Sources are shown through Mappings
  • Groups of mappings are stored in Collections
  • Dictionaries are groups of concepts (CIEL)

What does OCL allow me to do?

OCL allows users to

  • access the standardized sources of concepts like ICD-10, SNOMED, LOINC, etc
  • create subsets of data elements specific to a domain, age group, geography or condition
  • collaborate with other health informatics officers and organizations to build customized dictionaries
  • subscribe to the customized dictionaries of other organizations
  • share customized subsets, collections or dictionaries with other organizations
  • review and adopt xxxxx talk about QMs here
  • compare xxxx
  • see how concepts map to each other across dictionaries, allowing more dynamic measurement and ensuring interoperability

Clone this wiki locally