Recent Articles

“Condition” vs. “Disease” in Problem Type code values

August 22nd, 2014|0 Comments

There are four C-CDA entry templates which are designed for expressing observations of “problems” (the OID for the template identifier is show in parenthesis, following the template name):

Cognitive Status Problem Observation (2.16.840.1.113883.
Family History Observation (2.16.840.1.113883.
Indication […]

The sdtc:valueSet and sdtc:valueSetVersion attributes

May 16th, 2014|0 Comments

The article Codes in CDA presents an overview of the XML syntax that is used for coded elements in CDA documents.

In that article, in the discussion of the XML attributes of coded elements, reference is […]

Value sets

May 16th, 2014|0 Comments

Before You Read This Article…
The article Codes and code systems, introduces the concept of “codes” and “code systems” – which are fundamental to the representation of coded concepts (things represented with codes) in CDA documents. […]

Codes in CDA

February 6th, 2014|0 Comments

Note: Refer to the article Codes and code systems for an introduction to these two concepts.

Naming of Elements Representing Codes
In CDA, just about every XML element that is intended to represent a code has the word “code” […]

Working with the UCUM code system

February 6th, 2014|0 Comments

Note: Refer to the article Physical Quantities in CDA for a pre-requisite understanding of the context in which the UCUM code system is used in CDA documents.

The UCUM code system is used in CDA documents for units […]

Physical quantities in CDA

February 6th, 2014|0 Comments

There are a variety of places in a CDA document where physical quantities need to be represented. In this context, “physical quantities” refers to things that are measured (height, width, temperature, etc.) or things that […]

Codes and code systems

February 6th, 2014|0 Comments

Codes are used throughout CDA. There are clinical codes (medication codes, procedure codes, lab test codes, etc.) and administrative codes (gender, language, zip code, etc.).

While a human reader can match up a wide range of […]

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