Snapshot 3: Connectathon 32 Base

This is Snapshot #3 for FHIR R5, released to support Connectathon 32. For a full list of available versions, see the Directory of published versions.

Example Patient/proband (JSON)

Patient Administration Work GroupMaturity Level: N/AStandards Status: InformativeCompartments: Patient, Practitioner, RelatedPerson

Raw JSON (canonical form + also see JSON Format Specification)

Genetic Risk Assessment Person

{
  "resourceType" : "Patient",
  "id" : "proband",
  "text" : {
    "status" : "generated",
    "div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\"><p style=\"border: 1px #661aff solid; background-color: #e6e6ff; padding: 10px;\"><b>Anonymous Patient</b> female, DoB: 1966-04-04 ( Computer-Stored Abulatory Records (COSTAR): 999999999 (use: USUAL))</p><hr/><table class=\"grid\"><tr><td style=\"background-color: #f3f5da\" title=\"Record is active\">Active:</td><td>true</td><td style=\"background-color: #f3f5da\" title=\"Known status of Patient\">Deceased:</td><td colspan=\"3\">false</td></tr></table></div>"
  },
  "identifier" : [{
    "use" : "usual",
    "type" : {
      "text" : "Computer-Stored Abulatory Records (COSTAR)"
    },
    "system" : "urn:oid:2.16.840.1.113883.6.117",
    "value" : "999999999",
    "assigner" : {
      "display" : "Boston Massachesetts General Hospital"
    }
  }],
  "active" : true,
  "gender" : "female",
  "birthDate" : "1966-04-04",
  "deceasedBoolean" : false
}

Usage note: every effort has been made to ensure that the examples are correct and useful, but they are not a normative part of the specification.