Quick answer
Treat receipt, parsing, reconciliation and incorporation as separate states. A C-CDA document should retain its source and context while qualified users resolve differences before information becomes active. Test conflicting, missing and repeated data on the actual deployed version; certification scope and format support must be checked separately.
Inspect the point where imported information becomes active
A hospital summary arrives with one medication list, while the SNF chart contains another. The interface reports success. Staff still need to establish which information belongs to the resident, where it came from, when it was current and what should be incorporated.
ONC's reconciliation test method provides useful examples of displaying multiple sources, reconciling lists and user review and confirmation. Its certification context is not a blanket requirement that every SNF buy certified software or a complete clinical reconciliation protocol.
There is also a current transition to account for. The October 28, 2026 HTI-5 final rule retains the reconciliation criterion as a functional requirement while removing specified exchange-standard references. Its general effective date is December 28, 2026, with specified instructions effective January 1, 2027. As of this guide's November 10 review, distinguish the currently applicable criteria from the published changes. Contract explicitly for the formats and behavior needed by the facility.
Build a synthetic document pack
Use original synthetic cases, reviewed by clinical and technical staff, rather than copying real resident packets into a vendor demonstration.
| Case | Technical observation | Clinical workflow observation |
|---|---|---|
| Correct resident, routine summary | Identity and document source preserved | Intended reviewer receives work |
| Similar demographic identity | Ambiguity visibly held for resolution | No automatic wrong-chart incorporation |
| Conflicting medication status | Both source values and dates visible | Qualified user makes the reconciled decision |
| Missing allergy information | Missing/unknown state preserved | Not silently converted into “no allergies” |
| Repeated document | Duplicate or version relationship recognized | Existing decisions not silently overwritten |
| Unrecognized code or malformed section | Error localized and original content accessible as appropriate | Reviewer sees the limitation before relying on output |
Specify the document versions and templates the counterparties actually send. Supporting a named standard generally does not establish support for every variation in local production.
Preserve provenance through reconciliation
Separate the original document, parsed representation and accepted local data. Record the sending source, document date, relevant item status, reviewer and incorporation action. If an item is not incorporated, preserve an appropriate disposition so staff can distinguish intentional exclusion from a parsing failure.
A fictional test receives five medication entries. Two match existing items, one conflicts, one is historical and one cannot be mapped. A count of five imported entries would not establish a correct active list. The test should show the final reviewed result and explain each source item's disposition. Only qualified clinical staff determine the appropriate medication decisions.
Do not let a newer transport timestamp automatically imply newer clinical content. A document sent today may describe an older encounter. Test source dates and status display independently from arrival time.
Observe the downstream result
After acceptance, inspect the active lists, a later summary and the relevant clinical display. Verify that source context or unresolved limitations remain available where needed. Test a later corrected document and determine whether it creates new review work instead of silently reversing a prior decision.
If the receiver falls back to a human-readable document because structured incorporation fails, label that state clearly. It may preserve useful access but is not equivalent to successful structured reconciliation. Count the manual work and evaluate whether staff can sustain it at expected volume.
Accept a supported workflow, with limits
Require results for each synthetic case, the supplier's supported format/version statement, known parser limitations and the facility's clinical review process. Re-run affected cases after parser, terminology or format updates. Keep certification evidence in its own scope record, particularly as HTI-5 changes take effect.
The buying decision is whether incoming documents can become trustworthy, reviewed local information with visible exceptions. A transport acknowledgment alone cannot answer that question.
Questions & answers
Does a parsed C-CDA automatically become the active medication list?
It should follow the reviewed clinical reconciliation workflow. A successfully parsed document is evidence of technical processing, not a clinical decision to adopt every item.
Do the 2026 certification changes eliminate the need to test reconciliation?
No. HTI-5 changes certification requirements, including format references, while retaining a functional reconciliation criterion. Local clinical and technical acceptance needs remain.
Primary sources
Use the cited source and its applicable version when making a facility-specific decision. These guides explain operational evaluation methods; they are not individualized clinical, coding, or legal advice.