Recent Articles

nullFlavor generally is the only attribute when it is used

May 15th, 2014|0 Comments

The article The nullFlavor attribute overviews the nullFlavor attribute in CDA, and its syntax.

In general, when the nullFlavor attribute is used with an XML element in CDA, no other attributes are used. Since the nullFlavor attribute […]

Representing an unknown NPI number

May 15th, 2014|0 Comments

The article Identifiers in CDA presents an overview of how identifiers are represented in the XML syntax of CDA documents. It describes the two primary attributes of identifier XML elements: root and extension.

The article The […]

Masking confidential information in MU2 C-CDAs

February 23rd, 2014|0 Comments

As explained in the article Use of nullFlavor in C-CDA templates and MU2 documents, it’s generally valid to use the nullFlavor attribute in a C-CDA document to express “no information” or similar, even for XML elements that […]

When is nullFlavor not allowed in C-CDA templates?

February 6th, 2014|0 Comments

As explained in the article The nullFlavor attribute, the nullFlavor XML attribute is used in CDA documents to indicate that information is missing, and why that information is missing.

As explained in the article Use of nullFlavor in C-CDA Templates and MU2 Documents, it’s […]

Use of nullFlavor in C-CDA templates and MU2 documents

February 6th, 2014|0 Comments

As explained in the article The nullFlavor attribute, the nullFlavor XML attribute is used in CDA documents to indicate that information is missing, and why that information is missing.

Use of nullFlavor in MU2 C-CDA Templates
When a […]

The nullFlavor attribute

February 6th, 2014|0 Comments

The nullFlavor attribute in CDA documents is used to indicate that information is missing and why it is missing.

The nullFlavor attribute is used in CDA XML elements in a way that is similar to how […]

The negationInd attribute

February 6th, 2014|0 Comments

The article Clinical act statements overviews the different XML elements contained withing entry elements, that express the core clinical statements in a CDA document.

Those clinical statement XML element are in turn contained within section elements, which in […]

Negating an entryRelationship

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 patient does NOT have a condition, allergy, immunization, procedure […]

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 […]

Negation in C-CDA

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 patient does NOT have a condition, allergy, immunization, procedure […]

Negating a problem observation

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 patient does NOT have a condition, allergy, immunization, procedure […]

UNK is not ideal for “no matching code”

February 6th, 2014|0 Comments

The article No matching code, details the scenarios in which an XML element that represents a code in a CDA document does not have a suitable “matching” code in the list of allowed codes assigned for use […]

No matching code

February 6th, 2014|0 Comments

The article Codes in CDA overviews the XML syntax of elements in CDA documents that represent codes – and the attributes of such elements (code, displayName, codeSystem, codeSystemName, and codeSystemVersion). It also references the dedicated articles […]

“No known…” vs. “no information about…”

February 6th, 2014|0 Comments

The article No Known…, discusses the context of (and presents the XML syntax for) situations in which a CDA section needs to report “no known allergies”, “no known medications”, etc.

The article The need for “no information” […]

“No information” sections

February 6th, 2014|0 Comments

The article The need for “no information” sections, overviews the context in which it is necessary to express “no information available” for an entire CDA document section. Refer to the article What is the overall structure […]

Future directions for “no information” sectons

February 6th, 2014|0 Comments

The article The need for “no information” sections, presents the context in which it is necessary to express “no information available” for an entire CDA document section.

The article “No known…” vs. “No information about…”, further elaborates on the meaning […]

No known…

February 6th, 2014|0 Comments

The article Clinical act statements overviews the different XML elements contained withing entry elements, that express the clinical statements in a CDA document.

The clinical statement XML elements in a CDA document generally assert positive statements. However, there are times when what needs to be […]

Representing “No Known” for Problems or Allergies

February 6th, 2014|0 Comments

No Known…
The article No Known…, explains how to use the negationInd attribute (refer to The negationInd attribute, for additional information about this attiribute) to express concepts such as “Not currently known to be taking any […]