Halvorsen, Ingrid version 4.8.0+g4e56ddc

medical record number 771556, born 1980-01-17, in store default-store-2. Logical id eN7yU5tR3eW1qA9sD7fG5h.

← All patients

Records

3 in this patient's compartment — Patient:1 Encounter:1 Observation:1.

typeiddatesummaryoriginjson
PatienteN7yU5tR3eW1qA9sD7fG5hHalvorsen, Ingridfixture
json
{
  "resourceType": "Patient",
  "id": "eN7yU5tR3eW1qA9sD7fG5h",
  "meta": {
    "versionId": "1",
    "lastUpdated": "2025-06-24T09:02:00Z"
  },
  "identifier": [
    {
      "use": "usual",
      "type": {
        "coding": [
          {
            "system": "http://terminology.hl7.org/CodeSystem/v2-0203",
            "code": "MR",
            "display": "Medical record number"
          }
        ]
      },
      "system": "urn:oid:1.3.6.1.4.1.99999.2.1",
      "value": "771556"
    }
  ],
  "active": true,
  "name": [
    {
      "use": "official",
      "family": "Halvorsen",
      "given": [
        "Ingrid"
      ]
    }
  ],
  "gender": "female",
  "birthDate": "1980-01-17",
  "address": [
    {
      "use": "home",
      "line": [
        "31 Sedge Street"
      ],
      "city": "Fairhaven",
      "state": "MA",
      "postalCode": "02719",
      "country": "US"
    }
  ]
}
EncounterencN7a1Ws6Xt2025-06-24T08:30:00ZScreening referral, no diagnosis recordedfixture
json
{
  "resourceType": "Encounter",
  "id": "encN7a1Ws6Xt",
  "meta": {
    "versionId": "1",
    "lastUpdated": "2025-06-24T09:02:00Z"
  },
  "status": "finished",
  "class": {
    "system": "http://terminology.hl7.org/CodeSystem/v3-ActCode",
    "code": "AMB",
    "display": "ambulatory"
  },
  "type": [
    {
      "coding": [
        {
          "system": "http://snomed.info/sct",
          "code": "185349003",
          "display": "Encounter for check up"
        }
      ],
      "text": "Screening referral, no diagnosis recorded"
    }
  ],
  "subject": {
    "reference": "Patient/eN7yU5tR3eW1qA9sD7fG5h"
  },
  "period": {
    "start": "2025-06-24T08:30:00Z",
    "end": "2025-06-24T08:55:00Z"
  }
}
ObservationobsN7Wt1Yu2025-06-24T08:35:00ZBody weightfixture
json
{
  "resourceType": "Observation",
  "id": "obsN7Wt1Yu",
  "meta": {
    "versionId": "1",
    "lastUpdated": "2025-06-24T08:35:00Z"
  },
  "status": "final",
  "category": [
    {
      "coding": [
        {
          "system": "http://terminology.hl7.org/CodeSystem/observation-category",
          "code": "vital-signs",
          "display": "Vital Signs"
        }
      ]
    }
  ],
  "code": {
    "coding": [
      {
        "system": "http://loinc.org",
        "code": "29463-7",
        "display": "Body weight"
      }
    ],
    "text": "Body weight"
  },
  "subject": {
    "reference": "Patient/eN7yU5tR3eW1qA9sD7fG5h"
  },
  "encounter": {
    "reference": "Encounter/encN7a1Ws6Xt"
  },
  "effectiveDateTime": "2025-06-24T08:35:00Z",
  "issued": "2025-06-24T08:35:00Z",
  "valueQuantity": {
    "value": 71.2,
    "unit": "kg",
    "system": "http://unitsofmeasure.org",
    "code": "kg"
  }
}
date
The clinical date the record carries, whichever element its type puts it in. Blank where the type carries none. It is never meta.lastUpdated, which says when the rig wrote the row.
summary
The record's own coded text or the first coding's display. The JSON is the whole truth.
origin
fixture for a record out of the committed seed set, seeded for one written at runtime.

This is the store, not a source. Everything held for the patient is listed, including record types a narrower source does not serve and dates outside any search window — the same way the counts on the patients table are of the store rather than of what some source would answer. What a given client can actually read is decided by that source's profile and scopes, so prove a feed against the FHIR surface and never against this page.

The same records over the FHIR surface need a token and read, for example, /fhir/R4/Observation?patient=eN7yU5tR3eW1qA9sD7fG5h — a bare logical id, not Patient/eN7yU5tR3eW1qA9sD7fG5h, which that search refuses. This page needs no token: it is a rig operating surface over synthetic data, and its path carries _fake so any Arca code reaching for it is greppable.