Skip to main content

CareTeam

Overview​

The CareTeam resource provides "all the people and organizations who plan to participate in the coordination and delivery of care for a patient." (HL7 FHIR R4 CareTeam)

Purpose​

  • Represents care teams involved in patient care coordination
  • Tracks participants, roles, and responsibilities in care delivery
  • Supports care coordination workflows across healthcare organizations

Use Cases​

  • Care coordination across multiple providers
  • Team-based care management
  • Patient care planning and delivery tracking

Relationships​

  • Patient: References the patient receiving care
  • Practitioner/PractitionerRole: References care team members
  • Organization: References participating organizations
  • Encounter: May be associated with specific encounters

Resource Schema​

Key Fields​

FieldTypeDescriptionRequired
idstringLogical id of the resourceNo
statuscodeproposed | active | suspended | inactive | entered-in-errorYes
subjectReference(Patient)Who care team is forYes
participantBackboneElementMembers of the teamNo
participant.roleCodeableConceptType of involvementNo
participant.memberReferenceWho is involvedNo
periodPeriodTime period team coversNo
reasonCodeCodeableConceptWhy the care team existsNo
managingOrganizationReference(Organization)Organization responsible for the care teamNo

JSON Example​

{
  "resourceType": "CareTeam",
  "id": "example-careteam",
  "status": "active",
  "subject": {
    "reference": "Patient/123"
  },
  "participant": [
    {
      "role": [
        {
          "coding": [
            {
              "system": "http://snomed.info/sct",
              "code": "17561000",
              "display": "Cardiologist"
            }
          ]
        }
      ],
      "member": {
        "reference": "Practitioner/456"
      }
    }
  ],
  "period": {
    "start": "2023-01-01"
  },
  "managingOrganization": [
    {
      "reference": "Organization/789"
    }
  ]
}

Operations​

The Certified API CareTeam resource supports the following standard operations. However, support varies by the targeted CareRecord or solution.

CareRecord / SolutionCreateReadUpdateSearch
GEHRIMED-Yes-Yes
myAvatar-Yes-Yes
myEvolv-Yes-Yes
myUnity-Yes-Yes
TheraOffice-Yes-Yes

Read​

Retrieve a specific CareTeam resource by its ID.

Endpoint: GET /CareTeam/{id}

Search for care teams using various criteria.

GET Method​

Use GET for simple searches with parameters in the query string.

GET /CareTeam?parameter=value

POST Method​

Use POST for complex searches with form-encoded parameters.

POST /CareTeam/_search
info

Not all Netsmart solutions support CareTeam search. See supported operations table above and consult your target solution's documentation for more information.

Search Parameters​

Patient-based Search:

ParameterTypeRequiredDescriptionExample
patientreferenceYesWho care team is forpatient=value
statustokenNoproposedstatus=value
_revincludespecialNoInclude Provenance resource(s) that reference the matched search results. Allowed: "Provenance:target"_revinclude=value

ID-based Search:

ParameterTypeRequiredDescriptionExample
_idstringYesThe ID of the resource_id=value
_revincludespecialNoInclude Provenance resource(s) that reference the matched search results. Allowed: "Provenance:target"_revinclude=value

Examples​

Read Example​

Read CareTeam by ID
curl -X GET "https://fhir.netsmartcloud.com/provider/patient-access/v2/{tenant-id}/CareTeam/123" \
    -H "Authorization: {Bearer Token}" \
    -H "Accept: application/fhir+json"

Search Examples​

Via POST​

The POST method is recommended as it keeps health information out of the URL.

Search by Patient and Status
curl -X POST https://fhir.netsmartcloud.com/provider/patient-access/v2/{tenant-id}/CareTeam/_search \
    -H "Authorization: {Bearer Token}" \
    -H "Accept: application/fhir+json" \
    -H "Content-Type: application/x-form-urlencoded" \
    -d "patient=Patient/123" \
    -d "status=active"

Via GET​

Search by Patient and Status
curl -X GET "https://fhir.netsmartcloud.com/provider/patient-access/v2/{tenant-id}/CareTeam?patient=Patient/123&status=active" \
    -H "Authorization: {Bearer Token}" \
    -H "Accept: application/fhir+json"

Integration Patterns​

Common Workflows​

  1. Care Team Lookup: Retrieve active care teams for a specific patient
  2. Care Coordination: Use care team information to coordinate care across providers
  3. Team Management: Track care team composition and member roles over time
  • Patient: The subject of care team coordination
  • Practitioner: Individual care team members
  • PractitionerRole: Roles and specialties of care team members
  • Organization: Healthcare organizations participating in care
  • Encounter: Specific care encounters involving the team
  • CarePlan: Care plans managed by the care team

Integration Considerations​

  • Care teams may span multiple organizations and systems
  • Team composition can change over time - use period elements to track temporal aspects
  • Consider privacy and access controls when sharing care team information

Error Handling​

For detailed information about error responses and status codes, see the Error Handling documentation.

Supported Profiles​

This API supports the following FHIR profiles: