PointClickCare transitions need episode-and-facility identity

Resolve the facility and setting before assigning the episode

The direct answer is that an admission, discharge, or transfer signal is not yet a longitudinal episode. Preserve the source organization and facility identifiers, campus and location, sending system, care setting, encounter identifier and class, event type, event and message times, patient identifiers used for matching, source version, and any correction or cancellation. Map local and network identifiers explicitly; a familiar facility name or enterprise parent does not prove the physical location or setting where care occurred. ^[1]

Episode construction needs its own rule and version. Define which encounters can join, the time and clinical boundaries, transfers within a facility, acute-to-post-acute relationships, overlapping stays, observation status, emergency encounters, readmissions, duplicate feeds, and late corrections. Retain both the source events and the derived episode so a reviewer can reproduce why they were grouped without rewriting the original messages. ^[1]

Match the patient and attributed population independently

Patient matching should preserve the identifiers and demographics received, match method and version, candidate records, confidence or ambiguity, reviewer action, merge or unmerge history, and affected downstream work. A delivery associated with a network member does not establish that the event belongs to the intended person. High-consequence or ambiguous matches need a governed hold and correction path rather than automatic episode creation.

Attribution is a separate question. Record the payer, plan, ACO, provider, program, roster or relationship source, effective period, product, care-management rule, recipient organization, and permitted purpose. A correctly matched patient may not be in the recipient's attributed population at the event time, and a current roster does not necessarily answer historical eligibility. Preserve the evidence and the decision used when the task was opened.

Carry correction and cancellation through the episode

When a source corrects or cancels an event, link the new message to the prior one and recompute the episode through a controlled rule. Preserve supersession, reason, received time, prior derived state, changed facility or encounter facts, affected attribution, reopened or closed work, reviewer, and downstream acknowledgements. Do not delete the original signal or leave a care task attached to an encounter the source has withdrawn.

The episode record should then hand a bounded transition state to the care workflow: patient, source, facility, setting, encounter or episode, relevant event, attribution basis, uncertainty, data-use boundary, recipient, action owner, due time, and receipt. Resolve those source facts before treating notification delivery, a task assignment, or a completed follow-up as evidence that the correct episode prompted the correct action.

Test transfers, duplicates, and a corrected discharge

A representative test should include an emergency visit converted to inpatient status, an intra-system transfer, a post-acute admission, a duplicate network message, similar patient identities, an expired attribution, a facility alias, and a discharge later corrected or cancelled. Reviewers should reproduce the source events, patient match, facility mapping, episode grouping, attribution, recipient, correction effects, and retained uncertainty before any workflow outcome is credited. ^[1]

PointClickCare's official products page supports the attributed network, cross-setting encounter, event-notification, and care-transition positioning. It does not prove a customer's identity matching, facility map, episode logic, attribution, data completeness, delivery, clinical action, privacy or security compliance, savings, or outcome. Qualified clinical, interoperability, identity, care-management, privacy, security, compliance, and legal owners retain those decisions. ^[1]

Enterprise buyer test

Translate this change into the exact population, record type, workflow stage, decision owner, effective date, and evidence that could be affected. Ask current or prospective providers to demonstrate the named workflow with representative data and an exception—not a polished feature tour. Record what official documentation establishes, what a provider states, what the team observes, and what remains unresolved.

A defensible review also identifies the dependency outside the product. Authority interpretation, policy configuration, data quality, integrations, human judgment, approval rights, release governance, training, and retained evidence may remain customer or service responsibilities. The evaluation should preserve those boundaries instead of treating a technology claim as the complete operating model.

What we will watch next

Health Interoperability Review will watch the named source and affected market records for later evidence that changes status, scope, availability, implementation timing, workflow consequence, or the limits of the initial report. A later announcement does not silently overwrite this dated account; the change ledger preserves the sequence.