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.
Describes the type of the alternative record ID.
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 value is set to "https://citsehealth1.dilcis.eu/profile/E-ARK-eHealth1-ROOT.xml".
The `mets/@TYPE` attribute is set to the value "OTHER".
The `mets/@csip:OTHERTYPE` attribute is set to the value "Patient Medical Records".
There SHOULD be a reference to the Submission Agreement associated with the package as the SIP will contain personal data.
`@TYPE` is used with the value "SUBMISSIONAGREEMENT". Example: http://submissionagreement.kb.se/dnr331-1144-2011/20120711/.
Note: It is recommended to use a machine-readable format for a better description of a submission agreement.
For example, the submission agreement developed by Docuteam GmbH http://www.loc.gov/standards/mets/profiles/00000041.xml
A wrapper element that encapsulates the name of the organisation, software and person that originally created the data being transferred. Please note that this might be different from the organisation which has been charged with preparing and sending the SIP to the archives.
It MUST be easy to positively identify the creating organisation (healthcare provider) without which the data has no provenance.
The role of the archvial creator organisation is set to the value "CREATOR".
The type of the archvial creator agent is set to the value "ORGANIZATION".
The name of the organisation(s) that originally created the data being transferred MUST be given.
Please note that this might be different from the organisation which has been charged with preparing and sending the SIP to the archives.
The archival creator agent SHOULD have a note providing a unique identification code for the archival creator.
As permitted by national identification systems for healthcare providers submitting Patient Medical Records, an identifier for the provider should be provided.
The archival creator agent notetype has a value of "IDENTIFICATIONCODE".
There MUST be a reference to a metadata file held in the the metadata/descriptive folder of the package. At minimum this MUST be a Patient Manifest of Patient Names and unique personal identifiers. It CAN be a more detailed resource such as the FHIR Patient resource ‘FHIR.Patient’.
There MUST be reference() to the descriptive metadata file(s) located in the “metadata” section of the IP.
The value for the metadata type is set to "OTHER".
Specifies the type of metadata used for the Patient Manifest.
For example the value will be “FHIR.Patient” if the FHIR Patient resource is used.
The eHealth1 root 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 should 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 is placed in a representation folder described with a representation METS document.
Only a single file section (`<fileSec>`) element MUST be present.
The value of the attribute `mets/fileSec/fileGrp/@csip:CONTENTINFORMATIONTYPE` is set to "citsehpj_v2_0".
The eHealth1 root structMap element must comply with structMap requirements in the CSIP profile.
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