Template : LUXHeaderConstraints

Template : 1.3.182.11.1

Template Name: LUXHeaderConstraints

Template ID: 1.3.182.11.1

Parent: cda-POCDMT000040ClinicalDocument

Package: luxh

List of related constraints

  • The ClinicalDocument/title element shall be present and specifies the name used for this document. It shall not be nullFlavored more..
  • The realm code indicates the localization of the clinical document using this specification. The code shall be filled with “LUâ€� (Code from ISO 3166-1-alpha-2) STATIC more..
  • A ClinicalDocument/typeId element shall be present having the following values: @root=â€�2.16.840.1.113883.1.3â€� @extension=â€� POCD_HD000040â€� more..
  • To indicate conformance to the general header specifications of the clinical document in Luxemburg defined in this specification document, the ClinicalDocument/templateId shall be present with the following value: @root=â€�1.3.182.11.1â€� more..
  • To indicate conformance to level 1 (which also asserts compliance with all general or non-level specific constraints), ClinicalDocument/templateId elements may be present with the following value: @root=â€�2.16.840.1.113883.10.20.10â€� more..
  • To indicate conformance to level 2 features (which also asserts compliance with level 1 requirements and asserts the presence of section codes), ClinicalDocument/templateId elements may be present with the following value: @root=â€�2.16.840.1.113883.10.20.20â€� more..
  • To indicate conformance to level 3 features (which also asserts compliance with level 2 requirements and asserts the presence of CDA entries in some sections), ClinicalDocument/templateId elements may be present with the following value: @root=â€�2.16.840.1.113883.10.20.30â€� more..
  • For a unstructured document, to indicate conformance to the specifications of the profile IHE XDS-SD published by IHE international in the ITI Technical framework, ClinicalDocument/templateId elements may be present with the following value: @root=â€�1.3.6.1.4.1.19376.1.2.20â€� more..
  • The ClinicalDocument/id element shall not have a nullFlavor attribute more..
  • assigningAuthority and displayable may be omitted more..
  • The ClinicalDocument/code element specifies the type of the clinical document. Values are defined in the value set eSanté_DocType with codeSystem=2.16.840.1.113883.6.1 more..
  • The ClinicalDocument/code element shall not have a nullFlavor attribute more..
  • The ClinicalDocument/code/ @codeSystemName if present shall have the value "LOINC" more..
  • The ClinicalDocument/title element shall not have a nullFlavor attribute more..
  • The ClinicalDocument/effectiveTime element shall be present and not be nullFlavored. It specifies the creation time of the document. All history and physical documents authored by direct input to a computer system should record an effectiveTime that is precise to the second. When authored in other ways, for example, by filling out a paper form that is then transferred into an EHR system, the precision of effectiveTime may be less than to the second more..
  • The ClinicalDocument/effectiveTime shall have the format YYYYMMDDhhmmss[+/-]HHMM more..
  • The ClinicalDocument/confidentialityCode shall be present with @code=â€�Nâ€�@displayName=â€�Normalâ€�@codeSystem=â€�2.16.840.1.113883.5.25â€�@codeSystemName=â€�HL7:Confidentialityâ€� more..
  • The ClinicalDocument/languageCode shall be present and not be nullFlavored more..
  • Possible values for the languageCode@code shall be taken from the value set eSanté_LanguageCode, DYNAMIC. In this value set, the pattern is nn-CC where nn is a legal ISO-639-1 language code in lowercase and CC a legal ISO-3166-2 country code in uppercase more..
  • ClinicalDocument/setId and ClinicalDocument/versionNumber shall either be given both or both shall be omitted more..
  • The ClinicalDocument/setId element shall not have a nullFlavor attribute more..
  • The ClinicalDocument/versionNumber element shall not have a nullFlavor attribute more..
  • Only one ClinicalDocument/recordTarget shall be present more..
  • A document can have two relatedDocument entries where one shall be of typeCode “RPLCâ€� and the other of typeCode “XFRMâ€� more..
  • The custodian element shall be present more..
  • The informant may be present more..
  • The authenticator may be present more..
  • The authorization element need not to be used more..