BC Client Registry FHIR Implementation Guide
1.0.0 - Build CI Canada flag

BC Client Registry FHIR Implementation Guide - Local Development build (v1.0.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions

ValueSet: BC Client Registry Patient Change Notification Events Value Set

Official URL: https://terminology.hlth.gov.bc.ca/ClientRegistry/ValueSet/bc-client-registry-patient-change-notification-events Version: 1.0.0
Active as of 2024-06-07 Computable Name: PatientChangeNotificationEventsValueSet

Codes used to indicate that type of patient changes that a subscriber is interested in receiving.

References

Logical Definition (CLD)

 

Expansion

Expansion based on codesystem BC Client Registry Patient Change Notification Events Code System v1.0.0 (CodeSystem)

This value set contains 10 concepts

CodeSystemDisplayDefinition
  COMPOSITEhttps://terminology.hlth.gov.bc.ca/ClientRegistry/CodeSystem/bc-client-registry-patient-change-notification-eventscomposite

Composite view distributions inform a subscribing system that their records are out-of-sync with the composite view and a subscriber that a data attribute has been modified on a specific source.

  DEATHhttps://terminology.hlth.gov.bc.ca/ClientRegistry/CodeSystem/bc-client-registry-patient-change-notification-eventsdeath

DEATH distributions inform a subscriber that they have a record that is out of sync with the Date of Death, or the Deceased indicator is present and a change to the composite view has occurred and a subscribing system there is a Date of Death, or the Deceased indicator is present and a change to the composite view has occurred.

  EIDhttps://terminology.hlth.gov.bc.ca/ClientRegistry/CodeSystem/bc-client-registry-patient-change-notification-eventseid

EID distributions inform subscribers when one of their source records has changed entity sets and/or is out-of-sync with the composite view.

  NEWhttps://terminology.hlth.gov.bc.ca/ClientRegistry/CodeSystem/bc-client-registry-patient-change-notification-eventsnew PHN

The New PHN (NEW) distribution is a non-source distribution and informs subscribers of all new PHNs.

  NEWBORNhttps://terminology.hlth.gov.bc.ca/ClientRegistry/CodeSystem/bc-client-registry-patient-change-notification-eventsnewborn

This distribution informs subscribers that a newborn record has been created in the EMPI, and has been assigned a PHN.

  NEWBORN_GENDERhttps://terminology.hlth.gov.bc.ca/ClientRegistry/CodeSystem/bc-client-registry-patient-change-notification-eventsnewborn gender

A non-source distribution and informs subscribers when the gender on a newborn record changes from unknown or undifferentiated to any other gender value.

  PHNhttps://terminology.hlth.gov.bc.ca/ClientRegistry/CodeSystem/bc-client-registry-patient-change-notification-eventsPHN change

PHN Change distributions inform source systems that their purported PHN is out-of-sync with the PHN in the composite view.

  PHNJOINhttps://terminology.hlth.gov.bc.ca/ClientRegistry/CodeSystem/bc-client-registry-patient-change-notification-eventsPHN Join

PHN Join distributions inform source systems that their record has joined an entity with a PHN.

  PHNMERGEhttps://terminology.hlth.gov.bc.ca/ClientRegistry/CodeSystem/bc-client-registry-patient-change-notification-eventsPHN Merge

PHN merge is a non-source distribution and informs subscribers of merged PHNs.

  SSRIhttps://terminology.hlth.gov.bc.ca/ClientRegistry/CodeSystem/bc-client-registry-patient-change-notification-eventsSSRI Sync

SSRI Sync distributions notify a parent system that one of its child system’s records has joined the set.


Explanation of the columns that may appear on this page:

Level A few code lists that FHIR defines are hierarchical - each code is assigned a level. In this scheme, some codes are under other codes, and imply that the code they are under also applies
System The source of the definition of the code (when the value set draws in codes defined elsewhere)
Code The code (used as the code in the resource instance)
Display The display (used in the display element of a Coding). If there is no display, implementers should not simply display the code, but map the concept into their application
Definition An explanation of the meaning of the concept
Comments Additional notes about how to use the code