Composition (180)

#NameSourceVerDescription
1[Profile] - Structure Composition for Medication Recordihe-fhir-pharm-medicationrecord#currentR5The profile for how to organize the information in a medication Record
2ADHA Advance Care Directive Custodian Record Compositionau.digitalhealth.r4#currentR4The purpose of this profile is to define a representation of an Advance Care Directive Custodian Record document for a patient for the electronic exchange of health information between individuals, healthcare providers, and the My Health Record system infrastructure in Australia. A composition is a set of resources composed into a single coherent clinical statement that may have clinical attestation.
3ADHA Advance Care Planning Compositionau.digitalhealth.r4#currentR4The purpose of this profile is to define a representation of an Advance Care Planning document that includes an attached Advance Care Plan for a patient for the electronic exchange of health information between individuals, healthcare providers, and the My Health Record system infrastructure in Australia. A composition is a set of resources composed into a single coherent clinical statement that may have clinical attestation.
4ADHA Aged Care Transfer Summary Compositionau.digitalhealth.r4#currentR4The purpose of this profile is to define a representation of an Aged Care Transfer Summary for a patient for the electronic exchange of health information between individuals, healthcare providers, and the My Health Record system infrastructure in Australia. A transfer summary includes critical information for exchange of information between providers of care when a patient moves between health care settings. A composition is a set of resources composed into a single coherent clinical statement that may have clinical attestation.
5ADHA Continuity of Care Summary Compositionau.digitalhealth.r4#currentR4The purpose of this profile is to define a representation of an Continuity of Care Summary document for a patient for the electronic exchange of health information between individuals, healthcare providers, and the My Health Record system infrastructure in Australia. This profile standardises the core, common or critical information for exchange of information between healthcare providers, and individual, to support continuity of care across encounters and healthcare settings. Specific use cases are supported by defined profiles for those use cases such as Shared Health Summary, Event Summary, Discharge Summary, Transfer Summary, Referral; where available the most specific applicable profile should be used. A composition is a set of resources composed into a single coherent clinical statement that may have clinical attestation.
6ADHA Core Compositionau.digitalhealth.r4#currentR4The purpose of this profile is to provide a core representation of a composition for the electronic exchange of health information between individuals, healthcare providers, and the My Health Record system infrastructure in Australia. A composition is a set of resources composed into a single coherent clinical statement.
7ADHA Diagnostic Report Compositionau.digitalhealth.r4#currentR4The purpose of this profile is to define a representation of a Diagnostic Report document for the electronic exchange of health information between individuals, healthcare providers, and the My Health Record system infrastructure in Australia. A composition is a set of resources composed into a single coherent clinical statement that may have clinical attestation. This profile is intended to be capable of supporting reporting for specialist and other diagnostic disciplines, pathology disciplines, and imaging disciplines.
8ADHA Discharge Summary Compositionau.digitalhealth.r4#currentR4The purpose of this profile is to define a representation of an Discharge Summary document for a patient for the electronic exchange of health information between individuals, healthcare providers, and the My Health Record system infrastructure in Australia. This profile standardises the core, common or critical information for exchange of information between healthcare providers, and individual, to support continuity of care following discharge. A composition is a set of resources composed into a single coherent clinical statement that may have clinical attestation.
9ADHA Document Compositionau.digitalhealth.r4#currentR4The purpose of this profile is to provide a document composition for the electronic exchange of health information between individuals, healthcare providers, and the My Health Record system infrastructure in Australia. A composition is a set of resources composed into a single coherent clinical statement that may have clinical attestation.
10ADHA Event Summary Compositionau.digitalhealth.r4#currentR4The purpose of this profile is to define a representation of a Event Summary document for a patient for the electronic exchange of health information between individuals, healthcare providers, and the My Health Record system infrastructure in Australia. A composition is a set of resources composed into a single coherent clinical statement that may have clinical attestation.
11ADHA Event Summary Compositionau.digitalhealth.r4#currentR4The purpose of this profile is to define a representation of a Event Summary document for a patient for the electronic exchange of health information between individuals, healthcare providers, and the My Health Record system infrastructure in Australia. A composition is a set of resources composed into a single coherent clinical statement that may have clinical attestation.
12ADHA Event Summary Mixed Narrative and Structureau.digitalhealth.r4#currentR4The purpose of this profile is to define a representation of a mixed narrative and structured data Event Summary document for a patient for the electronic exchange of health information between individuals, healthcare providers, and the My Health Record system infrastructure in Australia. A composition is a set of resources composed into a single coherent clinical statement that may have clinical attestation.
13ADHA Event Summary Narrativeau.digitalhealth.r4#currentR4The purpose of this profile is to define a representation of a narrative only Event Summary document for a patient for the electronic exchange of health information between individuals, healthcare providers, and the My Health Record system infrastructure in Australia. A composition is a set of resources composed into a single coherent clinical statement that may have clinical attestation.
14ADHA Medicare Overview Compositionau.digitalhealth.r4#currentR4The purpose of this profile is to define a representation of a Medicare Overview document for an individual for the electronic exchange of health information between individuals, healthcare providers, and the My Health Record system infrastructure in Australia. A composition is a set of resources composed into a single coherent clinical statement that may have clinical attestation.
15ADHA National Cancer Screening Program Participation Viewau.digitalhealth.r4#currentR4The purpose of this profile is to define a representation of a National Cancer Screening Program Participation View that describes an individual's participation in one or more national cancer screening programs at a point in time for the electronic exchange of health information between individuals, healthcare providers, and the My Health Record system infrastructure in Australia.
16ADHA Personal Health Notes Compositionau.digitalhealth.r4#currentR4The purpose of this profile is to define a representation of a Personal Health Notes document for a patient for the electronic exchange of health information between individuals, healthcare providers, and the My Health Record system infrastructure in Australia. A composition is a set of resources composed into a single coherent clinical statement that may have clinical attestation.
17ADHA Personal Health Summary Compositionau.digitalhealth.r4#currentR4The purpose of this profile is to define a representation of a Personal Health Summary document for a patient for the electronic exchange of health information between individuals, healthcare providers, and the My Health Record system infrastructure in Australia. A composition is a set of resources composed into a single coherent clinical statement that may have clinical attestation.
18ADHA Personal Health Summary Compositionau.digitalhealth.r4#currentR4The purpose of this profile is to define a representation of a Personal Health Summary document for a patient for the electronic exchange of health information between individuals, healthcare providers, and the My Health Record system infrastructure in Australia. A composition is a set of resources composed into a single coherent clinical statement that may have clinical attestation.
19ADHA Personal Observations Compositionau.digitalhealth.r4#currentR4The purpose of this profile is to define a representation of a Personal Observations document for a patient for the electronic exchange of health information between individuals, healthcare providers, and the My Health Record system infrastructure in Australia. A Personal Observations document allows for a nominated or authorised representative to record and viewing of childhood measurement information such as a child’s height, weight and head circumference. A composition is a set of resources composed into a single coherent clinical statement that may have clinical attestation.
20ADHA Pharmacist Shared Medicines List Compositionau.digitalhealth.r4#currentR4The purpose of this profile is to define a representation of a Pharmacist Shared Medicines List document that describes a patient's medicine item use at a point in time from a practitioner medicines review for the electronic exchange of health information between individuals, healthcare providers, and the My Health Record system infrastructure in Australia. A composition is a set of resources composed into a single coherent clinical statement that may have clinical attestation.
21ADHA Prescription and or Dispense History Compositionau.digitalhealth.r4#currentR4The purpose of this profile is to define a representation of a Prescription and or Dispense History document that describes a patient's prescription history, or dispense history, or both, at a point in time for the electronic exchange of health information between individuals, healthcare providers, and the My Health Record system infrastructure in Australia. The list may be partial, or complete, and may be a full history or scoped to an active script list. A composition is a set of resources composed into a single coherent clinical statement that may have clinical attestation.
22ADHA Shared Health Summary Compositionau.digitalhealth.r4#currentR4The purpose of this profile is to define a representation of a Shared Health Summary document for a patient for the electronic exchange of health information between individuals, healthcare providers, and the My Health Record system infrastructure in Australia. A composition is a set of resources composed into a single coherent clinical statement that may have clinical attestation.
23ADHA Shared Medicines List Compositionau.digitalhealth.r4#currentR4The purpose of this profile is to define a representation of a Shared Medicines List document that describes a patient's medicine item use at a point in time for the electronic exchange of health information between individuals, healthcare providers, and the My Health Record system infrastructure in Australia. A composition is a set of resources composed into a single coherent clinical statement that may have clinical attestation.
24ADI Composition Headerhl7.fhir.us.pacio-adi#currentR4This abstract profile defines constraints that represent common administrative and demographic concepts for advance directives information used in US Realm clinical documents.
25ADI Personal Advance Care Plan Compositionhl7.fhir.us.pacio-adi#currentR4This profile encompasses information that makes up the author’s advance care information plan.
26ADI Personal Advance Care Plan Compositionhl7.fhir.us.pacio-adi#currentR4This profile encompasses information that makes up the author’s advance care information plan.
27Antapartum Summaryihe.pcc.aps#currentR4Antepartum Summary is a content profile that defines the structure for the aggregation of significant events, diagnoses, and plans of care derived from the visits over the course of an antepartum episode. It is represented in part by Estimated Due Dates and a Visit Summary Flowsheet, in which the aggregated data from the ambulatory office visits is recorded, as well as allergies, advance directives, care plans, and selected histories are provided. The Antepartum Summary represents a summary of the most critical information to an antepartum care provider regarding the status of a patient’s pregnancy.
28AU Base Compositionhl7.fhir.au.base#currentR4This profile defines a composition structure that localises core concepts for use in an Australian context. The purpose of this profile is to provide national level agreement on core localised concepts. This profile does not force conformance to core localised concepts. It enables implementers and modellers to make their own rules, i.e. [profiling](http://hl7.org/fhir/profiling.html), about how to support these concepts for specific implementation needs.
29AU Core Document Compositionhl7.fhir.au.core#currentR4This profile sets minimum expectations for a Composition resource to record, search, and fetch a clinical document for a patient. It is based on the [AU Base Composition](http://build.fhir.org/ig/hl7au/au-fhir-base/StructureDefinition-au-composition.html) profile and identifies the *additional* mandatory core elements, extensions, vocabularies and value sets that **SHALL** be present in the Composition when conforming to this profile. It provides the floor for standards development for specific uses cases in an Australian context.
30AU Primary Care Compositionau.csiro.fhir.au-primarycare#currentR4This profile defines a composition structure that includes core localisation concepts for use in an Australian primary care practice-to-practice record transfer context.
31BeLaboratoryreportCompositionhl7.fhir.be.lab#currentR4Belgian profile for a composition - to use when a laboratory report is sent as FHIR Document
32Breast Imaging Compositionhl7.fhir.us.breast-radiology#currentR4Composition instance for the Breast Imaging FHIR Document.
33BSeR Referral Feedback Compositionhl7.fhir.us.bser#currentR4This Composition profile represents the clical feedback included in the referral feedback document.
34BSeR Referral Request Compositionhl7.fhir.us.bser#currentR4This Composition profile represents the clical supporting information included in the referral request document.
35Care Planhl7.fhir.us.ccda#currentR4CARE 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
36Catalog Headerhl7.fhir.uv.order-catalog#currentR5This profile of Compositions retains the elements and extensions needed to characterize a catalog of healthare products / services / knowledge artefacts, with a set of general properties (name, category, owner, ...)
37CH Allergy Intolerance Composition Profilech.fhir.ig.ch-allergyintolerance#currentR4Definition of the composition for the allergy intolerance document
38CH Core Compositionch.fhir.ig.ch-core#currentR4Base definition for a composition with the CH Core profiles.
39CH Core Composition EPRch.fhir.ig.ch-core#currentR4Base definition for a composition in the context of the electronic patient record (EPR).
40CH CRL Compositionch.fhir.ig.ch-crl#0.9.0R4Definition of the Composition for reporting to the cancer registry
41CH ELM Composition: Laboratory Reportch.fhir.ig.ch-elm#currentR4This CH ELM base profile constrains the Composition resource for the purpose of laboratory test reports.
42CH EMED Medication Card Compositionch.fhir.ig.ch-emed#currentR4Definition of the composition for the medication card document
43CH EMED Medication Dispense Compositionch.fhir.ig.ch-emed#currentR4Definition of the composition for the medication dispense document
44CH EMED Medication List Compositionch.fhir.ig.ch-emed#currentR4Definition of the composition for the medication list document
45CH EMED Medication Prescription Compositionch.fhir.ig.ch-emed#currentR4Definition of the composition for the medication prescription document
46CH EMED Medication Treatment Plan Compositionch.fhir.ig.ch-emed#currentR4Definition of the composition for the medication treatment plan document
47CH EMED Pharmaceutical Advice Compositionch.fhir.ig.ch-emed#currentR4Definition of the composition for the pharmaceutical advice document
48CH EMS Composition Profilech.fhir.ig.ch-ems#1.9.0R4Definition of the composition for the use of the emergency medical service protocol
49CH eTOC Compositionch.fhir.ig.ch-etoc#currentR4Definition for the Composition resource in the context of electronic transition of care.
50CH Lab Composition: Laboratory Reportch.fhir.ig.ch-laboratory-report#currentR4This profile constrains the Composition resource for the purpose of laboratory test reports in Switzerland.
51CH Lab Composition: Laboratory Reportch.fhir.ig.ch-lab-report#currentR4This profile constrains the Composition resource for the purpose of laboratory test reports in Switzerland.
52CH LAB-Order Compositionch.fhir.ig.ch-lab-order#currentR4Definition for Composition resource in the context of CH LAB-Order
53CH ORF Compositionch.fhir.ig.ch-orf#currentR4Profile to specify how the generic elements (e.g. patient, author) and the healthcare domain specific elements must be structured in the Composition as the first entry of the document.
54CH RAD-Order Compositionch.fhir.ig.ch-rad-order#1.0.0R4Definition for the Composition resource in the context of CH RAD-Order.
55CH VACD Immunization Administration Compositionch.fhir.ig.ch-vacd#currentR4Definition of the composition for the immunization administration document.
56CH VACD VaccinationRecord Compositionch.fhir.ig.ch-vacd#currentR4Definition of the composition for the vaccination record document.
57CHMED Medication Card Compositionch.chmed.emediplan#currentR4Profile for the Composition resource of the Medication Card document
58CHMED Medication Prescription Compositionch.chmed.emediplan#currentR4Profile for the Composition resource of the Medication Prescription document
59CL Documentohl7.fhir.cl.clcore#1.8.4R4Definición de un documento para Resumen de Historia o Registro de Encuentro para Historia Clínica, basado en IPS.
60CL Documentohl7.fhir.cl.corecl#currentR4Definición de un documento para Resumen de Historia o Registro de Encuentro para Historia Clínica, basado en IPS.
61Composition (AU IPS)hl7.fhir.au.ips#currentR4Clinical document used to represent the International Patient Summary (IPS) data set. An International Patient Summary (IPS) document is an electronic health record extract containing essential healthcare information about a subject of care. The IPS dataset is minimal and non-exhaustive; specialty-agnostic and condition-independent; but still clinically relevant. As specified in EN 17269 and ISO 27269, it is designed for supporting the use case scenario for ‘unplanned, cross border care’, but it is not limited to it. It is intended to be international, i.e., to provide generic solutions for global application beyond a particular region or country. This profile is based on the ClinicalDocument profile.
62Composition (ePI)hl7.fhir.uv.emedicinal-product-info#currentR5The Composition captures the section headings, sub-section headings, and narrative text (For example, paragraphs, bulleted lists, tables) in an ePI.
63Composition (ePI)hl7.fhir.uv.vulcan-eproduct-info#currentR5The Composition captures the section headings, sub-section headings, and narrative text (For example, paragraphs, bulleted lists, tables) in an ePI.
64Composition (IPS)hl7.fhir.uv.ips#currentR4Clinical document used to represent the International Patient Summary (IPS) data set. An International Patient Summary (IPS) document is an electronic health record extract containing essential healthcare information about a subject of care. The IPS dataset is minimal and non-exhaustive; specialty-agnostic and condition-independent; but still clinically relevant. As specified in EN 17269 and ISO 27269, it is designed for supporting the use case scenario for ‘unplanned, cross border care’, but it is not limited to it. It is intended to be international, i.e., to provide generic solutions for global application beyond a particular region or country. This profile is based on the ClinicalDocument profile.
65Composition (PS-CA)ca.infoway.io.psca#1.0.1-alpha3R4This profile represents the constraints applied to the Composition resource by the PS-CA project. A Canadian Patient Summary (PS-CA) document is an electronic health record extract containing essential healthcare information about a subject of care. It is informed by the IPS-UV Composition profile, but differs in its application of Must Support flags on some of the sections to allow for jurisdictional implementors flexibility in what sections systems Must Support in order to show conformance to their respective patient summaries. The PS-CA dataset is minimal and non-exhaustive; specialty-agnostic and condition-independent; but still clinically relevant. Its informed by the requirements specified in EN 17269 and ISO/DIS 27269, it is designed for supporting the international use case scenario for ‘unplanned, cross border care’, but is also designed to support a variety of use cases for cross-jurisdiction exchange. It is intended to guide implementation nationally while ensuring international exchange of patient summaries is not impeded. This profile is based on the ClinicalDocument profile from the base R4 FHIR standard.
66Composition - ADE Hyperglycemiahl7.fhir.us.nhsn-ade#currentR4This profile supports the electronic submission of adverse drug event (ADE) data relating to hyperglycemia to the National Healthcare Safety Network (NHSN).
67Composition - ADE Hypoglycemiahl7.fhir.us.nhsn-ade#currentR4This profile supports the electronic submission of adverse drug event (ADE) data relating to hypoglycemia to the National Healthcare Safety Network (NHSN).
68Composition - Coded Cause of Fetal Deathhl7.fhir.us.bfdr#currentR4This Composition profile communicates coded cause of fetal death information to appropriate jurisdictional Vital Records Offices.
69Composition - Coded Race and Ethnicityhl7.fhir.us.bfdr#currentR4This Composition profile communicates coded race and ethnicity information to the appropriate jurisdictional Vital Records Office.
70Composition - Inpatient Medication Administrationhl7.fhir.us.nhsn-med-admin#1.0.0R4This profile supports the electronic submission of line-level medication administration data to the National Healthcare Safety Network (NHSN).
71Composition - Jurisdiction Fetal Death Reporthl7.fhir.us.bfdr#currentR4This 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.
72Composition - Jurisdiction Live Birth Reporthl7.fhir.us.bfdr#currentR4This 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.
73Composition - Lab Reporthl7.fhir.it.lab-report#currentR4Descrizione in tramite la risorsa Composition di header e body del Lab Report.
74Composition - MDI to EDRShl7.fhir.us.vrsandbox#currentR4This Composition profile represents data exchanged between an MDI CMS and an EDRS.
75Composition - MDI to EDRShl7.fhir.us.mdi#currentR4This Composition profile represents data exchanged between an MDI CMS and an EDRS.
76Composition - Provider Fetal Death Reporthl7.fhir.us.bfdr#currentR4This 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.
77Composition - Provider Live Birth Reporthl7.fhir.us.bfdr#currentR4This 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.
78Composition Medication Cardch.chmed20af.emediplan#2.0.0R4Profile for the Composition Resource of the Medication Card document.
79Composition Medication Prescriptionch.chmed20af.emediplan#2.0.0R4Profile for the Composition Resource of the Medication Prescription document.
80Composition-IEHRfhir.uv.crossborderdataexchange#currentR4
81Composition: Hospital Discharge Reporthl7.eu.fhir.xpandh.hdr#currentR4Clinical document used to represent a Hospital Discharge Report (HDR) for the scope of the XpanDH project.
82Composition: Laboratory Reporthl7.eu.fhir.xpandh.lab#currentR4Clinical document used to represent a Laboratory Report for the scope of the XPanDH project.
83Composition: Laboratory Reportncez.cz.fhir.lab#currentR4Clinical document used to represent a Laboratory Report in the scope of the Czech national interoperability project.
84Composition: Laboratory Reporthl7.fhir.eu.laboratory#currentR4Clinical document used to represent a Laboratory Report for the scope of the HL7 Europe project.
85Composition: Laboratory Report - Microbiology Culture & Susceptibilityhl7.fhir.eu.laboratory#currentR4Clinical document used to represent a specialized Laboratory Report for representing microbiology culture & susceptibility results in the scope of the HL7 Europe project.
86Composition: Survivor Passporthl7.eu.fhir.pcsp#currentR4This profile defines how to represent a PCSP Survivor Passport by using a HL7 FHIR Composition for the purpose of the PanCareSurPass project.
87CompositionIPS-IEHRfhir.uv.crossborderdataexchange#currentR4
88Consultation Notehl7.fhir.us.ccda#currentR4The 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).
89Continuity of Care Documenthl7.fhir.us.ccda#currentR4This 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.
90CPG Case Plan Progressing Notehl7.fhir.uv.cpg#currentR4CPG Case Plan Progressing Note combines relevant case features and feature groups with proposals, plans, and clinical impressions to provide a means to document patient progression with respect to a pathway in the context of a computable clinical practice guideline
91CPG Case Plan Summaryhl7.fhir.uv.cpg#currentR4CPG Case Plan Summary addresses information from the plan portion of the CPG, including patient-specific recommendations (i.e., proposals) along with their respective pertinent patient information and guideline recommendations that are either not applicable or not yet applicable to a specific patient
92CPG Case Summaryhl7.fhir.uv.cpg#currentR4CPG Case Summary is the set of case features and feature groups that completely represent the case data scoped by the clinical practice guideline. This expresses the complete patient state at any given point in time.
93Death Certificatehl7.fhir.us.vrdr#currentR4The body of the death certificate document (Composition).
94Death Certificatehl7.fhir.us.vrsandbox#currentR4The body of the death certificate document (Composition).
95Dental Consult Notehl7.fhir.us.dental-data-exchange#currentR4This 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.
96Dental Referral Notehl7.fhir.us.dental-data-exchange#currentR4This 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.
97DEQM Gaps In Care Composition Profilehl7.fhir.us.davinci-deqm#currentR4The 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.
98Diagnostic Imaging Reporthl7.fhir.us.ccda#currentR4A 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.
99DiagnosticReportRecordndhm.in#currentR4The Clinical Artifact represents diagnostic reports including Radiology and Laboratory reports that can be shared across the health ecosystem.
100DIS Compositionch.cara.fhir.epr.emed#currentR4Definition of the composition for the medication dispense document
101Discharge Summaryhl7.fhir.us.ccda#currentR4The 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.
102DischargeSummaryRecordndhm.in#currentR4Clinical document used to represent the discharge summary record for ABDM HDE data set.
103Documento Cohl7.fhir.co.CoreCO#currentR4Definición de un documento clínico para las necesidades de interoperabilidad en Colombia.
104eCTD Batch Analyses Compositionhl7.fhir.us.pq-cmc#currentR5The 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
105eCTD Batch Formulahl7.fhir.us.pq-cmc#currentR5The fields needed to represent the Product Batch Formula to be included under the eCTD. References Sponsor Organization and Batch Formula
106eCTD Product Characterization of Impurities Compositionhl7.fhir.us.pq-cmc#currentR5The 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
107eCTD Product Container Closure System Compositionhl7.fhir.us.pq-cmc#currentR5The fields needed to represent the Product Container Closure Systems to be included under the eCTD p.7.0
108eCTD Product Description and Compositionhl7.fhir.us.pq-cmc#currentR5The 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.
109eCTD Specification Compositionhl7.fhir.us.pq-cmc#currentR5The 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.
110eCTD Stability Data Compositionhl7.fhir.us.pq-cmc#currentR5The 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.
111eCTD Stability Summary and Conclusion Compositionhl7.fhir.us.pq-cmc#currentR5The 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.
112eCTD Substance Characterizationhl7.fhir.us.pq-cmc#currentR5The 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
113eCTD Substance Container Closure System Compositionhl7.fhir.us.pq-cmc#currentR5The 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
114eCTD Substance Control of Materials Compositionhl7.fhir.us.pq-cmc#currentR5The fields needed to represent the Substance Control of Materials in a to be included under the eCTD. References Sponsor Organization and Drug Substance Materials.
115eCTD Substance General Informationhl7.fhir.us.pq-cmc#currentR5The 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.
116Electronic Initial Case Report Compositionhl7.fhir.us.ecr#currentR4This Composition profile represents an electronic initial case report (eICR). It is based on and further constrains the US Public Health Composition.
117EvidenceMaphl7.fhir.uv.ebm#currentR5Profile of Composition for Evidence Based Medicine IG. The EvidenceMap Profile is used for an organized listing of Resources used to generate EvidenceReport instances.
118EvidenceReporthl7.fhir.uv.ebm#currentR5Profile of Composition for Evidence Based Medicine IG. The EvidenceReport Profile is used for a base structure (canonical resource management) for a report combining any number of Citation, Evidence, EvidenceVariable, EvidenceReport, and related Resources.
119gp-EncounterReportnictiz.fhir.nl.stu3.zib2017#2.2.15R3The general practitioner encounter report is an S-O-A-P (Subjective, Objective, Assessment, Plan) structured report of a patient encounter. S-O-A-P is known as S-O-E-P (Subjectief, Objectief, Evaluatie, Plan) in Dutch. Each Composition.section corresponds with a letter from SOAP and may additionally be ICPC coded using the appropriate extension. If the encounter report relates to an episode of care then the association with EpisodeOfCare shall be in Composition.event.detail.
120Guidelinehl7.fhir.uv.ebm#currentR5Profile of Composition for Evidence Based Medicine IG. The Guideline Profile is used for the composition of a clinical practice guideline and may be tightly related to use of Recommendation Profile of Composition for related content.
121Health Care Survey Report Compositionhl7.fhir.us.health-care-surveys-reporting#currentR4This Composition profile is used to organize the healthcare survey report content.
122HealthDocumentRecordndhm.in#currentR4The Clinical Artifact represents the unstructured historical health records as a single of multiple Health Record Documents generally uploaded by the patients through the Health Locker and can be shared across the health ecosystem.
123History and Physicalhl7.fhir.us.ccda#currentR4A 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.
124HospitalDischargeReport-IEHRfhir.uv.crossborderdataexchange#currentR4
125ICSR Compositionhl7.fhir.us.icsr-ae-reporting#currentR4The fields needed to represent the document metadata of a ICSR Report.
126ImagingResultReportComposition (CZ)ncez.cz.fhir.imaging#currentR4Czech profile for a composition - to be used when a imaging result report is sent as FHIR Document
127ImmunizationRecordndhm.in#currentR4The Clinical Artifact represents the Immunization records with any additional documents such as vaccine certificate, the next immunization recommendations, etc. This can be further shared across the health ecosystem.
128Laboratory Report Composition (CZ)ncez.cz.fhir.lab#currentR4Czech profile for a composition - to be used when a laboratory report is sent as FHIR Document
129LIVDCataloghl7.fhir.uv.livd#currentR4Profile on the Composition resource to specify and organize the sections and references to the necessary resource content to express the LIVD catalog.
130M11Section01hl7.fhir.uv.ebm#currentR5Profile of Composition for Evidence Based Medicine IG. The M11Section01 Profile is used for summary of Section 1 Protocol Summary for the International Council for Harmonisation of Technical Requirements for Pharmaceuticals for Human Use (ICH) Clinical Electronic Structured Harmonised Protocol (CeSHarP) M11 Technical Specification.
131M11Section02hl7.fhir.uv.ebm#currentR5Profile of Composition for Evidence Based Medicine IG. The M11Section02 Profile is used for summary of Section 2 Introduction for the International Council for Harmonisation of Technical Requirements for Pharmaceuticals for Human Use (ICH) Clinical Electronic Structured Harmonised Protocol (CeSHarP) M11 Technical Specification.
132M11Section03hl7.fhir.uv.ebm#currentR5Profile of Composition for Evidence Based Medicine IG. The M11Section03 Profile is used for summary of Section 3 Trial Objectives, Endpoints and Estimands for the International Council for Harmonisation of Technical Requirements for Pharmaceuticals for Human Use (ICH) Clinical Electronic Structured Harmonised Protocol (CeSHarP) M11 Technical Specification.
133M11Section04hl7.fhir.uv.ebm#currentR5Profile of Composition for Evidence Based Medicine IG. The M11Section04 Profile is used for summary of Section 4 Trial Design for the International Council for Harmonisation of Technical Requirements for Pharmaceuticals for Human Use (ICH) Clinical Electronic Structured Harmonised Protocol (CeSHarP) M11 Technical Specification.
134M11Section05hl7.fhir.uv.ebm#currentR5Profile of Composition for Evidence Based Medicine IG. The M11Section05 Profile is used for summary of Section 5 Trial Population for the International Council for Harmonisation of Technical Requirements for Pharmaceuticals for Human Use (ICH) Clinical Electronic Structured Harmonised Protocol (CeSHarP) M11 Technical Specification.
135M11Section06hl7.fhir.uv.ebm#currentR5Profile of Composition for Evidence Based Medicine IG. The M11Section06 Profile is used for summary of Section 6 Trial Intervention and Concomitant Therapy for the International Council for Harmonisation of Technical Requirements for Pharmaceuticals for Human Use (ICH) Clinical Electronic Structured Harmonised Protocol (CeSHarP) M11 Technical Specification.
136M11Section07hl7.fhir.uv.ebm#currentR5Profile of Composition for Evidence Based Medicine IG. The M11Section07 Profile is used for summary of Section 7 Discontinuation of Trial Intervention and Participant Withdrawal from Trial for the International Council for Harmonisation of Technical Requirements for Pharmaceuticals for Human Use (ICH) Clinical Electronic Structured Harmonised Protocol (CeSHarP) M11 Technical Specification.
137M11Section08hl7.fhir.uv.ebm#currentR5Profile of Composition for Evidence Based Medicine IG. The M11Section08 Profile is used for summary of Section 8 Trial Assessments and Procedures for the International Council for Harmonisation of Technical Requirements for Pharmaceuticals for Human Use (ICH) Clinical Electronic Structured Harmonised Protocol (CeSHarP) M11 Technical Specification.
138M11Section09hl7.fhir.uv.ebm#currentR5Profile of Composition for Evidence Based Medicine IG. The M11Section09 Profile is used for summary of Section 9 Statistical Considerations for the International Council for Harmonisation of Technical Requirements for Pharmaceuticals for Human Use (ICH) Clinical Electronic Structured Harmonised Protocol (CeSHarP) M11 Technical Specification.
139M11Section10hl7.fhir.uv.ebm#currentR5Profile of Composition for Evidence Based Medicine IG. The M11Section10 Profile is used for summary of Section 10 General Considerations: Regulatory, Ethical, and Trial Oversight for the International Council for Harmonisation of Technical Requirements for Pharmaceuticals for Human Use (ICH) Clinical Electronic Structured Harmonised Protocol (CeSHarP) M11 Technical Specification.
140M11Section11hl7.fhir.uv.ebm#currentR5Profile of Composition for Evidence Based Medicine IG. The M11Section11 Profile is used for summary of Section 11 General Considerations: Risk Management and Quality Assurance for the International Council for Harmonisation of Technical Requirements for Pharmaceuticals for Human Use (ICH) Clinical Electronic Structured Harmonised Protocol (CeSHarP) M11 Technical Specification.
141M11Section12hl7.fhir.uv.ebm#currentR5Profile of Composition for Evidence Based Medicine IG. The M11Section12 Profile is used for summary of Section 12 Appendix: Adverse Events and Serious Adverse Events -- Definitions, Severity, and Causality for the International Council for Harmonisation of Technical Requirements for Pharmaceuticals for Human Use (ICH) Clinical Electronic Structured Harmonised Protocol (CeSHarP) M11 Technical Specification.
142M11Section13hl7.fhir.uv.ebm#currentR5Profile of Composition for Evidence Based Medicine IG. The M11Section13 Profile is used for summary of Section 13 Appendix: Definitions and Supporting Operational Details for the International Council for Harmonisation of Technical Requirements for Pharmaceuticals for Human Use (ICH) Clinical Electronic Structured Harmonised Protocol (CeSHarP) M11 Technical Specification.
143M11Section14hl7.fhir.uv.ebm#currentR5Profile of Composition for Evidence Based Medicine IG. The M11Section14 Profile is used for summary of Section 14 Appendix: Glossary of Terms for the International Council for Harmonisation of Technical Requirements for Pharmaceuticals for Human Use (ICH) Clinical Electronic Structured Harmonised Protocol (CeSHarP) M11 Technical Specification.
144M11Section15hl7.fhir.uv.ebm#currentR5Profile of Composition for Evidence Based Medicine IG. The M11Section15 Profile is used for summary of Section 15 Appendix: References for the International Council for Harmonisation of Technical Requirements for Pharmaceuticals for Human Use (ICH) Clinical Electronic Structured Harmonised Protocol (CeSHarP) M11 Technical Specification.
145MedNet Interface (MNI) - PatientOverview Compositionswiss.mednet.fhir#0.15.0R4MedNet Interface (MNI) - PatientOverview Composition
146MTP Compositionch.cara.fhir.epr.emed#currentR4Definition of the composition for the medication treatment plan document
147no-basis-Compositionhl7.fhir.no.basis#2.1.2R4Basisprofil for Norwegian Composition. Defined by The Norwegian Directorate of eHealth and HL7 Norway. The profile adds terminology and extensions specific to Norway. The basis profile is open, derived profiles should close down the information elements according to the relevant use-case. The profile sets the absolute minimum requirements, identifies the extensions and terminology which can be present.
148NZIPS-Compositiontewhatuora.fhir.ig.nzips#currentR4Clinical document used to represent the NZIPS data set. It is an electronic health record extract containing essential healthcare information about a subject of care. The NZIPS dataset is minimal and non-exhaustive; specialty-agnostic and condition-independent; but still clinically relevant.
149Occupational Data For Healthhl7.fhir.us.odh#currentR4This 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.
150OPConsultRecordndhm.in#currentR4The Clinical Artifact represents the outpatient visit consultation note which may include clinical information on any OP examinations, procedures along with medication administered, and advice that can be shared across the health ecosystem.
151Operative Notehl7.fhir.us.ccda#currentR4The 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.
152PACIO ADI Headerhl7.fhir.us.pacio-adi#currentR4This abstract profile defines constraints that represent common administrative and demographic concepts for advance directives information used in US Realm clinical documents.
153PADV Compositionch.cara.fhir.epr.emed#currentR4Definition of the composition for the pharmaceutical advice document
154Paramedicince Care Summary Composition Clinical Subsetihe.pcc.pcs#currentR4The composition of the FHIR elements that are used to build the FHIR Document for the Paramedicine Care Summary Clinical Subset the following cardinalities follow the documentation in the PCS profile: - RE 0..1 IPS Advance Directives - R 1..1 IPS Allergies and Intolerances - R 1..1 IPS Medications - RE 0..1 Medications Administered Section - RE 0..1 IPS History of Past Illness - R 1..1 IPS Functional Status - RE 0..1 IPS History of Procedures - O 0..1 Immunizations - O 0..1 IPS Medical Devices - R 0..1 IPS Problems - O 0..1 IPS Results - RE 0..1 IPS Vital Signs - RE 0..1 IPS History of Pregnancy - O 0..1 IPS Plan of Care - O 0..1 Payor - RE 0..1 InjuryEvent seciton - RE 0..1 eArrest Section
155Paramedicince Care Summary Composition CompleteReportihe.pcc.pcs#currentR4The composition of the FHIR elements that are used to build the FHIR Document for the Paramedicine Care Summary the following cardinalities follow the documentation in the PCS profile: - RE 0..1 IPS Advance Directives - R 1..1 IPS Allergies and Intolerances - R 1..1 IPS Medication Summary - RE 0..1 Medications Administered Section - RE 0..1 IPS History of Past Illness - R 1..1 IPS Functional Status - RE 0..1 IPS History of Procedures - O 0..1 Immunizations - O 0..1IPS Medical Devices - R 0..1 IPS Problems - O 0..1 IPS Results - RE 0..1 IPS Vital Signs - RE 0..1 IPS History of Pregnancy - O 0..1 IPS Plan of Care - O 0..1 Payor - RE 0..1 InjuryEvent seciton - RE 0..1 EMS Protocol Section - R 1..1 Paramedicine Note - RE 0..1 eArrest Section - RE 0..1 EMS Response Section - RE 0..1 EMS Times Section - O 0..1 CareTeam - O 0..1 Physician Certification Statement - RE 0..1 Transport Section
156PCDE Coverage Transition Composition Profilehl7.fhir.us.davinci-pcde#currentR4Constraints on Composition to define the root and table of contents for a Coverage Transition Document
157PhCP Compositionhl7.fhir.us.phcp#1.0.0R4The 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.
158PML Compositionch.cara.fhir.epr.emed#currentR4Definition of the composition for the medication list document
159PMLC Compositionch.cara.fhir.epr.emed#currentR4Definition of the composition for the medication card document
160PRE Compositionch.cara.fhir.epr.emed#currentR4Definition of the composition for the medication prescription document
161PrescriptionRecordndhm.in#currentR4The Clinical Artifact represents the medication advice to the patient in compliance with the Pharmacy Council of India (PCI) guidelines, which can be shared across the health ecosystem.
162Procedure Notehl7.fhir.us.ccda#currentR4A 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.
163ProductSubmissionDocumenthl7.fhir.us.spl#currentR4BA profile that represents a document that is required for Product Submission to the FDA.
164Progress Notehl7.fhir.us.ccda#currentR4This 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.
165Radiation Summary Reporthl7.fhir.uv.radiation-dose-summary#currentR4A report document describing the irradiation act
166Recommendationhl7.fhir.uv.ebm#currentR5Profile of Composition for Evidence Based Medicine IG. The Recommendation Profile is used for the composition of a recommendation (such as that from a clinical practice guideline) and may be tightly related to a RecommendationPlan Profile of PlanDefinition and a RecommendationJustification Profile of ArtifactAssessment.
167Referral Notehl7.fhir.us.ccda#currentR4A 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.
168Refferal For Interfacility Patient Transportihe.pcc.ript#currentR4composition of the FHIR elements that are used to build the FHIR Document for the Refferal For Interfacility Patient Transport document. the following cardinalities follow the documentation in the RIPT profile: - RE 0..1 IPS Advance Directives - R 1..1 IPS Allergies and Intolerances - R 1..1 IPS Medication Summary - RE 0..1 IPS History of Past Illness - R 1..1 IPS Functional Status - RE 0..1 IPS History of Procedures - O 0..1 Immunizations - O 0..1 IPS Medical Devices - RE 0..1 IPS Problems - O 0..1 IPS Results - RE 0..1 IPS Vital Signs - RE 0..1 IPS History of Pregnancy - O 0..1 IPS Plan of Care - O 0..1 Payor - RE 0..1 Coded Reason for Referral - RE 0..1 Transport Instructions
169RR Compositionhl7.fhir.us.ecr#currentR4This Composition profile represents the Reportability Response that is created in response to an electronic Initial Case Report Composition.
170SummaryOfFindingshl7.fhir.uv.ebm#currentR5Profile of Composition for Evidence Based Medicine IG. The SummaryOfFindings Profile is used for an evidence report combining Evidence and EvidenceVariable Resources, organized around OutcomeDefinition (Profile of EvidenceVariable), to represent the summary of findings of comparative evidence.
171SummaryOfNetEffecthl7.fhir.uv.ebm#currentR5Profile of Composition for Evidence Based Medicine IG. The SummaryOfNetEffect Profile is used for an evidence report combining ArtifactAssessment and Evidence and EvidenceVariable Resources, organized around OutcomeDefinition (Profile of EvidenceVariable), to represent the summary of net effect contributions of comparative evidence, adjusted for the relative importance of outcomes.
172TableConstructorhl7.fhir.uv.ebm#currentR5Profile of Composition for Evidence Based Medicine IG. The TableConstructor Profile is used for specifying column headers and instructions for generating content values for table rows and table cells. For the Evidence Based Medicine IG, the TableConstructor Profile is intended to facilitate processing the input of an EvidenceMap instance and generating the output of an EvidenceReport instance.
173Transfer Summaryhl7.fhir.us.ccda#currentR4This 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.
174US Public Health Compositionhl7.fhir.us.ecr#currentR4This Composition profile represents a public health composition.
175US Public Health Compositionhl7.fhir.us.ph-library#currentR4This Composition profile represents a public health composition.
176US Public Health Compositionhl7.fhir.us.ph-library#currentR4This Composition profile represents a public health composition.
177US Realm Headerhl7.fhir.us.ccda#currentR4This 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.
178VetCompositionfhir.zentricx-grupo-b#currentR4
179VisitReport-IEHRfhir.uv.crossborderdataexchange#currentR4
180WellnessRecordndhm.in#currentR4The Clinical Artifact represents regular wellness information of patients typically through the Patient Health Record (PHR) application covering clinical information such as vitals, physical examination, general wellness, women wellness, etc., that can be shared across the health ecosystem.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180
Composition D D D I D D D D D D D D D D D D D D I I I I I D D D D D D D D D D D D D D D D
Composition.id D
Composition.confidentiality C C C C B M F C D C F F C F F F F C D C
Composition.confidentiality.id D D D D D D
Composition.confidentiality.extension S S C (2) S S S S S S S S S S S C (2) S C (2) S C (2) S C (2) S C (2) S C (2)
Composition.confidentiality.extension.value[x] S S S S S S
Composition.confidentiality.extension.value[x].coding F F F F F F
Composition.confidentiality.extension.value[x].coding.userSelected D D D D D D
Composition.confidentiality.extension.value[x].coding.version D D D D D D
Composition.confidentiality.extension.value[x].coding.extension D D D D D D
Composition.confidentiality.extension.value[x].extension D D D D D D
Composition.meta
Composition.meta.tag D D D D D D
Composition.meta.security D D D D D D
Composition.meta.source D D D D D D
Composition.meta.lastUpdated D D D D D D
Composition.meta.versionId D D D D D D
Composition.meta.extension D D D D D D
Composition.meta.profile C C C C C C C C C C C C C
Composition.implicitRules C D C D C D C D C D C D
Composition.language C C C F C D C C
Composition.text C
Composition.text.status F
Composition.contained
Composition.extension S C (2) S C (8) S C D (2) S C (2) S (2) S (2) S C (3) S C (10) S (2) S (2) S C S C (2) S C (2) S C (3) S C (5) S C (5) S C (2) S C D (2) S D S C (5) S C (5) S C (2) S C (2) S C (2) S C D (3) S C (2) S C (2) S C D (3) S C D (3) S C (4) S C (4) S S C D (3) S C (10) S C (10) S C (2) S C (11) S C (2) S C D S C D (3) S C D (3) S C D (3) S C (8)
Composition.extension.url F
Composition.extension.value[x] S C (3) S C (2) S C (2)
Composition.modifierExtension C D C D C D C D C D C D
Composition.url
Composition.identifier C C C C C C C D D C D C D C C C C I I D C C C C C C C C C C C C C D C C C C D C C C D C D C D C C
Composition.identifier.assigner D C D D D D D C
Composition.identifier.assigner.display C D
Composition.identifier.assigner.identifier C
Composition.identifier.assigner.reference C
Composition.identifier.period D C D D D D D C
Composition.identifier.type D C D D D D D C
Composition.identifier.use F C F F F F F C
Composition.identifier.extension D D D D D D
Composition.identifier.value C C I C C I C C D I I I I I C
Composition.identifier.system C F C F C C C F C C F
Composition.version
Composition.status F F F F F F F F F F F F F F F F F F F F F F F F F F F F F F F D F D D D I D D D I B M B M D F F F F F F F F F F F F F F D F F
Composition.type F B M B M B M F F F F F F F B M F B M B M F F B M F B M F I F I F I F I F I F I F F F F F B M F F F D B M D B M D D B M F D C F D F D F D F D F D F D F D F D I F D F D F D F D F D B M F D I D B M F B M F F F F F F F D B M D B M B M D B M F F F F F F F F F F F F F D F D D B M F F F D B M B M B M F D B M B M B M B M F D B M F
Composition.type.extension D D D D D D
Composition.type.coding C C C D C C D S C D (2) C C D F C
Composition.type.coding.userSelected D C D D D D D C
Composition.type.coding.version D C D D D D D C
Composition.type.coding.extension D D D D D D
Composition.type.coding.display F C C F C F C F C C F C F C F
Composition.type.coding.code F C C F F C F C F C D C F C F C F C F
Composition.type.coding.system F F F F F F C C F F F C F
Composition.type.text C F F C C F
Composition.category S C F (2) S C F (2) S C F (2) C B M S C F (2) C B M S C F (2) S C F (2) S C F (2) S C F (2) S C F (2) S C F (2) S C F (2) S C F (2) S C F (2) S C F (2) B M S C F (2) S C F (2) C F S C F (2) C C B M F F C B M F I S C I F D B M (3) S C (2) S C (2) C C S C (2) S C (2) S C (2) S C (2) S C (2) S C (2) S C (2) S C (2) S C (2) S C (2) S C (2) S C (2) S C (2) S C (2) S C (2) C C S C (2) S C (2) S C (2) S C (2) C
Composition.category.text C F C F C F C F C F C F C F C F C F C F C F C F C F C F C F C F C F C F C F C F C F C
Composition.category.coding C C
Composition.category.coding.userSelected C
Composition.category.coding.display C F
Composition.category.coding.version C
Composition.category.coding.code C F C F
Composition.category.coding.system C F C F
Composition.subject I C I C C C C C C D C C C C C C D C D C C D D C C C C C C D C D C I C D C D C D C D C D C C I D C C C C C C C D C D C D C D C C C C C C D C C C C C C D C C C C D C D C D C C
Composition.subject.display C
Composition.subject.identifier C
Composition.subject.type C
Composition.subject.reference C C C C C C C C C C C C C C
Composition.encounter C C C C C C D D D C C C D D I D D I D C C D C C D C C D C D C D C C D D D D C D C D C D C
Composition.encounter.extension C C
Composition.encounter.display D D
Composition.encounter.identifier D D
Composition.encounter.reference C C C C C C
Composition.date I I I D D D I D D D I I I I I
Composition.useContext
Composition.author C C I I C C C C C D C D C C C C C C C D S C (3) S C (3) S C (3) S C (3) C S C (2) S C C D C D D D D D C D C D C D C D I D C C C D C D S C D (2) D I D S (3) C D C C C C C C C C C C C C C D D C D D C D S (3) S (3) C C D S (3) D C C D C D C D D
Composition.author.type C
Composition.author.display C D C
Composition.author.identifier C C
Composition.author.id D D D D D D
Composition.author.reference C C C C C C C
Composition.author.extension C S C C C S C (2) S C (2)
Composition.name
Composition.title F F F D D D D D D F D D D D D D F D F D D D F C D
Composition.title.extension S (2)
Composition.note
Composition.attester I C C S (2) S C (2) S (2) S (2) S (2) S (2) S (2) S (2) S (2) D D S C (3) C D C D S (2) C S D (2) C C C S D (2) S C (4) S D (2) S D (2) S D (2) S D (2) S C (4) C
Composition.attester.extension S C (2)
Composition.attester.modifierExtension
Composition.attester.mode F F F F F F B M B M F (2) F F F B M D F (3) C F (3)
Composition.attester.time C C C D D C C
Composition.attester.party C C C D D (2) D D C (3) C (3) C
Composition.attester.party.display C
Composition.attester.party.identifier C
Composition.attester.party.type C
Composition.attester.party.extension S C (2)
Composition.attester.party.reference C C
Composition.custodian C I C C C C C C D C C C C C C
Composition.custodian.display C
Composition.custodian.identifier C
Composition.custodian.type C
Composition.custodian.id D D D D D D
Composition.custodian.reference C C
Composition.relatesTo D D D D D S C D (3) C D D D D D S C (2) S C D (3) S C D (3) S C D (3) S C D (3) C
Composition.relatesTo.resourceReference
Composition.relatesTo.type F
Composition.relatesTo.target[x] D (2) D (2) D (2) D (2) D (2)
Composition.relatesTo.code F F (2) F F F F F F (2) F (2) F (2) F (2)
Composition.event C C S C D (2) S C D (2) C C C D C D D C D D D D C C C
Composition.event.code C F C F C F C F C F C B M
Composition.event.extension
Composition.event.modifierExtension
Composition.event.period C C C C
Composition.event.period.end C C
Composition.event.period.start C C
Composition.event.detail S (2) C C S (2)
Composition.section S C (5) C C S C I D (12) S C I D (15) C S C I D (2) S C I D (10) C S C I D (8) S C I D (6) S C I D (8) S C D (8) S C D (5) D C D S C I D (3) S C I D (3) C D S D (2) I D S C I D (5) S C I D (3) S C I D (8) S C I (7) S C D (18) C S C (13) C S C D (8) S C (8) S C (8) S C D (5) C S C (3) S C (2) S C (11) S C (2) S C (4) S C (3) S C (3) S C (4) S C (3) S C (3) S C (12) S C (14) S C (3) S S C (7) S C (6) S C (3) S (2) S C D (6) S C D (6) S (15) C D C D S C D (15) S C D (16) S C D (6) S C D (6) S C D (2) C D S C D (5) S C D (7) S C D (7) S C D (4) S C D (8) S C D (8) S C D (7) S C D (7) S C (5) S (4) S C D (29) S C D (4) S C D (4) S C (3) S S C D (26) S C D (20) S C (2) S C (6) S C (6) S C D (8) S C (8) C S C D (11) C S C (5) S C D (28) S C (11) S C D (4) S C D (3) C D C D C D S C D (4) S C D (4) S C D (3) S C D (3) S C D (3) C D C D S C D (3) S C D (19) S C (9) S C (7) S C D (18) C D S C (22) S (14) S C (15) C C C C D S C (4) S C (3) S C (2) S C (5) S C (7) S C (9) S C (5) S C (12) S C (10) S C (6) S C (4) S C (5) S C (5) S C (2) S C (2) S C (12) S C (5) C D S C (12) S C (17) S C (5) S C D (10) S C D (6) S C (3) S C D (3) S C (5) S C (5) S C (5) C D S C (29) S C (3) S C D (17) S C (4) S C (6) S C D (26) S C D (5) S C D (4) S C (3) S C (4) S C (4) S C D (27) S C D (14) S (20) S C D (9)
Composition.section.id D (2) D (2) D (2) D (2) D (2)
Composition.section.mode F F F (12) F C D F F F F F C (13)
Composition.section.extension S C (2) S (7) S S (4) S (4) S C (2) S C (2) D S C (2) D S C (2) D D D S C (7) S C D (6)
Composition.section.modifierExtension C D (5) C D (5) C D (5) C D (5) C D (5) C D (5)
Composition.section.title C (11) C (14) C C (9) C (7) C (5) C (7) C (7) C F (4) C C C (2) C C (4) C (2) C (7) C (6) F (7) C (4) C (2) C C (10) C C (3) C (2) C (2) C (3) C (2) C (2) C (11) C (13) C (2) C (6) C (6) C (5) C (5) C D C D (14) C D (15) C (5) C (5) C (4) C (3) (3) C D (26) C C C (2) C (25) C (19) C (2) C (2) C (10) C (27) C (3) C (2) C C C C C C (2) C (2) C C C C (2) C (21) C F (15) C D C F (11) C (16) C (3) C (2) C (28) C (2) C (16) C (25) F (3) C (26) C F (13) C F (8)
Composition.section.code C F C F C F D (11) C F D (14) C F D C F D (9) C F D (7) C F D (5) C F D (7) C F D (7) C F (4) C F D C F D C F D (2) C F D (2) C F C B M C F D (4) C F D B M (2) C F (7) C F (6) C F (8) (12) C F (7) C F (8) C F (8) C F (4) C F (2) C F C F (10) C B M (2) C F (2) C F (2) C F (2) C F (2) C F (2) C F (2) C F (11) C F (13) C F (2) C F (6) C F (6) C F C F B M (6) C F B M (6) F (14) C B M C B M C F (15) C F (16) C F (5) C F (5) C F D F C F (4) C F D (6) C F D (6) C F B M (4) C F D (7) C F D (7) C F D (6) C F D (6) C F (4) (3) C F (28) C F B M (4) C F B M (4) F C F (2) C F (25) C F (19) C F C F (6) C F (6) C F (3) C F (3) C F (10) C F C F (27) C F B M (4) C F (2) F F F C F B M (4) C F B M (4) C F (2) C F (2) C F F F C F (2) C F D (18) C F (8) C B M C F D (17) C F (21) F (13) C F (15) C D B M C F (11) C F C F (16) C F C F (9) C F (5) C F B M (2) C F (2) C F C F C F C F (28) C F B M (3) C F (16) C F (25) C F (4) C F (3) C F C F C F (26) C (13) F (19)
Composition.section.code.extension D (2) D (3) D (2) D (2) D (2)
Composition.section.code.text (10) F (6) F (3) F (2) F F (4) F (6) F (8) F (4) F (11) F (9) F (5) F (3) F (4) F (4) F F (11) F (5) F F (2) F (3)
Composition.section.code.coding C C (10) C C (11) C C C C C F (3)
Composition.section.code.coding.version D (2) D (3) D (2) D (2) D (2)
Composition.section.code.coding.extension D (2) D (3) D (2) D (2) D (2)
Composition.section.code.coding.userSelected F D (2) D (3) D (2) D (2) D (2)
Composition.section.code.coding.display F (2) C C F (10) C F C F C F (11) C F
Composition.section.code.coding.code C F (12) C C F (10) C F C F C F (11) C F
Composition.section.code.coding.system F (12) F F (10) F F F (11) F
Composition.section.author (5) (5) C (5) (5) (5) C (5) C (5) (5) C (13)
Composition.section.author.reference C C C C C C (5) C (5)
Composition.section.author.extension C C (5) C (5)
Composition.section.focus C C D C D (4) C D (4) C D (4) C D (4) C D (3) C (3) D (3) D (3) D D (3) D (3) C (13)
Composition.section.text C (7) C C C C (4) C (2) C C (2) C (2) C (2) C (2) C (2) C (2) C (11) (13) C (2) (6) (6) C C (5) (5) C (4) C (3) D (3) C D (4) (2) (2) C (28) C (3) C (3) C (2) C (25) C (19) C (10) C (27) C D (18) C C D (17) C (21) C (4) C C (2) C C C (4) C (6) C (8) C (4) C (11) C (9) C (5) C (3) C (4) C (4) C C C (16) C C (2) C C (28) C (2) C (16) C (25) C D (2) C (26) C (13)
Composition.section.orderedBy D C D D D D D C (13)
Composition.section.entry (4) C C (11) (14) C (9) (7) (5) (7) (4) C C (2) (2) C I D (4) (2) (6) (6) S C (19) S C (29) C C D (7) S C (25) S C (36) S (8) C S C (86) C (2) C S C (5) C (2) C C S C (14) S C (17) S C (6) S (6) C (6) S C D (8) S C (5) S C (5) S (33) S C D (33) S C D (48) S C (13) S C (11) S C D (3) S C D (3) S C (9) S C D (39) S C D (54) C (2) S C D (18) S C D (18) S C D (31) S C D (42) S C D (9) (2) S C D (36) C (2) C (2) S C D (6) S S (36) S (38) C S C D (43) S C D (43) S C (7) S C (8) C S (4) S C D (3) C (3) S (34) (10) S C (3) C (3) C C (3) C (4) C (3) C (3) C (2) C C C (3) S C D (41) (8) D S C (31) C D S (26) S (28) C (15) C S C D (4) C C (2) (4) (4) S C (31) C (3) S C D (6) (11) S (14) C (3) S C D (14) S C D (5) C (2) S (4) S C (5) C (2) C (3) S C D (3) S (26) C (3) S (20) (3) S (42) S C D (18) S C D (5) S (46) (8)
Composition.section.entry.display C D C (13)
Composition.section.entry.identifier C C (13)
Composition.section.entry.id D (2) D (2) D (2) D D (2) D (2)
Composition.section.entry.type C F (2) C F (3) C F (2) C (13)
Composition.section.entry.extension S C S C D (16)
Composition.section.entry.reference C C C C (76) C C C (4) C C C C (11) C (4) C (6) C (5) C (2) C (10) C C (3) C C (11) C (2) C (13) C (8)
Composition.section.emptyReason B M (11) B M (14) B M (9) B M (7) B M (5) B M (7) B M (4) C C B M (2) B M (2) C B M B M (4) B M (2) B M B M C C (15) D (4) (4) C (27) (2) D (2) C D (2) D (2) D (2) D (2) C (13)
Composition.section.section C C C C C C C S C (2) C C C (10) C C (2) C (2) C (2) C (2) C (2) C (2) S C (14) C (10) C (2) C (6) C (6) C D D C C (15) C (3) C C C (3) C (3) S C (9) D (2) C S C (7) S C (4) S C (4) S C (2) S C (18) D (2) D (2) S C (5) D (2) D (2) C (3) S C (67) S C (18) S C (18) C (3) C (13)
Composition.section.section.extension S C (7)
Composition.section.section.orderedBy
Composition.section.section.emptyReason (7)
Composition.section.section.text C (7) C (6) C (3) C (3) C C (15) C (3) C
Composition.section.section.section C (3) C C S C (7) C (3) S C (3)
Composition.section.section.section.emptyReason (6)
Composition.section.section.section.entry S C D (21)
Composition.section.section.section.text C (6) C
Composition.section.section.section.code C F (6)
Composition.section.section.section.code.text F (2)
Composition.section.section.section.title C (6) F (2)
Composition.section.section.title C F (3) C C (7) (3)
Composition.section.section.entry S C (5) S C (6) C C C S C D (24) (6) C (3) C C (7) C (7)
Composition.section.section.entry.reference C (5)
Composition.section.section.focus
Composition.section.section.code C F C B M C B M C B M C B M C B M C F (8) C F B M (3) C B M C F (14) C F (8) C
Composition.section.section.code.text F (6) F (3) F (3) F F (15) F (62) F (2) F (8)
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