GET /codes/{code} is the primary endpoint for drilling into a MedDRA concept. It returns the concept metadata, hierarchy context, and change history you need for UI detail views or downstream processing.
Core properties
The response includes:code,term,level, andstatus– the canonical identifiers and the current lifecycle state (for example,CurrentorNon-current).isPrimaryandprimarySocCode– flags that help you highlight primary Preferred Terms within a System Organ Class.synonyms– Lowest Level Terms linked to the Preferred Term, returned with pagination via_meta.
synonymsPage and synonymsLimit to page through longer synonym lists.
Hierarchy context
The payload includesparents and children arrays, each item describing the relationship type (for example, SOC_TO_PT, HLT_TO_PT, PT_TO_LLT). This makes it easy to render tree views without issuing extra requests. If you only need the immediate parents, you can filter the array client-side.
Change insights
If the concept was added, updated, or retired in the current MedDRA release, thechange object provides:
changeType:ADDED,UPDATED, orRETIREDdetails: optional descriptive text from the source releasepreviousTerm: the prior term name, when applicable
GET /codes/{code}/changes to compare two versions directly.
Best practices
- Cache responses when building UI detail views; individual codes change infrequently between releases.
- Pair
changeTypeflags with styling to highlight newly added or retired concepts. - Combine hierarchy data with the
/versions/{toVersionId}/changesendpoint for release-level dashboards.