Condition

Health Concerns / Problems : USCDI v1 - The Condition resource is used to record problems, diagnoses, or other health matters that are concerning to a patient, and generally refers to the problem list. Diagnoses are recorded on an encounter to document conditions addressed or treated during a specific patient visit.

General Information

The connectivity of this FHIR endpoint is as follows:

HTTP Method
GET, POST
URL Template
https://portal.viewmymed.com/fhir/Condition?_id=token&patient=reference&_count=number&date=date&status=token&_pretty=boolean&_revinclude=static
Supported OAuth 2.0 User Types
Backend Systems, Clinicians or Administrative Users, Patients
Profiles Supported
  • Us Core Condition
  • Request Parameters

    The following fields and datatypes are the parameters for the request string. All fields are optional, however if no settings are set, all values will be exported up to the maximum count of 100

    Name (type) Description (bindings)
    _id
    (token)
    A single or comma separated list of Condition ids. It is a required field if the patient field is not given.
    patient
    (reference)
    Who the condition is for. It is a required field if the _id field is not given.
    _count
    (number)
    The maximum number of results to return in a page. Not honored when '_id' is set.
    date
    (date)
    A date or date range from which to find condition. The 'date' parameter may be provided once without a prefix or time component to imply a date range or once without a prefix and with a time component to search for condition at a specific time. Alternately it may be provided twice with 'le' and 'gt' prefixes to search for condition within a specific range. The date prefix pair must create a closed range.
    status
    (token)
    The overall status of the condition.
    _pretty
    (boolean)
    set to false to disable formatted output.
    _revinclude
    (static)
    _revinclude parameter may be provided once with the value Provenance:target to pull the relevant Provenance information. Example: _revinclude=Provenance:target

    Returned Data Fields

    The following fields and bindings are returned if valued

    Field (type) Description (bindings) Opt?
    id
    (Id)
    Id
    patient
    (Reference)
    Reference to a patient resource for whom the problem list is relevant
    encounter
    (Reference)
    Reference to a patient encounter for whom the problem list is relevant
    code
    (CodeableConcept)
    The display name for the condition.

    SNOMED CT (http://snomed.info/sct)
    category
    (CodeableConcept)
    Hard coded 'care-plan-problem'

    Condition Category Codes (http://terminology.hl7.org/CodeSystem/condition-category)
    clinicalStatus
    (CodeableConcept)
    The clinical status, which can be active, resolved, or inactive.

    Condition Clinical Status Codes (http://terminology.hl7.org/CodeSystem/condition-clinical)
    verificationStatus
    (CodeableConcept)
    If the problem list is on the patient's chart, this element specifies confirmed

    Condition Verification Status Codes (http://terminology.hl7.org/CodeSystem/condition-ver-status)

    Default Patient Query

    The following are live queries representative of a data request on our sandbox environment.

    Headers

    Accept: application/fhir+json
    Authorization: <OAuth2 Bearer Token>

    Request

    GET https://portal.viewmymed.com/fhir/Condition?patient=99999.122753-00&_count=1

    HTTP/1.0 200 OK
    Cache-Control: no-cache, private
    Content-Type:  application/fhir+json
    Date:          Mon, 02 Feb 2026 13:37:19 GMT
    Etag:          W/"1"
    
    {
        "resourceType": "Bundle",
        "id": "6980a88f88f6d6980a88f88f6e",
        "type": "searchset",
        "link": [
            {
                "relation": "self",
                "url": "https://portal.viewmymed.com/api/Condition"
            }
        ],
        "entry": [
            {
                "fullUrl": "https://portal.viewmymed.com/fhir/Condition/9247e7ebf6ca6c20d9ba4b7ec686cd96",
                "resource": {
                    "resourceType": "Condition",
                    "id": "9247e7ebf6ca6c20d9ba4b7ec686cd96",
                    "meta": {
                        "versionId": "9247e7ebf6ca6c20d9ba4b7ec686cd96",
                        "lastUpdated": "2023-01-26T06:33:04+00:00"
                    },
                    "text": {
                        "status": "generated",
                        "div": "

    ICD-10: ZZZ.

    \n

    Description: Uncoded Diagnosis

    \n

    Status: Active

    \n

    Onset: / /

    \n
    " }, "subject": { "reference": "Patient/99997.122753-00" }, "encounter": { "reference": "Encounter/fb9f088c689044da7a617c6ae144be05" }, "recordedDate": "2015-08-01T00:00:00+00:00", "code": { "coding": [ { "system": "http://terminology.hl7.org/CodeSystem/data-absent-reason", "code": "unknown" } ] }, "category": [ { "coding": [ { "system": "http://terminology.hl7.org/CodeSystem/condition-category", "code": "problem-list-item", "display": "Problem List Item" } ] } ], "clinicalStatus": { "coding": [ { "system": "http://terminology.hl7.org/CodeSystem/condition-clinical", "code": "active" } ] }, "verificationStatus": { "coding": [ { "system": "http://terminology.hl7.org/CodeSystem/condition-ver-status", "code": "confirmed" } ] } } } ] }

    Error Codes / Outcomes

    All endpoints share the same error codes and common outcomes.