Composition (63)

#	Name	Source	Ver	Description
1	ADI Composition Header	hl7.fhir.us.pacio-adi#current	R4	This abstract profile defines constraints that represent common administrative and demographic concepts for advance directives information used in US Realm clinical documents.
2	ADI Personal Advance Care Plan Composition	hl7.fhir.us.pacio-adi#current	R4	This profile encompasses information that makes up the author’s advance care information plan.
3	ADI Personal Advance Care Plan Composition	hl7.fhir.us.pacio-adi#current	R4	This profile encompasses information that makes up the author’s advance care information plan.
4	Breast Imaging Composition	hl7.fhir.us.breast-radiology#current	R4	Composition instance for the Breast Imaging FHIR Document.
5	BSeR Referral Feedback Composition	hl7.fhir.us.bser#current	R4	This Composition profile represents the clical feedback included in the referral feedback document.
6	BSeR Referral Request Composition	hl7.fhir.us.bser#current	R4	This Composition profile represents the clical supporting information included in the referral request document.
7	Care Plan	hl7.fhir.us.ccda#current	R4	CARE PLAN FRAMEWORK: A Care Plan (including Home Health Plan of Care (HHPoC)) is a consensus-driven dynamic plan that represents a patient and Care Team Members prioritized concerns, goals, and planned interventions. It serves as a blueprint shared by all Care Team Members (including the patient, their caregivers and providers), to guide the patients care. A Care Plan integrates multiple interventions proposed by multiple providers and disciplines for multiple conditions. A Care Plan represents one or more Plan(s) of Care and serves to reconcile and resolve conflicts between the various Plans of Care developed for a specific patient by different providers. While both a plan of care and a care plan include the patient's life goals and require Care Team Members (including patients) to prioritize goals and interventions, the reconciliation process becomes more complex as the number of plans of care increases. The Care Plan also serves to enable longitudinal coordination of care. The Care Plan represents an instance of this dynamic Care Plan at a point in time. The composition itself is NOT dynamic. Key differentiators between a Care Plan profile and CCD profile (another snapshot in time document): * Requires relationships between various concepts: * Health Concerns * Interventions * Goals * Outcomes * Provides the ability to identify patient and provider priorities with each act * Provides a header participant to indicate occurrences of Care Plan review
8	Composition - ADE Hyperglycemia	hl7.fhir.us.nhsn-ade#current	R4	This profile supports the electronic submission of adverse drug event (ADE) data relating to hyperglycemia to the National Healthcare Safety Network (NHSN).
9	Composition - ADE Hypoglycemia	hl7.fhir.us.nhsn-ade#current	R4	This profile supports the electronic submission of adverse drug event (ADE) data relating to hypoglycemia to the National Healthcare Safety Network (NHSN).
10	Composition - Coded Cause of Fetal Death	hl7.fhir.us.bfdr#current	R4	This Composition profile communicates coded cause of fetal death information to appropriate jurisdictional Vital Records Offices.
11	Composition - Coded Race and Ethnicity	hl7.fhir.us.bfdr#current	R4	This Composition profile communicates coded race and ethnicity information to the appropriate jurisdictional Vital Records Office.
12	Composition - Inpatient Medication Administration	hl7.fhir.us.nhsn-med-admin#1.0.0	R4	This profile supports the electronic submission of line-level medication administration data to the National Healthcare Safety Network (NHSN).
13	Composition - Jurisdiction Fetal Death Report	hl7.fhir.us.bfdr#current	R4	This Composition profile contains information of a fetal death and the creation of a jurisdictional file to be recorded and communicated to the national statistics agency.
14	Composition - Jurisdiction Live Birth Report	hl7.fhir.us.bfdr#current	R4	This Composition profile contains information of a live birth and the issuance of a Birth Certificate to be recorded and communicated to the national statistics agency.
15	Composition - MDI to EDRS	hl7.fhir.us.vrsandbox#current	R4	This Composition profile represents data exchanged between an MDI CMS and an EDRS.
16	Composition - MDI to EDRS	hl7.fhir.us.mdi#current	R4	This Composition profile represents data exchanged between an MDI CMS and an EDRS.
17	Composition - Provider Fetal Death Report	hl7.fhir.us.bfdr#current	R4	This Composition profile contains constraints to address the use case describing the need for fetal death information to be recorded and communicated to the jurisdictional Vital Records Office.
18	Composition - Provider Live Birth Report	hl7.fhir.us.bfdr#current	R4	This Composition profile defines constraints to address the use case in which information for live birth information is recorded and communicated to the jurisdictional Vital Records Office.
19	Composition-IEHR	fhir.uv.crossborderdataexchange#current	R4
20	CompositionIPS-IEHR	fhir.uv.crossborderdataexchange#current	R4
21	Consultation Note	hl7.fhir.us.ccda#current	R4	The Consultation Note is generated by a request from a clinician for an opinion or advice from another clinician. Consultations may involve face-to-face time with the patient or may fall under the auspices of telemedicine visits. Consultations may occur while the patient is inpatient or ambulatory. The Consultation Note should also be used to summarize an Emergency Room or Urgent Care encounter. A Consultation Note includes the reason for the referral, history of present illness, physical examination, and decision-making components (Assessment and Plan).
22	Continuity of Care Document	hl7.fhir.us.ccda#current	R4	This profile was originally based on the Continuity of Care Document (CCD) Release 1.1 which itself was derived from HITSP C32 and CCD Release 1.0. The Continuity of Care Document (CCD) profile represents a core data set of the most relevant administrative, demographic, and clinical information facts about a patient's healthcare, covering one or more healthcare encounters. It provides a means for one healthcare practitioner, system, or setting to aggregate all of the pertinent data about a patient and forward it to another to support the continuity of care. The primary use case for the CCD is to provide a snapshot in time containing the germane clinical, demographic, and administrative data for a specific patient. The key characteristic of a CCD is that the Composition.event.code is constrained to "PCPR". This means it does not function to report new services associated with performing care. It reports on care that has already been provided. The CCD provides a historical tally of the care over a range of time and is not a record of new services delivered. More specific use cases, such as a Discharge Summary, Transfer Summary, Referral Note, Consultation Note, or Progress Note, are available as alternative profiles.
23	Death Certificate	hl7.fhir.us.vrdr#current	R4	The body of the death certificate document (Composition).
24	Death Certificate	hl7.fhir.us.vrsandbox#current	R4	The body of the death certificate document (Composition).
25	Dental Consult Note	hl7.fhir.us.dental-data-exchange#current	R4	This Profile defines the Dental Consult Note profile. It contains the textual information regarding what was observed and performed by a general dentist or dental specialist in response to a dental referral as well as references to supplemental dental profiles for that referral. This Consult Note is linked to its Referral via the In-Fulfillment-Of extension reference to ServiceRequest.
26	Dental Referral Note	hl7.fhir.us.dental-data-exchange#current	R4	This profile defines the Dental Referral Note. It contains the textual information regarding a referral to a general dentist or dental specialist as well as references to supplemental dental profiles for the referral. This is not intended to be the mechanism for initiating the referral itself, but rather is a secondary communication that provides additional patient information to support a referral that already has been initated through some other channel.
27	DEQM Gaps In Care Composition Profile	hl7.fhir.us.davinci-deqm#current	R4	The DEQM Gaps In Care Composition Profile defines a document composition consisting of one or more indivdiual MeasureReport(s). Each section of this composition corresponds to an indivdiual MeasureReport for a specific measure. The subject of each individual MeasureReport referenced by the section must be for the same individual specified in the subject of this Composition.
28	Diagnostic Imaging Report	hl7.fhir.us.ccda#current	R4	A Diagnostic Imaging Report (DIR) is a document that contains a consulting specialist's interpretation of image data. It conveys the interpretation to the referring (ordering) physician and becomes part of the patient's medical record. It is for use in Radiology, Endoscopy, Cardiology, and other imaging specialties. Note: this document type overlaps with the FHIR DiagnosticReport resource. Most use cases will want to use the specific resource type, but this document type is still useful for CDA to FHIR conversion and other such use cases.
29	Discharge Summary	hl7.fhir.us.ccda#current	R4	The Discharge Summary is a document which synopsizes a patient's admission to a hospital, LTPAC provider, or other setting. It provides information for the continuation of care following discharge. The Joint Commission requires the following information to be included in the Discharge Summary (http://www.jointcommission.org/): The reason for hospitalization (the admission) The procedures performed, as applicable The care, treatment, and services provided The patients condition and disposition at discharge Information provided to the patient and family Provisions for follow-up care The best practice for a Discharge Summary is to include the discharge disposition in the display of the header.
30	eCTD Batch Analyses Composition	hl7.fhir.us.pq-cmc#current	R5	The fields needed to represent the Batch Analyses to be included under the 3.2.P.5.4 and 3.2.S.4.4 eCTD headings. References Sponsor Organization and Batch Analysis
31	eCTD Batch Formula	hl7.fhir.us.pq-cmc#current	R5	The fields needed to represent the Product Batch Formula to be included under the eCTD. References Sponsor Organization and Batch Formula
32	eCTD Product Characterization of Impurities Composition	hl7.fhir.us.pq-cmc#current	R5	The fields needed to represent the Product Characterization of Impurities in a to be included under the eCTD. References Sponsor Organization and Product Characterization of Impurities
33	eCTD Product Container Closure System Composition	hl7.fhir.us.pq-cmc#current	R5	The fields needed to represent the Product Container Closure Systems to be included under the eCTD p.7.0
34	eCTD Product Description and Composition	hl7.fhir.us.pq-cmc#current	R5	The fields needed to represent the Product Description, Container Closure and Composition of the Drug Product to be included under the 3.2.P.1.0 heading of the eCTD. References Sponsor Organization, Drug Product Description, and Product Container Closure System.
35	eCTD Specification Composition	hl7.fhir.us.pq-cmc#current	R5	The fields needed to represent the Quality Specifications to be included under the eCTD 3.2.P.5.1, 3.2.S.4.1, and 3.2.P.4.1 headings.. References Sponsor Organization and Quality Specification.
36	eCTD Stability Data Composition	hl7.fhir.us.pq-cmc#current	R5	The fields needed to represent the Stability Data to be included under the 3.2.P.8.3 , 3.2.S.7.3 and 3.2.P.4.5 eCTD headings. References Sponsor Organization and Stability Study.
37	eCTD Stability Summary and Conclusion Composition	hl7.fhir.us.pq-cmc#current	R5	The fields needed to represent the Stability Summary and Conclusion to be included in the 3.2.P.8.3 and 3.2.S.7.3 eCTD headings. References Sponsor Organization and Stability Study.
38	eCTD Substance Characterization	hl7.fhir.us.pq-cmc#current	R5	The fields needed to represent the Substance Structure and Impurities to be included under the 3.2.S.3.0 heading of the eCTD. References Sponsor Organization, Drug Substance Structure, and Drug Substance Impurities
39	eCTD Substance Container Closure System Composition	hl7.fhir.us.pq-cmc#current	R5	The fields needed to represent the Substance Container Closure Systems to be included under the eCTD 3.2.S.6.0 eCTD heading. References Sponsor Organization and Substance Container Closure
40	eCTD Substance Control of Materials Composition	hl7.fhir.us.pq-cmc#current	R5	The fields needed to represent the Substance Control of Materials in a to be included under the eCTD. References Sponsor Organization and Drug Substance Materials.
41	eCTD Substance General Information	hl7.fhir.us.pq-cmc#current	R5	The fields needed to represent the Substance Nomenclature and Structure to be included under the 3.2.S.1.0 heading of the eCTD. References Sponsor Organization.
42	Electronic Initial Case Report Composition	hl7.fhir.us.ecr#current	R4	This Composition profile represents an electronic initial case report (eICR). It is based on and further constrains the US Public Health Composition.
43	Health Care Survey Report Composition	hl7.fhir.us.health-care-surveys-reporting#current	R4	This Composition profile is used to organize the healthcare survey report content.
44	History and Physical	hl7.fhir.us.ccda#current	R4	A History and Physical (H&P) note is a medical report that documents the current and past conditions of the patient. It contains essential information that helps determine an individual's health status. The first portion of the report is a current collection of organized information unique to an individual. This is typically supplied by the patient or the caregiver, concerning the current medical problem or the reason for the patient encounter. This information is followed by a description of any past or ongoing medical issues, including current medications and allergies. Information is also obtained about the patient's lifestyle, habits, and diseases among family members. The next portion of the report contains information obtained by physically examining the patient and gathering diagnostic information in the form of laboratory tests, imaging, or other diagnostic procedures. The report ends with the clinician's assessment of the patient's situation and the intended plan to address those issues. A History and Physical Examination is required upon hospital admission as well as before operative procedures. An initial evaluation in an ambulatory setting is often documented in the form of an H&P note.
45	HospitalDischargeReport-IEHR	fhir.uv.crossborderdataexchange#current	R4
46	ICSR Composition	hl7.fhir.us.icsr-ae-reporting#current	R4	The fields needed to represent the document metadata of a ICSR Report.
47	Occupational Data For Health	hl7.fhir.us.odh#current	R4	This Composition covers information about a patient’s work, including some voluntary work, or a patient’s household members’ work. ODH is designed for the social history section of a medical record, to facilitate clinical care in multiple disciplines and delivery environments. ODH can be used for clinical decision support, population health activities and value-based care, and public health reporting.
48	Operative Note	hl7.fhir.us.ccda#current	R4	The Operative Note is a frequently used type of procedure note with specific requirements set forth by regulatory agencies. The Operative Note is created immediately following a surgical or other high-risk procedure. It records the pre- and post-surgical diagnosis, pertinent events of the procedure, as well as the condition of the patient following the procedure. The report should be sufficiently detailed to support the diagnoses, justify the treatment, document the course of the procedure, and provide continuity of care.
49	PACIO ADI Header	hl7.fhir.us.pacio-adi#current	R4	This abstract profile defines constraints that represent common administrative and demographic concepts for advance directives information used in US Realm clinical documents.
50	PCDE Coverage Transition Composition Profile	hl7.fhir.us.davinci-pcde#current	R4	Constraints on Composition to define the root and table of contents for a Coverage Transition Document
51	PhCP Composition	hl7.fhir.us.phcp#1.0.0	R4	The Pharmacist Care Plan standardizes the information gathered and developed through the process of medication planning and management in community, hospital, and long term post-acute care (LTPAC) settings. It allows exchange of information between providers of care to optimize medication-related decision support and patient adherence to medication regimens both within a healthcare setting and when a patient moves between healthcare settings. Standardization of information used in this form will promote interoperability; support a comprehensive, multi-discipline longitudinal care plan; and create information suitable for reuse in quality measurement, public health reporting, research, and for reimbursement. In assessment of and consultation with the patient, the Pharmacist Care Plan focuses on: * Maximizing the effectiveness of medications ordered and currently used * Identifying and addressing barriers to successful implementation of the therapy regimen * Assuring patient understanding of the reasons for and use of the medication and the goals of therapy * Resolving conflicting orders and plans These activities help the patient achieve the best possible outcomes of treatment and an enhanced sense of wellbeing.
52	Procedure Note	hl7.fhir.us.ccda#current	R4	A Procedure Note encompasses many types of non-operative procedures including interventional cardiology, gastrointestinal endoscopy, osteopathic manipulation, and many other specialty fields. Procedure Notes are differentiated from Operative Notes because they do not involve incision or excision as the primary act. The Procedure Note is created immediately following a non-operative procedure. It records the indications for the procedure and, when applicable, postprocedure diagnosis, pertinent events of the procedure, and the patients tolerance for the procedure. It should be detailed enough to justify the procedure, describe the course of the procedure, and provide continuity of care.
53	ProductSubmissionDocument	hl7.fhir.us.spl#current	R4B	A profile that represents a document that is required for Product Submission to the FDA.
54	Progress Note	hl7.fhir.us.ccda#current	R4	This profile represents a patient's clinical status during a hospitalization, outpatient visit, treatment with a LTPAC provider, or other healthcare encounter. Taber's medical dictionary defines a Progress Note as An ongoing record of a patient's illness and treatment. Physicians, nurses, consultants, and therapists record their notes concerning the progress or lack of progress made by the patient between the time of the previous note and the most recent note. Mosby's medical dictionary defines a Progress Note as Notes made by a nurse, physician, social worker, physical therapist, and other health care professionals that describe the patient's condition and the treatment given or planned. A Progress Note is not a re-evaluation note. A Progress Note is not intended to be a Progress Report for Medicare. Medicare B Section 1833(e) defines the requirements of a Medicare Progress Report.
55	Referral Note	hl7.fhir.us.ccda#current	R4	A Referral Note communicates pertinent information from a provider who is requesting services of another provider of clinical or non-clinical services. The information in this document includes the reason for the referral and additional information that would augment decision making and care delivery. Examples of referral situations are: * When a patient is referred from a family physician to a cardiologist for cardiac evaluation. * When patient is sent by a cardiologist to an emergency department for angina. * When a patient is referred by a nurse practitioner to an audiologist for hearing screening. * When a patient is referred by a hospitalist to social services.
56	RR Composition	hl7.fhir.us.ecr#current	R4	This Composition profile represents the Reportability Response that is created in response to an electronic Initial Case Report Composition.
57	Transfer Summary	hl7.fhir.us.ccda#current	R4	This profile describes constraints for a Transfer Summary. The Transfer Summary standardizes critical information for exchange of information between providers of care when a patient moves between health care settings. Standardization of information used in this form will promote interoperability; create information suitable for reuse in quality measurement, public health, research, and for reimbursement.
58	US Public Health Composition	hl7.fhir.us.ecr#current	R4	This Composition profile represents a public health composition.
59	US Public Health Composition	hl7.fhir.us.ph-library#current	R4	This Composition profile represents a public health composition.
60	US Public Health Composition	hl7.fhir.us.ph-library#current	R4	This Composition profile represents a public health composition.
61	US Realm Header	hl7.fhir.us.ccda#current	R4	This profile defines constraints that represent common administrative and demographic concepts for US Realm clinical documents. Further specification, such as type, are provided in document profiles that conform to this profile.
62	VetComposition	fhir.zentricx-grupo-b#current	R4
63	VisitReport-IEHR	fhir.uv.crossborderdataexchange#current	R4

Composition

Composition.confidentiality

C D

Composition.meta

Composition.meta.profile

Composition.implicitRules

Composition.language

Composition.text

Composition.contained

Composition.extension

S C (8)

S C (2)

S C (3)

S C (5)

S C D (2)

S D

S C (5)

S C (2)

S C (4)

S C D (3)

S C (10)

S C (11)

S C (2)

S C D

S C D (3)

S C (8)

Composition.extension.value[x]

Composition.extension.url

Composition.modifierExtension

Composition.url

Composition.identifier

C D

Composition.identifier.assigner

Composition.identifier.period

Composition.identifier.type

Composition.identifier.use

Composition.identifier.value

Composition.identifier.system

C F

Composition.version

Composition.status

B M

Composition.type

B M

F D

B M

F D

B M

F D

B M

F D

B M

Composition.type.text

Composition.type.coding

S C D (2)

Composition.type.coding.userSelected

Composition.type.coding.display

C F

Composition.type.coding.version

Composition.type.coding.code

C F

Composition.type.coding.system

C F

Composition.category

C F

Composition.category.text

Composition.category.coding

Composition.category.coding.userSelected

Composition.category.coding.display

C F

Composition.category.coding.code

C F

Composition.category.coding.version

Composition.category.coding.system

C F

Composition.subject

C D

Composition.subject.display

Composition.subject.identifier

Composition.subject.type

Composition.subject.reference

Composition.encounter

C D

Composition.encounter.extension

Composition.date

Composition.useContext

Composition.author

C D

Composition.author.display

Composition.author.identifier

Composition.author.type

Composition.author.reference

Composition.author.extension

S C (2)

Composition.name

Composition.title

Composition.note

Composition.attester

C D

S C (4)

Composition.attester.extension

S C (2)

Composition.attester.modifierExtension

Composition.attester.mode

F (3)

C F (3)

Composition.attester.time

Composition.attester.party

C (3)

Composition.attester.party.display

Composition.attester.party.identifier

Composition.attester.party.type

Composition.attester.party.reference

Composition.custodian

Composition.custodian.display

Composition.custodian.identifier

Composition.custodian.type

Composition.custodian.reference

Composition.relatesTo

S C D (3)

Composition.relatesTo.target[x]

D (2)

Composition.relatesTo.code

F (2)

Composition.event

C D

Composition.event.code

C F

C B M

Composition.event.extension

Composition.event.modifierExtension

Composition.event.period

Composition.event.period.end

Composition.event.period.start

Composition.event.detail

S (2)

Composition.section

S C I D (8)

S C I (7)

S C D (8)

S C (8)

S C D (5)

S C D (6)

S C D (2)

C D

S C D (5)

S C D (7)

S C D (8)

S C D (7)

S C D (26)

S C D (20)

S C (6)

S C D (8)

S C (8)

S C D (11)

S C D (28)

S C D (3)

C D

S C D (4)

S C D (3)

C D

S C D (3)

S C D (19)

S C D (18)

S C (22)

S (14)

S C (15)

C D

S C (17)

S C (3)

S C D (3)

S C (29)

S C (3)

S C D (17)

S C D (26)

S C D (4)

S C D (27)

S C D (14)

S (20)

Composition.section.mode

C (13)

Composition.section.extension

S C (2)

S (7)

S C (2)

S C (7)

S C D (6)

Composition.section.modifierExtension

Composition.section.title

C (7)

C (6)

F (7)

C (4)

C (5)

C (4)

C (25)

C (19)

C (2)

C (10)

C (27)

C (2)

C (21)

C F (15)

C (16)

C (3)

C (2)

C (28)

C (2)

C (16)

C (25)

C (26)

C F (13)

Composition.section.code

C F (7)

C F (6)

C F (7)

C F (8)

C F (4)

C F (5)

C F D

C F (4)

C F D (6)

C F D (7)

C F D (6)

C F (25)

C F (19)

C F (6)

C F (3)

C F (10)

C F (27)

C F (2)

C F B M (4)

C F (2)

C F

C F (2)

C F D (18)

C F D (17)

C F (21)

F (13)

C F (15)

C F (16)

C F B M (2)

C F (2)

C F (28)

C F B M (3)

C F (16)

C F (25)

C F (3)

C F (26)

C (13)

F (19)

Composition.section.code.text

Composition.section.author

C (13)

Composition.section.focus

C D

C D (4)

C (13)

Composition.section.text

C (4)

(5)

C (4)

D (3)

C D (4)

C (25)

C (19)

C (10)

C (27)

C D (18)

C D (17)

C (21)

C (4)

C (16)

C (2)

C (28)

C (2)

C (16)

C (25)

C D (2)

C (26)

C (13)

Composition.section.orderedBy

C (13)

Composition.section.entry

(6)

C D (7)

S C (25)

S C (36)

S (8)

S C (13)

S C (11)

S C D (3)

S C (9)

S C D (39)

S C D (54)

S C D (18)

S C D (31)

S C D (42)

S (36)

S (38)

S C D (43)

S C (7)

S C (8)

S (4)

S (34)

C (3)

C (4)

C (3)

C (2)

C (3)

S C D (41)

S C (31)

S (26)

S (28)

C (15)

S C D (6)

S (14)

C (2)

S (4)

S (26)

C (3)

S (20)

S (42)

S C D (5)

S (46)

Composition.section.entry.type

C (13)

Composition.section.entry.reference

C (13)

Composition.section.entry.display

C (13)

Composition.section.entry.identifier

C (13)

Composition.section.entry.extension

S C D (16)

Composition.section.emptyReason

B M

D (4)

(4)

C (13)

Composition.section.section

S C (2)

S C (5)

C (3)

C (13)

Composition.section.section.extension

S C (7)

Composition.section.section.section

C (3)

Composition.section.section.text

C (3)

Composition.section.section.title

(3)

Composition.section.section.entry

S C (5)

C (3)

Composition.section.section.focus

Composition.section.section.code

C F

C F B M (3)

C B M

S: There is slicing defined in the element(s)
C: There is cardinality erstrictions defined in the element(s)
I: There is invariants defined in the element(s)
F: There is a fixed or pattern value defined in the element(s)
D: There is document provided in the element(s)
B: There is terminology bindings defined in the element(s)
M: At least one of the element(s) has must-support = true
(N): The number of elements if > 1

Produced 08 Sep 2023