> ## Documentation Index > Fetch the complete documentation index at: https://docs.clinikehr.com/llms.txt > Use this file to discover all available pages before exploring further. # Get a condition > **Permission:** `conditions:read` Get one condition from the problem list. With `Accept: application/fhir+json` the answer is a FHIR R4 Condition. ## OpenAPI ````yaml /openapi/ehr-api.v1.yaml get /v1/clinics/{clinic_id}/conditions/{condition_id} openapi: 3.1.0 info: title: ClinikEHR API version: 1.0.0 description: >- Server-to-server REST API for a clinic's own data, reached with a key the clinic (or a developer workspace) creates in the developer portal. Authenticate every request with `Authorization: Bearer `. Test keys reach only your workspace's own synthetic sandbox; live keys reach the clinic that created them. Lists wrap their rows as `{ data, has_more, next_cursor }`; single resources are returned directly. Errors are `application/problem+json` (RFC 9457) with a stable `code`. Write requests accept an `Idempotency-Key` header so a retry never repeats a change. See the guides for authentication, permissions, pagination, rate limits and retries. servers: - url: https://api.clinikehr.com security: - ApiKey: [] paths: /v1/clinics/{clinic_id}/conditions/{condition_id}: get: tags: - Conditions summary: Get a condition description: |- **Permission:** `conditions:read` Get one condition from the problem list. With `Accept: application/fhir+json` the answer is a FHIR R4 Condition. operationId: getCondition parameters: - name: clinic_id in: path required: true schema: type: string format: uuid - name: condition_id in: path required: true schema: type: string format: uuid responses: '200': description: OK. content: application/json: schema: type: object required: - data properties: data: $ref: '#/components/schemas/Condition' '400': $ref: '#/components/responses/BadRequest' '401': $ref: '#/components/responses/Unauthorized' '403': $ref: '#/components/responses/Forbidden' '404': $ref: '#/components/responses/NotFound' '429': $ref: '#/components/responses/TooManyRequests' security: - ApiKey: [] components: schemas: Condition: type: object description: >- A diagnosis or problem-list entry — the exposed-field allow-list, field by field. `review_status` says where the record stands: `confirmed` is a row in the clinic's problem list (clinic truth; `verification_status: confirmed`, or `unconfirmed` while an item the clinic accepted automatically has not been reviewed by a clinician: see `accepted_by`); `pending` is an outside submission still waiting for a clinician (`verification_status: unconfirmed`); `rejected` and `withdrawn` are this key's own submissions that did not become chart truth. Only the submitting key or organization ever sees its own pending, rejected or withdrawn records. required: - id - patient_id - title - clinical_status - verification_status - review_status properties: id: type: - string - 'null' format: uuid description: >- The problem-list row's id once confirmed; null while the record is still a pending submission — use `submission_id` then. patient_id: type: string format: uuid title: type: string code: oneOf: - $ref: '#/components/schemas/ConditionCode' - type: 'null' clinical_status: type: string enum: - active - resolved - entered_in_error verification_status: type: string enum: - confirmed - unconfirmed onset_date: type: - string - 'null' format: date resolved_date: type: - string - 'null' format: date notes: type: - string - 'null' recorded_by: type: - string - 'null' format: uuid description: clinic_staff.id of the clinician who recorded or confirmed it. source: type: string enum: - clinic - api description: >- `api` for a record that came in through the API and was confirmed by a clinician. origin_assistant_name: type: - string - 'null' accepted_by: type: - string - 'null' enum: - clinic - automatic - null description: >- Who put this record on the chart: `clinic` (the clinic's own team, or a clinician who confirmed it) or `automatic` (the clinic chose to accept this kind of item from this key or connection without review; the record is on the chart but no clinician has reviewed it, so `verification_status` reads `unconfirmed` until one does). Null while the item is still a pending submission. reviewed_at: type: - string - 'null' format: date-time description: >- Set when a clinician marked an automatically accepted item reviewed; null otherwise. reviewed_by_staff_id: type: - string - 'null' format: uuid description: >- clinic_staff.id of the clinician who marked an automatically accepted item reviewed; null otherwise. review_status: type: string enum: - confirmed - pending - rejected - withdrawn submission_id: type: - string - 'null' format: uuid decision_reason: type: - string - 'null' description: >- Why a clinician rejected it. Present only when `review_status` is `rejected`. created_at: type: - string - 'null' format: date-time updated_at: type: - string - 'null' format: date-time ConditionCode: type: object description: >- A coded diagnosis. `system` names the code system: `icd-10-cm`, `icd-10`, `snomed-ct`, or `local` (a clinic's own code, never mapped to an HL7 system). The code is checked for SHAPE only — it is not looked up in a terminology. required: - system - code properties: system: type: string enum: - icd-10-cm - icd-10 - snomed-ct - local code: type: string Problem: type: object description: RFC 9457 application/problem+json. required: - type - title - status - code - request_id properties: type: type: string format: uri title: type: string status: type: integer detail: type: string code: type: string request_id: type: string errors: type: array items: type: object required: - pointer - message properties: pointer: type: string message: type: string responses: BadRequest: description: >- The request failed validation (unknown query parameter, limit out of range, malformed body). content: application/problem+json: schema: $ref: '#/components/schemas/Problem' Unauthorized: description: >- Missing, malformed, unknown, revoked or expired key, or the wrong secret. content: application/problem+json: schema: $ref: '#/components/schemas/Problem' Forbidden: description: >- The key or connection lacks the required scope, the plan does not include this resource, the request came from an address this key's IP allow-list does not permit, a TEST-environment workspace key asked for a clinic_id other than its own workspace's sandbox (`sandbox_only`), or a LIVE workspace key asked for a real clinic while its workspace's verification has lapsed (`not_verified`) — the response never names which addresses ARE allowed, nor which clinic actually is the sandbox. content: application/problem+json: schema: $ref: '#/components/schemas/Problem' NotFound: description: The record is absent, or out of the key's scope — one message for both. content: application/problem+json: schema: $ref: '#/components/schemas/Problem' TooManyRequests: description: Rate limited. See the Retry-After header. content: application/problem+json: schema: $ref: '#/components/schemas/Problem' securitySchemes: ApiKey: type: http scheme: bearer bearerFormat: ehr_live__ or ehr_test__ ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.