+
-##### MedComDocumentBundle
+The figure shows the general MedCom document model. It is a structural overview of a MedCom Document Bundle, illustrating the relationships between Bundle, Composition, authorPerson, subject (patient), and referenced resources such as Practitioner, PractitionerRole, Organization, RelatedPerson, Device, and use-case–specific content.
-[MedComDocumentBundle](./StructureDefinition-medcom-document-bundle.html) is a Bundle resource defined to be of the type 'document'. All profiles included in a message shall be referenced from the entry element in the profile, with a Composition as the first resource.
+##### MedComDocument Profiles
+You will find a list of all MedCom Document profiles in the "Profiles" tab in the menu.
-__Note:__ Be aware that entries in a document in general are unordered.
+##### Resource Identifiers in MedCom FHIR Documents
-##### MedComDocumentCompostition
+In FHIR, `Resource.identifier` is intended to capture business identifiers that remain constant across system boundaries, which differs from `Resource.id`, the internal technical identifier used within a single FHIR Bundle.
+All resources included in a MedCom FHIR document **MUST** carry an `identifier` element consisting of both a `system` and a `value`. The identifier SHALL be globally unique, persistent, and stable over time. This means that the identifier **MUST NOT** change as long as the resource represents the same underlying real-world entity or dataset. For example, a Patient resource will always carry the same civil registration number (CPR) as its identifier.
-When the Bundle is of the type 'document', the [MedComDocumentCompostition](./StructureDefinition-medcom-document-composition.html) resource must be the first resource. The resource creates the structure for the document and references the relevant clinical information.
+**Global uniqueness:** To ensure global uniqueness, implementations may for example use UUIDv4 or UUIDv5. Use authoritative identifiers when available, such as CPR number or SOR codes.
-##### MedComDocumentOrganization
-
-The [MedComDocumentOrganization](./StructureDefinition-medcom-document-organization.html) profile inherits from MedComCoreOrganization and is used to describe author organization. The resource constrains the MedComCoreOrganization profile to contain a SOR identifier and a name.
-
-##### MedComDocumentPatient
-
-The [MedComDocumentPatient](./StructureDefinition-medcom-document-patient.html) profile desribes the basic requirements for information about citizens and patients when exhancging a document. The profile inherits from DkCorePatient and furhter limit the requirements, e.g. may documents only be exchanged for patients with a CPR-number. To limit the MustSupport elements, this profiles does not inherit from MedComCorePatient.
-
-##### MedComDocumentPractitioner
-
-The [MedComDocumentPractitioner](./StructureDefinition-medcom-document-practitioner.html) profile inherits from MedComCorePractitioner and further requires a given and family name to be present.
-
-##### MedComDocumentReference
-
-The [MedComDocumentReference](./StructureDefinition-medcom-documentreference.html) profile should not be exchanged, but can be used for internal validation of the metadata associated with a document, as the DocumentReference contains the same information as the IHE XDS metadata standard.
-
-#### General document assumptions
+**Persistence across snapshots:** Even if a document is re-created or updated, resources representing the same entity (e.g., Patient, Practitioner, Organization, Encounter) **MUST** retain their identifier.
**Bundle.identifier:** Once a document is assembled into a Bundle, the document is immutable, meaning its content cannot be changed, and the document id (Bundle.identifier) can never be reused.
+##### XML and JSON
**XML and JSON:** Note that the document may be represented in either XML or JSON and interconverted between these or have its character encoding changed, all the while remaining the same document.
-**Narrative:** It is a key element in documents that they contain a narrative text. The requirements concerning the narrative text, follows the [recommendations from HL7 for narrative text](https://hl7.org/fhir/R4/documents.html#presentation). This states that there must be narrative text included in the subject resource, which is the Patient resource in this IG, the Composition resource and for each Composition.section.text.
+#### Terminology IG and metadata IG
+In [MedCom Terminology IG](http://medcomfhir.dk/ig/terminology/) all referenced MedCom Terminology CodeSystems and ValueSets developed by MedCom can be found.
-#### Terminology
-On [MedCom Terminology IG](http://medcomfhir.dk/ig/terminology/) all referenced CodeSystem and ValueSets developed by MedCom can be found.
+In MedCom [Dk Terminology for XDS Metadata](https://medcomfhir.dk/ig/xdsmetadata/) all MedCom CodeSystems and ValueSets related to metadata.
#### Dependencies
-This IG has a dependency to the [MedComCore IG](http://medcomfhir.dk/ig/core/) and [DK-core](https://hl7.dk/fhir/core/) v. 3.2.0, defined by [HL7 Denmark](https://hl7.dk/).
+Besides Terminology and metadata IGs, this IG has a dependency to the [MedComCore IG](http://medcomfhir.dk/ig/core/), [DK-core](https://hl7.dk/fhir/core/), defined by [HL7 Denmark](https://hl7.dk/) and [IHE MHD](https://profiles.ihe.net/ITI/MHD/). **Note** that the IG versions linked may be newer than the versions used as dependencies in this implementation guide. For the exact dependency versions applied, see the **Dependencies** tab in the top menu under **More**.
### Documentation
+[More information about MedCom Document](https://medcomdk.github.io/dk-medcom-document/) can be found here. MedCom document profiles does not alone constitute a standard.
-[More information about MedCom Document](https://medcomdk.github.io/dk-medcom-document/) can be found here. MedCom document profiles does not alone constitute a standard, why the documentation is limited.
-
-### Governance
+### Governance and guidance
+FHIR profiles are managed under MedCom: [Source code](https://github.com/medcomdk/dk-medcom-document).
-FHIR profiles are managed under MedCom: [Source code](https://github.com/medcomdk/dk-medcom-document).
+A description of governance and guidance for MedCom's FHIR standards, can be found on the [MedCom Landing Page](https://medcomdk.github.io/MedComLandingPage).
-#### Quality Assurance Report
+The MedCom FHIR landing page provides a overview of governance requirements that apply to MedCom’s FHIR standards. This includes fx the mandatory rules for interpreting MustSupport, the formal validation requirements that implementers must follow, the expectations for producing narrative texts and governance for how MedCom Terminology is versioned. In addition, the governance section outlines the rules for MedCom FHIR Messaging and Document Sharing, including requirements for fx message flow and envelope usage.
-In the Quality Assurance report (QA-report) for this IG, there is an error with the following description: *Reference is remote which isn’t supported by the specified aggregation mode(s) for the reference (bundled)*. The error occurs when creating instances of the profiles and is due to some elements having a Bundled flag {b}, however the referenced profile is not included in a Bundle in an instance, since the instance only represents a part of the entire message. This should not influence the implementation by IT-vendors.
+The landing page also offers help to developers to understand how to work with MedCom’s FHIR standards. This includes a guide of how to read an Implementation Guide. Users will also find instructions on how to use some of the required tools, such as validation setup and how to use Touchstone.
### Contact
diff --git a/input/sushi-ignoreErrors.txt b/input/sushi-ignoreErrors.txt
new file mode 100644
index 0000000..5f41dc5
--- /dev/null
+++ b/input/sushi-ignoreErrors.txt
@@ -0,0 +1,14 @@
+== Suppressed errors ==
+# Link to sushi desciption: https://fshschool.org/docs/sushi/project/#using-the-hl7-ig-publisher-and-auto-builder
+# Suppresses this error as IG Publisher autogenerates narratives after SUSHI has run.
+Element Patient.text has minimum cardinality 1 but occurs 0 time(s).
+Element CareTeam.text has minimum cardinality 1 but occurs 0 time(s).
+Element DiagnosticReport.text has minimum cardinality 1 but occurs 0 time(s).
+Element Encounter.text has minimum cardinality 1 but occurs 0 time(s).
+Element Media.text has minimum cardinality 1 but occurs 0 time(s).
+Element Observation.text has minimum cardinality 1 but occurs 0 time(s).
+Element Organization.text has minimum cardinality 1 but occurs 0 time(s).
+Element Practitioner.text has minimum cardinality 1 but occurs 0 time(s).
+Element PractitionerRole.text has minimum cardinality 1 but occurs 0 time(s).
+Element DocumentReference.text has minimum cardinality 1 but occurs 0 time(s).
+Element Composition.text has minimum cardinality 1 but occurs 0 time(s).
diff --git a/out/puml/MedComDocument/DocumentModel.svg b/out/puml/MedComDocument/DocumentModel.svg
new file mode 100644
index 0000000..846fe80
--- /dev/null
+++ b/out/puml/MedComDocument/DocumentModel.svg
@@ -0,0 +1 @@
+
\ No newline at end of file
diff --git a/puml/MedComDocument.puml b/puml/MedComDocument.puml
index ba382f2..3b39173 100644
--- a/puml/MedComDocument.puml
+++ b/puml/MedComDocument.puml
@@ -2,18 +2,38 @@
hide empty members
-class "MedComDocumentBundle" as document
-class "MedComDocumentComposition" as composition
+class "MedComDocumentBundle" as document <