clinical-data-standards

Reason over MedDRA, ICD-10, SNOMED CT, and LOINC for accurate clinical coding and mapping.

13|5|Updated May 4, 2026
One-click install
npx skills add https://github.com/awslabs/hcls-agent-skills --skill clinical-data-standards
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clinical-data-standards
Source: https://github.com/awslabs/hcls-agent-skills/tree/main/skills/clinical-data-standards
Command: npx skills add https://github.com/awslabs/hcls-agent-skills --skill clinical-data-standards

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill resolves the complexity of navigating clinical terminology systems like MedDRA, ICD-10, SNOMED CT, and LOINC, preventing errors in adverse event coding, diagnosis grouping, and lab result interoperability.

Core Features & Use Cases

  • Terminology Reasoning: Provides decision frameworks for selecting the correct granularity in MedDRA and ICD-10 coding.
  • Mapping Guidance: Offers rules for cross-walking between disparate systems (e.g., MedDRA to ICD-10) to ensure regulatory compliance.
  • Use Case: Use this skill when you need to determine whether to report an adverse event at the Preferred Term level or aggregate it at the High Level Term level for a safety signal detection report.

Quick Start

Invoke the clinical-data-standards skill to determine the appropriate MedDRA hierarchy level for coding adverse events in a clinical study report.

Frequently Asked Questions about clinical-data-standards

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I map MedDRA terms to ICD-10 codes for regulatory compliance?

MedDRA to ICD-10 cross-walk mapping requires adherence to established regulatory hierarchies and official cross-walk conventions to ensure accurate diagnosis grouping and safety reporting compliance.

When do I need to report adverse events at the MedDRA Preferred Term vs High Level Term?

Adverse event reporting requires selecting the correct MedDRA granularity based on the safety signal detection requirements, using Preferred Terms for specific events or High Level Terms for aggregated analysis.

How does SNOMED CT terminology reasoning support EHR interoperability tasks?

SNOMED CT terminology reasoning ensures accurate clinical data coding and mapping across EHR systems, preventing errors in lab result interoperability and diagnosis documentation through standardized hierarchies.

What is the best way to ensure accurate LOINC coding for lab result interoperability?

LOINC coding for lab result interoperability relies on expert terminology reasoning and standardized coding frameworks to prevent mapping errors and ensure consistent clinical data exchange across systems.

Can I use clinical terminology standards for epidemiological study design and clinical trial safety reporting?

Clinical terminology standards support both epidemiological study design and clinical trial safety reporting by providing decision frameworks for selecting appropriate coding granularity across MedDRA, ICD-10, SNOMED CT, and LOINC systems.

Why does my clinical data coding produce errors when cross-walking between disparate terminology systems?

Cross-walking errors between terminology systems occur when official mapping conventions and established regulatory hierarchies are not followed, requiring expert reasoning to ensure accurate data mapping and compliance.