Condition read

get/Condition/{id}
Page View

This resource contains details of a clinical diagnosis, problem, or other concept that needs to be conveyed for context about a patient’s wellness. This could be sent prior to a patient visit or received as a follow-up. A condition may or may not be related to a specific encounter, and the details may be about a condition that's active, resolved, or recurring.  

You can receive, retrieve, or save condition information.

read

This interaction allows you to review clinical condition information or context for a patient.

Request parameters

cURL request example

1
curl 'https://api.redoxengine.com/fhir/R4/{destinationSlug}/{environmentFlag}/Condition/{id}' \
2
--request GET \
3
--header 'Authorization: Bearer $API_TOKEN'

Request Parameters

  • id
    required, string

    Condition identifier

Response fields and example

1
{}
  • resourceType
    required, string

    Identifies the type of the resource

    Value: Condition
  • category
    required, Array of us-core or Other

    A category assigned to the condition.

      Categorizes this Condition as an entry on the patient's problem list

    • coding
      required, Array of object

      A reference to a code defined by a terminology system.

      • code
        required, string

        A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).

        Value: problem-list-item
      • system
        required, string

        The identification of the code system that defines the meaning of the symbol in the code.

        Value: http://terminology.hl7.org/CodeSystem/condition-category
    • text
      string

      A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user.

  • code
    required, object

    Identification of the condition, problem or diagnosis.

    • extension
      Array of OriginalText or Other

      May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.

        A human language representation of the concept (resource/element) as seen/selected/uttered by the user who entered the data and/or which represents the full intended meaning of the user.

        See http://hl7.org/fhir/StructureDefinition/originalText for more information

      • url
        required, string

        Source of the definition for the extension code - a logical name or a URL.

        Value: http://hl7.org/fhir/StructureDefinition/originalText
      • valueString
        required, string

        The original text

    • coding
      Array of object

      A reference to a code defined by a terminology system.

      • system
        string

        The identification of the code system that defines the meaning of the symbol in the code.

      • code
        string

        A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).

    • text
      string

      A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user.

  • subject
    required, object

    Indicates the patient or group who the condition record is associated with.

    Must be a resource of type Patient.

    • reference
      string

      A reference to another resource. This is typically either a relative reference which includes the resource type and ID, or an internal reference which starts with # and refers to a contained resource.

  • id
    string

    The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.

  • identifier
    Array of object

    Business identifiers assigned to this condition by the performer or other systems which remain constant as the resource is updated and propagates from server to server.

    • extension
      Array of Boolean, String, CodeableConcept, Coding, HumanName or Reference

      May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.

      • url
        required, string

        Source of the definition for the extension code - a logical name or a URL.

      • valueBoolean
        boolean

        A single value for the extension.

    • use
      string

      The purpose of this identifier.

      Possible Values: usual, official, temp, secondary, old (If known)
    • system
      string

      Establishes the namespace for the value - that is, a URL that describes a set values that are unique.

    • value
      string

      The portion of the identifier typically relevant to the user and which is unique within the context of the system.

  • clinicalStatus
    string

    The clinical status of the condition.

    Possible Values: active, recurrence, relapse, inactive, remission, resolved
  • verificationStatus
    string

    The verification status to support the clinical status of the condition.

    Possible Values: unconfirmed, provisional, differential, confirmed, refuted, entered-in-error
  • severity
    object

    A subjective assessment of the severity of the condition as evaluated by the clinician.

    • coding
      Array of object

      A reference to a code defined by a terminology system.

      • system
        string

        The identification of the code system that defines the meaning of the symbol in the code.

      • code
        string

        A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).

    • text
      string

      A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user.

  • encounter
    object

    The Encounter during which this Condition was created or to which the creation of this record is tightly associated.

    Must be a resource of type Encounter.

    • reference
      string

      A reference to another resource. This is typically either a relative reference which includes the resource type and ID, or an internal reference which starts with # and refers to a contained resource.

  • recordedDate
    string

    The recordedDate represents when this particular Condition record was created in the system, which is often a system-generated date.

  • recorder
    object

    Individual who recorded the record and takes responsibility for its content.

    Must reference one of the following types of resources:

    • Practitioner
    • PractitionerRole
    • Patient
    • RelatedPerson
    • reference
      string

      A reference to another resource. This is typically either a relative reference which includes the resource type and ID, or an internal reference which starts with # and refers to a contained resource.

  • note
    Array of object

    Additional information about the Condition. This is a general notes/comments entry for description of the Condition, its diagnosis and prognosis.

    • text
      required, string

      The text of the annotation in markdown format.

  • onsetDateTime
    string

    Estimated or actual date or date-time the condition began, in the opinion of the clinician.

  • abatementDateTime
    string

    The date or estimated date that the condition resolved or went into remission. This is called "abatement" because of the many overloaded connotations associated with "remission" or "resolution" - Conditions are never really resolved, but they can abate.