Clinical Document Architecture
E755534
Clinical Document Architecture is an HL7 standard that defines the structure and semantics of electronic clinical documents to enable consistent exchange and interoperability in healthcare.
All labels observed (4)
| Label | Occurrences |
|---|---|
| Clinical Document Architecture canonical | 3 |
| HL7 CDA | 2 |
| C-CDA | 1 |
| HL7 CDA (when used for document content) | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T8757950 — resolving that mention is where its identity was fixed. The disambiguator weighed these candidate entities and picked the highlighted one (or “None”, minting a new entity). This is how homonymy is resolved: the same surface form can point to different entities.
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Clinical Document Architecture Context triple: [HL7 International, developsStandard, Clinical Document Architecture]
-
A.
Documentation and Its Facets
"Documentation and Its Facets" is a seminal work by library science pioneer S. R. Ranganathan that systematically explores the theory, practice, and organization of documentation and information services.
-
B.
CDSS
CDSS is the state agency in California responsible for overseeing social services programs such as welfare, child welfare, and community care licensing.
-
C.
ClinicalKey
ClinicalKey is a comprehensive clinical search engine and decision-support platform for healthcare professionals, providing access to medical textbooks, journals, guidelines, and multimedia content.
-
D.
Case Management/Electronic Case Files
Case Management/Electronic Case Files (CM/ECF) is the federal judiciary’s nationwide electronic filing and case management system that allows courts, attorneys, and the public to access and manage case documents online.
-
E.
FHIR DocumentReference
FHIR DocumentReference is a FHIR resource that represents metadata about a clinical or administrative document, including its type, status, content, and context, enabling standardized discovery and retrieval of documents across health systems.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Clinical Document Architecture Target entity description: Clinical Document Architecture is an HL7 standard that defines the structure and semantics of electronic clinical documents to enable consistent exchange and interoperability in healthcare.
-
A.
Documentation and Its Facets
"Documentation and Its Facets" is a seminal work by library science pioneer S. R. Ranganathan that systematically explores the theory, practice, and organization of documentation and information services.
-
B.
CDSS
CDSS is the state agency in California responsible for overseeing social services programs such as welfare, child welfare, and community care licensing.
-
C.
ClinicalKey
ClinicalKey is a comprehensive clinical search engine and decision-support platform for healthcare professionals, providing access to medical textbooks, journals, guidelines, and multimedia content.
-
D.
Case Management/Electronic Case Files
Case Management/Electronic Case Files (CM/ECF) is the federal judiciary’s nationwide electronic filing and case management system that allows courts, attorneys, and the public to access and manage case documents online.
-
E.
FHIR DocumentReference
FHIR DocumentReference is a FHIR resource that represents metadata about a clinical or administrative document, including its type, status, content, and context, enabling standardized discovery and retrieval of documents across health systems.
- F. None of above. chosen
Statements (47)
| Predicate | Object |
|---|---|
| instanceOf |
HL7 standard
ⓘ
clinical document standard ⓘ healthcare interoperability standard ⓘ |
| abbreviation | CDA ⓘ |
| abbreviationOf |
HL7 CDA
ⓘ
linked to:
HL7 Clinical Document Architecture
|
| appliesTo | clinical documents ⓘ |
| basedOn |
HL7 Reference Information Model
ⓘ
linked to:
HL7 v3 Reference Information Model
|
| category | health informatics standard ⓘ |
| constrains | XML-based document structure ⓘ |
| defines |
semantics of electronic clinical documents
ⓘ
structure of electronic clinical documents ⓘ |
| developedBy |
HL7
ⓘ
linked to:
HL7 International
Health Level Seven International ⓘ
linked to:
HL7 International
|
| domain |
electronic health records
ⓘ
healthcare information technology ⓘ |
| enables |
reuse of clinical information across systems
ⓘ
semantic interoperability of clinical documents ⓘ |
| geographicScope | international ⓘ |
| governingBody | HL7 Structured Documents Work Group ⓘ |
| hasCharacteristic |
contextual
ⓘ
document-centric ⓘ machine-processable semantics ⓘ persistent ⓘ wholly interpretable by humans ⓘ |
| hasConstraintMechanism |
implementation guides
ⓘ
templates ⓘ |
| hasVersion |
CDA Release 1.0
ⓘ
linked to:
CDA
CDA Release 2.0 ⓘ
linked to:
CDA
|
| purpose |
enable consistent exchange of clinical documents
ⓘ
support interoperability in healthcare ⓘ |
| relatedStandard |
Continuity of Care Document
ⓘ
linked to:
CCD (Continuity of Care Document)
HL7 FHIR ⓘ
linked to:
FHIR
HL7 V3 ⓘ
linked to:
HL7 standards
|
| releaseDate |
CDA Release 1.0 2000
ⓘ
linked to:
CDA
CDA Release 2.0 2005 ⓘ
linked to:
CDA
|
| scope | exchange of clinical documents between healthcare systems ⓘ |
| serializationFormat | XML ⓘ |
| supports |
document-level metadata
ⓘ
entry-level clinical statements ⓘ human-readable clinical documents ⓘ machine-processable clinical documents ⓘ section-level structure ⓘ |
| usedFor |
consultation notes
ⓘ
continuity of care documents ⓘ discharge summaries ⓘ imaging reports ⓘ laboratory reports ⓘ |
How these facts were elicited
The pipeline generated the facts above by prompting gpt-5.1 with this entity's name + description and the instruction below.
Instruction
You are a knowledge base construction expert. Given a subject entity and a description of it, return factual statements that you know for the subject as a JSON list of dictionaries(triples), where keys must be "subject", "predicate" and "object". The number of facts may be very high, between 25 to 50 or more, for very popular subjects. For less popular subjects, the number of facts can be very low, like 5 or 10. # Requirements - If you don't know the subject at all, return an empty list. - If the subject is not a named entity, return an empty list. - Include at least one triple where predicate is "instanceOf". - Do not get too wordy. - Separate several objects into multiple triples with one object.
Input
Subject: Clinical Document Architecture Description of subject: Clinical Document Architecture is an HL7 standard that defines the structure and semantics of electronic clinical documents to enable consistent exchange and interoperability in healthcare.
Referenced by (7)
Full triples — surface form annotated when it differs from this entity's canonical label.
linked to: Clinical Document Architecture
linked to: Clinical Document Architecture
linked to: Clinical Document Architecture