|DotNet Namespace HL7Connect.Ccd|
The CCD Builder Module
|ContentBuilder||Builds a content part|
|ParagraphBuilder||Builds a paragraph|
|ListBuilder||Builds a List|
|TableRowBuilder||Builds a Row in a Table|
|TableBuilder||Builds a Table|
|NarrativeBuilder||Builds a Narrative Block|
|PurposeStatement||a statement of purpose|
|AuthorizationActivity||a statement of CoverageDetail|
|PolicyActivity||A policy activity represents the policy or program providing the coverage. The person for whom payment is being provided (i.e. the patient) is the covered party. The subscriber of the policy or program is represented as a participant that is the holder the coverage. The payer is represented as the performer of the policy activity.|
|CoverageActivity||Insurance and authorization acts are represented as Acts within the section. These acts are grouped together under a single coverage activity, which serves to order the payment sources. A coverage activity contains one or more policy activities, each of which contains zero or more authorization activities.|
|EncounterLocation||a statement of CoverageDetail|
|EncounterActivity||a statement of Coverage|
|ResultOrganizer||a statement of Coverage|
|ProblemAct||a statement of a problem|
|FamilyHistoryRelative||Describes the Relative that a family history entry is about
The Age of the patient may be inferred from these details, but the age of the patient associated with any particular observation may also be reported directly (i.e Uncle Joe was born 1955, passed away when 53 years old, but had a heart attack in his 40s)
|FamilyHistoryObservation||An observation of a problem in family history
May be cause of death or not. May have a problem observation
Other observations are available through CDAEntry
|FamilyHistoryEntry||Family History Observations about a single Relative.
|Builder||The CDA library provides a general model for CDA documents. CCD is a profile
on the general CDA model which makes many restrictions on the content of the
CDA document, and also provides business names that help to map the somewhat
abstract names of the CDA document to the CCD context of use.
The CCD builder provides an object API over the top of an underlying CDA that make it easy to build a CCD document by filling out all the fixed values, and expressing the API in terms of the business names defined in the CCD specification.
The API is intentionally simplified, but the underlying CDA classes can be accessed through the API if more content is desired that is not fixed by the CCD specification.
The CCD builder is also useful when reading CCD documents, as it surfaces the existing document through the CCD API.
The CCD Builder is access through the events, by using the UseCCD() routine.
|Factory||Used to build new instances of CCD related classes|