> ## Documentation Index > Fetch the complete documentation index at: https://docs.rcintell.com/llms.txt > Use this file to discover all available pages before exploring further. # Search UMLS concepts > Search UMLS concepts by name, CUI, or source code (optionally one vocab). ## OpenAPI ````yaml /docs/openapi.client.json get /v1/concepts/umls/search openapi: 3.1.0 info: description: >- Client API for RCIntel. Admin ingest, catalog sync, and internal audit routes are omitted. See Guides → Which API to use. summary: Multi-tenant knowledge API for healthcare revenue cycle management. title: Healthcare Knowledge Layer version: 0.1.0 servers: [] security: [] tags: - description: >- Geographic payer policy lookup (national NCD vs MAC LCD vs state). Query payer, code, state, plan_type. Each row includes geo_scope and document_version. name: policies - description: >- Payer network directory — search payers, check prior auth requirements, view filing rules, denial patterns, and appeal levels. name: payers - description: >- Resolve healthcare billing knowledge across the L1-L6 layer stack. Includes payment calculation, billing guidance, and per-layer queries. name: knowledge - description: >- CMS Fee Schedule lookups — OPPS (Addendum B / APC), DMEPOS (state-level pricing), and Clinical Lab Fee Schedule (CLFS). name: fee-schedules - description: >- NCCI (National Correct Coding Initiative) — dedicated MUE limits, PTP bundling edits, add-on code edits, and code pair validation. name: ncci - description: >- Service code intelligence — CPT/HCPCS lookup, RVU data, NCCI edits, payment calculation, implant/GUDID search, and service group classification. name: codes - description: >- Submit asynchronous AI agent jobs for code research, medical necessity, and denial resolution. Poll for results and retrieve reasoning traces. name: agents - description: >- Register and manage healthcare facilities by CCN (Medicare Provider Number). Each facility is the root entity for knowledge resolution. name: facilities - description: >- NPI Registry — live search against CMS NPPES API for provider and organization National Provider Identifiers. name: npi - description: >- OpenFDA drug product lookup by NDC. Includes product-level fields with normalized ingredient and package detail. name: drugs - description: Health checks, service metadata, and Prometheus metrics. name: system paths: /v1/concepts/umls/search: get: tags: - knowledge summary: Search UMLS concepts description: >- Search UMLS concepts by name, CUI, or source code (optionally one vocab). operationId: search_umls_concepts_v1_concepts_umls_search_get parameters: - description: Search by concept name, CUI, or source code. in: query name: q required: true schema: description: Search by concept name, CUI, or source code. minLength: 2 title: Q type: string - description: Maximum number of records to return. in: query name: limit required: false schema: default: 20 maximum: 100 minimum: 1 title: Limit type: integer - description: >- Optional source vocabulary filter, e.g. SNOMEDCT_US, RXNORM, ICD10PCS, LNC. in: query name: source_vocabulary required: false schema: anyOf: - type: string - type: 'null' description: >- Optional source vocabulary filter, e.g. SNOMEDCT_US, RXNORM, ICD10PCS, LNC. title: Source Vocabulary responses: '200': content: application/json: schema: $ref: '#/components/schemas/UMLSConceptSearchResponse' description: Successful Response '422': content: application/json: schema: $ref: '#/components/schemas/HTTPValidationError' description: Validation Error security: - APIKeyHeader: [] components: schemas: UMLSConceptSearchResponse: properties: reliability: $ref: '#/components/schemas/ReliabilityMetadata' results: items: $ref: '#/components/schemas/UMLSConceptSummary' title: Results type: array total_count: title: Total Count type: integer required: - total_count title: UMLSConceptSearchResponse type: object HTTPValidationError: properties: detail: items: $ref: '#/components/schemas/ValidationError' title: Detail type: array title: HTTPValidationError type: object ReliabilityMetadata: description: User-visible reliability metadata attached to API responses. properties: data_sources: additionalProperties: type: string description: Data-source backends used to build this response. title: Data Sources type: object dataset_versions: additionalProperties: type: string description: >- CMS/DHCS/NLM/FDA named versions used to compose this response (e.g. mpfs=CY2026, ipps=FY2026). See GET /v1/data/changes. title: Dataset Versions type: object degraded: default: false description: True when a fallback or non-primary source path was used. title: Degraded type: boolean generated_at: description: UTC timestamp when the response payload was composed. title: Generated At type: string warnings: description: Human-readable caveats relevant to downstream consumers. items: type: string title: Warnings type: array required: - generated_at title: ReliabilityMetadata type: object UMLSConceptSummary: properties: attribution: $ref: '#/components/schemas/UMLSAttribution' cui: title: Cui type: string preferred_name: title: Preferred Name type: string semantic_types: items: type: string title: Semantic Types type: array required: - cui - preferred_name - attribution title: UMLSConceptSummary type: object ValidationError: properties: ctx: title: Context type: object input: title: Input loc: items: anyOf: - type: string - type: integer title: Location type: array msg: title: Message type: string type: title: Error Type type: string required: - loc - msg - type title: ValidationError type: object UMLSAttribution: properties: confidence: title: Confidence type: number source_code: anyOf: - type: string - type: 'null' title: Source Code source_vocabulary: title: Source Vocabulary type: string umls_release: title: Umls Release type: string required: - source_vocabulary - umls_release - confidence title: UMLSAttribution type: object securitySchemes: APIKeyHeader: in: header name: X-API-Key type: apiKey ````