×

Warning message

The installed version of the browser you are using is outdated and no longer supported by Konveio. Please upgrade your browser to the latest release.

Canadian Core Data for Interoperability (CACDI) Draft Version 2, September 2025
File name:

-

File size:

-

Title:

-

Author:

-

Subject:

-

Keywords:

-

Creation Date:

-

Modification Date:

-

Creator:

-

PDF Producer:

-

PDF Version:

-

Page Count:

-

Page Size:

-

Fast Web View:

-
Choose an option Alt text (alternative text) helps when people can’t see the image or when it doesn’t load.
Aim for 1-2 sentences that describe the subject, setting, or actions.
This is used for ornamental images, like borders or watermarks.
Preparing document for printing…
0%
Document is loading Loading Glossary…
Powered by Konveio

Comments

View all Cancel

Commenting is closed for this document.

Ken Sinn 2 Dec 4 2025 at 12:52PM on page 44

Suggestion
Suggest not including Health Care Provider Address Start/End date -- this data is very obscure, and I can't think of a practical use case outside of a Provider Registry. Certainly not for usual data exchange/interop. There isn't even a natural mapping in FHIR for Address start-end dates.

Ken Sinn 2 Dec 4 2025 at 12:38PM on page 45

tgateway links should be deprecated; the platform is considered sunset.
Work with Infoway Terminology team to develop a translated/hosted version on National TS.

Ken Sinn 2 Dec 4 2025 at 12:36PM on page 19

Suggestion
tgateway links should be deprecated; the platform is considered sunset.
Work with Infoway Terminology team to develop a translated/hosted version on National TS.

Ken Sinn 2 Dec 4 2025 at 12:32PM on page 37

Suggestion
Doesn't make sense for Immunization to have an End Date? should just be a Start Date.

Also, having an Immunization Date + Immunization Start Date + Immunization End Date seems like a lot of overlap/duplication.

Ken Sinn 2 Dec 4 2025 at 12:24PM on page 41

Suggestion
Current description "the date/time when the clinical service is reported as having been delivered" sounds like immunization start time or Procedure start time.
I think this Reported Clinical Information is meant to capture Time of Data Capture/Reporting? Otherwise there is a lot of confusion between the difference between the two.

Ken Sinn 2 Dec 4 2025 at 12:21PM on page 40

Suggestion
Health Service Event Type might be too granular/model-centric for a CACDI. It's reasonable in a LDM, but specifications & implementations won't explicitly model Health Care Service Events & Event Types in such an abstract way for exchange..

Ken Sinn 2 Dec 4 2025 at 12:19PM on page 40

Suggestion
Procedure Performed and Appendix: Procedure Code may cause confusion due to redundancy. Recommend leaving "code" for implementations to manage, and just keep Procedure Performed in CACDI.

Ken Sinn 2 Dec 4 2025 at 12:15PM on page 23

Procedure Reason has not yet been adopted by IPS/PS-CA; adoption of this element may be slow.

Ken Sinn 2 Dec 4 2025 at 12:14PM on page 15

May want to consider a "No Known Allergies or Intolerances" to avoid ambiguity when storing or viewing a Patient record with no listed allergies/intolerances; is nothing listed because the record is incomplete (or not asked), or because the Patient has confirmed the absence of any allergies/intolerances?

Ken Sinn 2 Dec 4 2025 at 12:14PM on page 21

May want to consider a "No Known Conditions" to avoid ambiguity when storing or viewing a Patient record with no listed Conditions; is nothing listed because the record is incomplete (or not asked), or because the Patient has confirmed the absence of any conditions?

Ken Sinn 2 Dec 4 2025 at 12:08PM on page 36

Suggestion
This is duplicative with Patient Service Language
Confusing to have the same element & content in both places.

Ken Sinn 2 Dec 4 2025 at 12:06PM on page 35

Identifier Start/End Dates aren't regularly captured for the patient health record exchange, but are applicable for billing/claims use cases.

Ken Sinn 2 Dec 4 2025 at 11:53AM on page 36

Question
Health Identifier Start/End Dates aren't regularly captured for the patient data exchange, but are more applicable for billing/claims use cases.

For Ontario EMR Core Data Set, only the Expiry Date is captured, not the Effective Date. What is the purpose of the Effective Date? Should only matter that the card hasn't expired.

Ken Sinn 2 Dec 4 2025 at 11:39AM on page 33

Name Type is typically not captured in data exchange standards (rarely more than one name is exchanged)

Ken Sinn 2 Dec 4 2025 at 11:32AM on page 33

Suggestion
Suggest capturing Issuing Organization, and leaving determination of Organization to implementations. The identifier issuer is rarely used in national/international specs; the identifier system provides sufficient detail on both the nature of the identifier, as well as the issuing organization. There is little need to separately capture an Organization code.

Ken Sinn 2 Dec 4 2025 at 11:27AM on page 12

Suggestion
When Service Language is captured in pan-Can specs, use of FHIR's "CommonLanguages" is the more common (though only a Preferred binding), and is generally used more often internationally.

Ken Sinn 2 Dec 4 2025 at 11:25AM on page 12

Suggestion
Would suggest to allow either Date of Death or a Death Indicator (True/False), in case the exact date isn't known, for maximum flexibility

Ken Sinn 2 Dec 4 2025 at 11:24AM on page 11

Suggestion
tgateway link should be deprecated, and the platform is considered sunset.
Consider using link, or work with Infoway Terminology team to develop a translated/hosted version on National TS.

Ken Sinn 1 Dec 4 2025 at 11:23AM on page 11

Suggestion
tgateway link should be deprecated, and the platform is considered sunset.
Consider using link, or work with Infoway Terminology team to develop a translated/hosted version on National TS.

Ken Sinn Dec 4 2025 at 9:22AM on page 12

Suggestion
Name Used is useful in a practice setting (primary care EMRs, hospitals) as part of the patient's administrative profile. It's less applicable during data exchange, where only the patient's official/legal name is exchanged.
Could also be valuable in eReferrals & eConsults.
PS-CA, CA:eReC, and most PT specs are not capturing Names other than the official/legal.

Marcy Nov 28 2025 at 11:44AM on page 5

Suggestion
Suggest collection in place of capture -- capture can reflect power differentials, as it also can be defined as "an act of catching, winning, or gaining control by force" link.

Janice Spence Nov 18 2025 at 3:19PM on page 50

Question
Is this set of elements in the context of the Healthcare Provider Organization? Or used across multiple context settings?

Janice Spence Nov 18 2025 at 3:12PM on page 33

Question
Are these "Organization" elements still in context of Identifier Issuer Organization for PHI?

Janice Spence Nov 18 2025 at 1:34PM on page 36

Suggestion
Consider clarifying wording "the recommended supporting alternate"
in reply to Liz's comment

Liz Nov 13 2025 at 11:14AM on page 6

Disregard, I see below. Miigwetch

Liz Nov 13 2025 at 11:14AM on page 6

Suggestion
Where Indigenous Standards not considered essential

Mehala M Senthuran Nov 5 2025 at 2:40PM on page 7

Suggestion
This is not commonly in the personal profile but with the diverse cultures and name changes for married woman, does "Maiden Name" seems like an element that may need more attention in these days (maybe as optional in the interim)?

Carl Severson Oct 14 2025 at 11:12AM on page 24

Question
There is nothing in the CACDI about menstrual status, pregnancy history, or anything else women's health related. I would argue that at least some of these data should be included in the CACDI; menstrual status is of equivalent importance to other vital signs like blood pressure, for example. I make this comment as a gynecologist so I clearly have a bias! These measures are not in USCDI or AUCDI that I am aware of. I was on a call today where some of us were chatting about this today and whether or not we should make a case to have it included in the USCDI or AUCDI, so I am also planting the seed about a discussion of this here.

Janice Spence Sep 30 2025 at 9:26AM on page 11

Question
This is leveraging PrescribeIT on Terminology Gateway. Why is this valueset not used? link

Janice Spence Sep 30 2025 at 8:52AM on page 22

Suggestion
Could we add some guidance on when CCI classification should/could be used as the coding for this element. Given this is intended to support interoperability we should be clear as to the role of the alternate bindings to help guide implementers. Role clinical terminologies vs classifications etc...

Janice Spence Sep 30 2025 at 8:50AM on page 21

Suggestion
Could we add some guidance on when ICD-10 CA classification should/could be used as the coding for this element. Given this is intended to support interoperability we should be clear as to the role of the alternate bindings to help guide implementers. Role of clinical terminologies vs classifications etc...

Janice Spence Sep 29 2025 at 1:54PM on page 10

Suggestion
Suggest to add a note explaining log in required to access any value sets on the national terminology server

Janice Spence Sep 29 2025 at 1:52PM on page 9

Suggestion
The Terminology Foundation column includes information on the code system leveraged, as well as the applicable valueset creation method (extensional or intensional, inclusion or exclusion criteria). Not all valuesets are intensional or created with logical definitions nor are all SNOMED CT based but that is all this definition covers. Suggested to revise appropriately.

ewithey Sep 22 2025 at 9:45AM on page 7

Question
Are there any data categories or data elements that you would like to see included in future versions of the Canadian Core Data for Interoperability (CACDI)?
View all