Care Coordination Management
0.0.1 - ci-build Estonia (EST)

Care Coordination Management, published by Helex OÜ. This guide is not an authorized publication; it is the continuous build for version 0.0.1 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/helexlab/ig-ccm/ and changes regularly. See the Directory of published versions

Artifact Index

Contents:

This page provides a list of the FHIR artifacts defined as part of this implementation guide.

Requirements: Actor Definitions

The following artifacts define the types of individuals and/or systems that will interact as part of the use cases covered by this implementation guide.

Client Registry

The Client Registry assists in uniquely identifying individuals who receive health care services by: Maintaining a central registry of all patients and their demographics and assigning a unique identifier to each patient.

Linking patient registration entries that result due to changes in patient demographics (patient moved to another location), data entry errors during patient registration, or missing demographic information.

Enabling health care workers to identify facilities at which a patient has received care.
Facility Registry

A registry that stores and manages standardized information about health facilities, serving as a central authority for facility data.
Health Management Information System

A system that collects, analyzes, and reports health data for monitoring and decision-making purposes.
Health Worker Registry

A registry that maintains information about health workers, including their identifiers, roles, and affiliations.

The Health Worker Registry serves as an authority for maintaining the unique identities of health workers within a context.

  • Pulls the minimum dataset of health workforce information from the various source data systems.

  • Merges the source data systems into an authoritative registry of health workers according to a data governance policy.

  • Allows queries of health worker information by client systems.
Terminology Service

A service that provides access to standardized code systems, value sets, and mappings to ensure consistent use of terminology across systems.

Structures: Logical Models

These define data models that represent the domain covered by this implementation guide in more business-friendly terms than the underlying FHIR resources.

Asutus

Asutuse andmekoosseis.
Patsient

Patsiendi andmekoosseis.
Spetsialist

Spetsialisti andmekoosseis.

Structures: Resource Profiles

These define constraints on FHIR resources for systems conforming to this implementation guide.

CarePlanCcm

CCM CarePlan profile linking a patient with a ResearchStudy and tracking lifecycle via progress entries.
CareTeamCcm

CCM CareTeam profile linking a patient with a ResearchStudy and tracking lifecycle via progress entries.
CommunicationCcm

CCM Communication profile linking a patient with a ResearchStudy and tracking lifecycle via progress entries.
GoalCcm

CCM Goal profile linking a patient with a ResearchStudy and tracking lifecycle via progress entries.
MedicationCcm

CCM Medication profile linking a patient with a ResearchStudy and tracking lifecycle via progress entries.
MedicationStatementCcm

CCM MedicationStatement profile linking a patient with a ResearchStudy and tracking lifecycle via progress entries.
OrganizationCcm

A localized profile of Organization for use in CCM.
PatientCcm

A localized profile of Patient for use in CCM.
PractitionerCcm

A localized profile of Practitioner for use in CCM.
PractitionerRoleCcm

A localized profile of PractitionerRole for use in CCM.
ProcedureCcm

A localized profile of Procedure for use in CCM.
ResearchStudyCcm

A localized profile of ResearchStudy for use in Estonian clinical research settings.
ResearchSubjectCcm

CCM ResearchSubject profile linking a patient with a ResearchStudy and tracking lifecycle via progress entries.
TaskCcm

A localized profile of Task for use in CCM.

Example: Example Instances

These are example instances that show what data produced and consumed by systems conforming with this implementation guide might look like.

Example of CCM Care Plan

A sample care plan instance conforming to the CCM localized profile.
Example of CCM Care Team

A sample care team instance conforming to the CCM localized profile.
Example of CCM Communication

A sample communication instance conforming to the CCM localized profile.
Example of CCM Goal

A sample goal instance conforming to the CCM localized profile.
Example of CCM MedicationStatement

A sample medication statement instance conforming to the CCM localized profile.
Example of CCM Organization

A sample organization instance conforming to the CCM localized profile.
Example of CCM Patient

A sample patient instance conforming to the CCM localized profile.
Example of CCM Practitioner

A sample practitioner instance conforming to the CCM localized profile.
Example of CCM PractitionerRole

A sample practitionerRole instance conforming to the CCM localized profile.
Example of CCM Procedure

A sample procedure instance conforming to the CCM localized profile.
Example of CCM Research Study definition

A sample research study instance conforming to the CCM localized profile.
Example of CCM ResearchSubject

Example linking a patient to a ResearchStudyStudy with lifecycle entries.
Example of CCM Task

A sample task instance conforming to the CCM localized profile.