{scrollbar:icons=false}

Page info
title title

Revision History

Option 1

Overview (Option 1)

MedDRA loader serves as a bridge between MedDRA ontology to OWL loader. It first converts the MedDRA ontologies to OWL/RDF format, and then it employs the LexEVS OWL loader API to load the converted OWL/RDF ontology to LexEVS model.

Design Consideration (Option 1)

1. MedDRA loader is based on Manchester OWL API, which is the one of most popular OWL/RDF APIs. It supports OWL 2.0, and OWL/RDF ontology creation and modification.
2. the exported OWL/RDF ontology is saved in the file system. The path could be either provided by customers or using the system default.
3. a set of mappings need to be created between MedDRA to OWL/RDF ontology. It should cover the System Organ Class(SOC), High Level Group Term(HLGT), High Level Term(HLT), Preferred Term(PT) and Lowest Level Term(LLT) and their relationships
4. once the converted job is done, MedDRA loader automatically calls the LexEVS OWL loader API to load the OWL/RDF ontology into the LexEVS model.
5. create the LoadMedDRALaucher.java and scripts(.sh and .bat) for the command line loading.

Option 2

Overview (Option 2)

MedDRA loader directly loads the MedDRA ontologies into LexEVS model and database.

Design Consideration (Option 2)

1. MedDRA loader is based LexEVS loader interface.
2. a set of mappings need to be created between MedDRA to LexEVS. It should cover the System Organ Class(SOC), High Level Group Term(HLGT), High Level Term(HLT), Preferred Term(PT) and Lowest Level Term(LLT) and their relationships
3. create the LoadMedDRALaucher.java and scripts(.sh and .bat) for the command line loading.