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 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 uses of the structutal map divisions label that are supported by the 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.
Describes the type of metadata described in 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 the package METS document, this should be the name/ID of the package, i.e. the name of the package root folder.
For a representation level METS document this value records the repname/ID of the representation, i.e. the name of the top-level representation folder.
The value is set to "https://earkehealth1.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 "eHealth1".
The eHealth1 representation METS metsHdr element should comply with metsHdr requirements in the SIP profile.
Used to reference Case Patient Clinical Information held in the metadata/descriptive folder of the representation.
There is one dmdSec present for each descriptive metadata file located in the “repname/metadata” section of the representation.
An `xml:id` identifier for the descriptive metadata section (`<dmdSec>`) used for internal package references. It must be unique within the package.
Creation date of the descriptive metadata in this section.
Indicates the status of the package using a fixed vocabulary.
There MUST be a reference to the descriptive metadata file located in the folder “repname/metadata” section of the representation.
The value for the metadata type is set to "OTHER".
Specifies the type of metadata used for Patient Clinical Information.
For example the value will be “FHIR.Condition” if the FHIR Condition resource is used.
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 file groups contain the file elements that describe the Case digital objects
The file group (`<fileGrp>`) contains the file elements which describe the digital objects. The hierarchical structure of the Patient Medical Records within the CITS eHealth1 requires that digital objects (groups of files that form a single intellectual entity) can be described through the structMap (`<div>`) element.
If administrative metadata has been provided at a representation level (i.e. there is rights and/or digital provenance metadata that is specific to the patient data) then this attribute refers to the (`<amdSec>`) of the representation mets.xml by ID.
All Patient Personal Clinical Information included in the representation MUST be referenced from a file group element with ‘mets/fileSec/fileGrp/@USE’ attribute “Patient Clinical Information”
For example as can be described using the resource FHIR.Condition
The value of the attribute the `mets/fileSec/fileGrp/@csip:CONTENTINFORMATIONTYPE` is set to "OTHER".
The value of the attribute `mets/fileSec/fileGrp/@csip:OTHERCONTENTINFORMATIONTYPE` is set to "eHealth1".
The value in the `mets/fileSec/fileGrp/@USE` is the name of the folder structure to the data, e.g "Representations/submission/data".
An `xml:id` identifier for the file group used for internal package references. It must be unique within the package.
The file group (`<fileGrp>`) contains all the file elements which describe the digital objects.
Each file element describes one of the Case digital objects
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 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.
If descriptive metadata has been provided for the stream this attribute refers to the streams's descriptive metadata by ID.
There MUST be one structural map following the requirements in the E-ARK SIP and thus E-ARK CSIP present.
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/@TYPE` attribute must take the value “PHYSICAL” from the vocabulary.
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.
The structural map comprises a single division.
Mandatory, `xml:id` identifier must be unique within the package.
The package's top-level structural division `<div>` element's `@LABEL` attribute value must be identical to the package identifier, i.e. the same value as the `mets/@OBJID` attribute.
The metadata referenced in the administrative and/or descriptive metadata section is described in the structural map with one sub division.
Mandatory, `xml:id` identifier must be unique within the package.
The metadata division `<div>` element's `@LABEL` attribute value must be "Metadata".
When there is administrative metadata and the amdSec is present, all administrative metadata MUST be referenced via the administrative sections different identifiers.
All of the `<amdSec>` identifiers are listed in a single `@ADMID` using spaces as delimiters.
When there are descriptive metadata and one or more dmdSec is present, all descriptive metadata MUST be referenced via the descriptive section identifiers.
Every `<dmdSec>` identifier is listed in a single `@DMDID` attribute using spaces as delimiters.
The documentation referenced in the file section file groups is described in the structural map with one sub division.
Mandatory, `xml:id` identifier must be unique within the package.
The documentation division `<div>` element in the package uses the value "Documentation" from the vocabulary as the value for the `@LABEL` attribute.
All file groups containing documentation described in the package are referenced via the relevant file group identifiers. There MUST be one file group reference per `<fptr>` element.
A reference, by ID, to the "Documentation" file group.
Related to the requirement which describes the "Documentation" file group in CSIP and the requirement which describes the file group identifier.
Within eHealth1 patient Cases 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 within the data division.
Mandatory, `xml:id` identifier must be unique within the package.
The package's data division `<div>` element must have the `@LABEL` attribute value "DATA", taken from the vocabulary.
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” folder within the representation and may contain any number of Sub-cases and Documents.
Every package must contain at least one Patient Case. A Case is represented within a second 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.
Data Files are components which contain data and have associated MIME file types.
A Data File can be a single bit stream or can encapsulate bit streams and attributes according to a standard such as a DICOM or MP4.
Mandatory, `xml:id` identifier must be unique within the package.
The package's patient case/documentation/data file division `<div>` element must have the `@LABEL` attribute value "DATAFILE", 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.
Data Files are components which contain data and have associated MIME file types.
A Data File can be a single bit stream or can encapsulate bit streams and attributes according to a standard such as a DICOM or MP4.
Mandatory, `xml:id` identifier must be unique within the package.
The package's sub-case/documentation/data file division `<div>` element must have the `@LABEL` attribute value "DATAFILE", taken from the vocabulary.
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