Recent Articles

Where do you indicate the referring physician in a CDA document?

October 21st, 2014|0 Comments

The CDA Header of a CDA document has XML sub-elements of the ClinicalDocument root element to represent the patient (the recordTarget element), the author of the CDA document (the author element), who the document is […]

The encounterParticipant element

October 21st, 2014|0 Comments

The encounterParticipant XML element in the CDA Header, is used to represent the care providers that participated in the primary encounter in which the clinical acts being documented in the CDA document took place.

Understanding encompassingEncounter
encounterParticipant is […]

Multiple recordTarget elements in one CDA document

August 22nd, 2014|0 Comments

The article The recordTarget element provides an overview of the recordTarget XML sub-element of the ClinicalDocument root element of all CDA documents.

As explained in detail in that article, the recordTarget element is part of the […]

Limitations of the allowed values for functionCode

April 7th, 2014|0 Comments

The article The serviceEvent/performer sub-element discusses the special use of the performer XML element, as a sub-element within the serviceEvent element, in the Header of a CDA document.

As that article explains, the serviceEvent/performer element has […]

The serviceEvent/performer sub-element

April 7th, 2014|0 Comments

The performer Element
The article The performer element, introduces the XML element named performer, in CDA documents.

The article notes that there are two closely related contexts in which the performer element is used. The primary use […]

The performer element

April 7th, 2014|0 Comments

performer is a Participation Element
The performer XML element in CDA documents, is one of several “participation” elements that connect roles/entities to clinical act statements. The following articles overview the relevant concepts:

The article “Entity” XML elements […]

The use of serviceEvent in C-CDA documents

April 7th, 2014|0 Comments

The serviceEvent Element
The article The serviceEvent element introduces and provides a basic explanation of the serviceEvent XML element in CDA documents, which is part of the CDA Header.

The serviceEvent element represents (in the words of […]

serviceEvent/performer vs. encompassingEncounter/encounterParticipant

April 3rd, 2014|0 Comments

The serviceEvent Element
The article The serviceEvent element introduces and provides a basic explanation of the serviceEvent XML element in CDA documents, which is part of the CDA Header.

The serviceEvent element represents (in the words of […]

The serviceEvent element

April 2nd, 2014|0 Comments

The serviceEvent XML element in a CDA document is located in the CDA Header under ClinicalDocument/documentationOf.

The reason it appears under documentationOf and not directly under ClinicalDocument is that both serviceEvent and ClinicalDocument are clinical act statements. […]

Use of encompassingEncounter in MU2 C-CDA documents

February 28th, 2014|0 Comments

The article The encompassingEncounter element, provides an overview of the use of the componentOf/encompassingEncounter element that is part of the CDA Header, as well as its XML syntax.

The encompassingEncounter XML element in the CDA Header, is used […]

Should there be an encompassingEncounter in a C-CDA CCD?

February 28th, 2014|0 Comments

The encompassingEncounter element
The article The encompassingEncounter element, provides an overview of the use of the componentOf/encompassingEncounter element that is part of the CDA Header, as well as its XML syntax.

The encompassingEncounter XML element in the CDA Header, […]

Use of encompassingEncounter in C-CDA document templates

February 28th, 2014|0 Comments

The article The encompassingEncounter element, provides an overview of the use of the componentOf/encompassingEncounter element that is part of the CDA Header, as well as its XML syntax.

The encompassingEncounter XML element in the CDA Header, is used […]

The encompassingEncounter Element

February 28th, 2014|0 Comments

The encompassingEncounter XML element in the CDA Header, is used to represent the primary encounter in which the clinical acts being documented in the CDA document took place.

The element’s full path is ClincialDocument/componentOf/encompassingEncounter – where the […]

Which encounters go in the CDA Header and which in the CDA Body?

February 28th, 2014|0 Comments

The article The encounter element overviews the use and XML syntax of the encounter element to represent “encounters” (interactions between a healthcare provider and patient – such as: office visits, hospital stays, or clinical consultation phone […]

The encounter element

February 28th, 2014|0 Comments

Clinical Statements
The article Clinical act statements, provides an overview of the clinical statements that form the “core” of a CDA document. Clinical statements are contained within entry elements, which in turn are contained within section elements, which in turn comprise the […]

Why can’t encounter and supply clinical statements be negated?

February 6th, 2014|0 Comments

The article The negationInd attribute introduces and overviews the use of the negationInd attribute with a clinical statement XML element in a CDA document, to express something that didn’t happen or isn’t present (that a […]