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 CareTeam/example (JSON)

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

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

Care Team to address obesity

{
  "resourceType" : "CareTeam",
  "id" : "example",
  "text" : {
    "status" : "generated",
    "div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\">Care Team</div>"
  },
  "contained" : [{
    "resourceType" : "Practitioner",
    "id" : "pr1",
    "name" : [{
      "family" : "Dietician",
      "given" : ["Dorothy"]
    }]
  }],
  "identifier" : [{
    "value" : "12345"
  }],
  "status" : "active",
  "category" : [{
    "coding" : [{
      "system" : "http://loinc.org",
      "code" : "LA27976-2",
      "display" : "Encounter-focused care team"
    }]
  }],
  "name" : "Peter James Charlmers Care Team for Inpatient Encounter",
  "subject" : {
    "reference" : "Patient/example",
    "display" : "Peter James Chalmers"
  },
  "period" : {
    "end" : "2013-01-01"
  },
  "participant" : [{
    "role" : {
      "text" : "responsiblePerson"
    },
    "member" : {
      "reference" : "Patient/example",
      "display" : "Peter James Chalmers"
    }
  },
  {
    "role" : {
      "text" : "adviser"
    },
    "member" : {
      "reference" : "#pr1",
      "display" : "Dorothy Dietition"
    },
    "onBehalfOf" : {
      "reference" : "Organization/f001"
    },
    "coverageTiming" : {
      "repeat" : {
        "boundsPeriod" : {
          "start" : "2010-12-23",
          "end" : "2013-01-01"
        },
        "frequency" : 1,
        "period" : 1,
        "periodUnit" : "d",
        "dayOfWeek" : ["mon"],
        "when" : ["MORN"]
      }
    }
  }],
  "managingOrganization" : [{
    "reference" : "Organization/f001"
  }]
}

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.