This profile together with the E-ARK CITS eHealth1 document describes the root METS document for an IP conforming to the E-ARK CITS eHealth1.
An extension schema with the added attributes for use in this profile.
The schema is used with a namespace prefix of sip.
An extension schema with the added attributes for use in this profile.
The schema is identified using the namespace prefix csip.
The filepath must be decoded consistently throughout all file references within the information package.
Describes the type of the alternative record ID.
Describes the type of the alternative record ID.
Describes the type of a note for an agent.
Lists the names of specific E-ARK content information type specifications supported or maintained in this METS profile.
Declares the categorical classification of package content.
Describes the uses of the file group `<fileGrp>` that are supported by the profile.
Own names should be placed in an own extending vocabulary.
Describes the extra terms supported by this profile.
Own names should be placed in an own extending vocabulary.
Describes the status of the descriptive metadata section (dmdSec) which is supported by the profile.
Valid values for the mime types of referenced files.
Describes the type of the structural map `<structMap>` that is supported by the profile.
Own types should be placed in an own extending vocabulary.
Describes the label of the structural map that is supported by the profile.
Own labels should be placed in an own extending vocabulary.
The `mets/@OBJID` attribute is mandatory, its value is a string identifier for the METS document.
. For a representation level METS document, this value records the name of the representation (i.e. the name of the top-level representation folder. For example this could be: “Patient_Record_Submission”.
The value is set to "https://citsehealth1.dilcis.eu/profile/E-ARK-eHealth1-REPRESENTATION.xml".
The `mets/@TYPE` attribute is set to the value "OTHER".
The `mets/@csip:OTHERTYPE` attribute is set to the value "Patient Medical Records".
The `mets/@csip:CONTENTINFORMATIONTYPE` attribute is set to the value "citsehpj_v2_0".
The eHealth1 representation METS metsHdr element should comply with metsHdr requirements in the SIP profile.
The SIP dmdSec element should comply withdmdSec requirements in the CSIP profile
The eHealth1 representation METS document amdSec element should comply with amdSec requirements in the CSIP profile.
In eHealth1 it is required that any rights or digital provenance metadata that is general to the package can be held within the root metadata folder and that any rights or digital provenance metadata that is specific to the data held in the representation should be held in the representation metadata folder.
The transferred content within the representation is referenced from the file section in different file group elements. Only a single file section (`<fileSec>`) element should be present.
Representation of the Patient Case structural hierarchy is only possible if the file section (`<fileSec>`) is present in the representation.
The representation (Patient Document) file groups contain the file elements that describe the Patient Documents, the Patient Administrative and the Patient Clinical Information.
The hierarchical structure of the Patient Medical Records within the CITS eHealth1 requires that Documents groups of files that form a single intellectual entity) can be described through the structMap (`<div>`) element.
The value in the `mets/fileSec/fileGrp/@USE` is the name of the folder structure to the data, e.g "data/Patient_ID/Case_ID/Document_ID".
The value of the attribute the `mets/fileSec/fileGrp/@csip:CONTENTINFORMATIONTYPE` is set to "citsehpj_v2_0".
A file may comprise one or more subsidiary byte streams (e.g. an MPEG4 file might contain separate audio and video streams, each of which is associated with technical metadata).
The repeatable (`<stream>`) element provides a mechanism to record the existence of separate datastreams within a particular file and to associate (`<dmdSec>`) and (`<amdSec>`) with them.
A unique xml:id for this object across the package.
The IANA mime type for the referenced byte stream.
If an identifier for the byte stream was supplied by the owner, it can be recorded in this attribute.
If administrative metadata has been provided for the byte stream this attribute refers to the streams's administrative metadata by ID.
For the administrativ description of the byte stream the PREMIS standard is recommended.
Each representation METS file must include ONE structural map (`<structMap>`) element as exactly as described here.
Institutions can add their own additional custom structural maps as separate `<structMap>` sections.
The `mets/structMap/@LABEL` attribute value is set to “eHealth1” from the vocabulary.
An `xml:id` identifier for the structural description (structMap) used for internal package references. It must be unique within the package.
Within eHealth1 all patient records must be held within a data folder within a minimum single representation and described in the structural map within a single sub-division. There are no files contained in the data division.
Mandatory, 'xml:id' identifier must be unique within the package.
The representations's data division '<div>` element must have the `@LABEL` attribute value "Data" taken from the vocabulary.
There must be a discrete 'div' element for each patient record.
The patient record division `<div>` element's `@LABEL` attribute value must be "Patient Record" as taken from the vocabulary.
Mandatory, 'xml:id' must be unique wqithin the package.
Each Patient Case contains Documents that are related in some way (e.g. chronologically and/or share a particular set of diagnoses and/or treatments).
A Patient Case is a folder located in the ”data/patient_record” folder within the representation and may contain any number of Sub-cases and Documents.
Every representation must contain at least one Patient Case. A Case is represented within a third level sub-division.
Mandatory, `xml:id` identifier must be unique within the package.
The package's patient case division `<div>` element must have the `@LABEL` attribute value "Case", taken from the vocabulary.
Each Patient Case MAY contain individual Data Files that are related logically and together form Documents (e.g. a book, video, image and annotation, document and audio notes).
Mandatory, `xml:id` identifier must be unique within the package.
The package's Patient Documentation division `<div>` element must have the `@LABEL` attribute value "Document", taken from the vocabulary.
All file groups containing content described in the package are referenced via the relevant file group identifiers. One file group reference per fptr-element.
The pointer to the identifier for the file group containing the data files.
Each Patient Sub-case contains Documents that are related in some way (e.g. chronologically and/or share a particular set of diagnoses and/or treatments).
A Patient Sub-case is a folder located in a Case folder within the representation and must contain at least one Document.
Mandatory, `xml:id` identifier must be unique within the package.
The package's patient sub-case division `<div>` element must have the `@LABEL` attribute value "Subcase", taken from the vocabulary.
Each Patient sub-case can contain individual Data Files that are related logically and together form Documents (e.g. a book, video, image and annotation, document and audio notes).
Mandatory, `xml:id` identifier must be unique within the package.
The package's patient sub-case/documentation division `<div>` element must have the `@LABEL` attribute value "Document", taken from the vocabulary.
The pointer to the identifier for the file group containing the data files.
The pointer to the identifier for the file group containing the data files.
Section not defined or used in CSIP, additional own uses may occur.
Information regarding the structural links is found in the METS Primer
Section not defined or used in CSIP, additional own uses may occur.
Information regarding the behavior section is found in the METS Primer
Requirements not stated in CITS eHealth1
Requirements not stated in CITS eHealth1
Requirements not stated in CITS eHealth1
Currently no tool