Medspiration â System Requirements Document - Data User Element
Medspiration â System Requirements Document - Data User Element
Medspiration â System Requirements Document - Data User Element
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
<strong>Medspiration</strong><br />
<strong>System</strong> <strong>Requirements</strong> <strong>Document</strong><br />
PP MDB at GDAC.<br />
MED-SOC-RS-001_1<br />
Issue F<br />
SR.EXT.CTR.0320/I The MDB records shall be formatted as XML files with respect to the<br />
DTD provided in Annex 3 (“MDB records format”).<br />
SR.EXT.CTR.0330/I The generated MDB data records shall be sent to the GHRSST-PP<br />
MDB through ftp.<br />
It is stated in GDS that both email or ftp may be used for the delivery. Only ftp will be<br />
considered within <strong>Medspiration</strong> since it provides better control on delivery checking and<br />
delays, and for consistency with delivery of MMR-FR and Error logs.<br />
SR.EXT.CTR.0340/I An error message (event code 9) shall be received from the central<br />
error log system if a <strong>Medspiration</strong> MDB record is rejected by the GHRSST MDB.<br />
4.2.5 Master Metadata Repository<br />
SR.EXT.CTR.0410/I The <strong>Medspiration</strong> system shall be interfaced with the Master<br />
Metadata Repository <strong>System</strong>.<br />
SR.EXT.CTR.0420/I Each MMR-FR shall be formatted in XML format, following the DTD<br />
in annex 5 (“format of MMR files”).<br />
SR.EXT.CTR.0430/I Each MMR-FR shall be delivered to the Master Metadata Repository<br />
by ftp push.<br />
It is stated in GDS that both email or ftp may be used for the delivery. Only ftp will be<br />
considered within <strong>Medspiration</strong> since it provides better control on delivery checking and<br />
delays, and for consistency with delivery of MDB records and Error logs.<br />
4.2.6 GDS error log system<br />
SR.EXT.CTR.0510/I The <strong>Medspiration</strong> system shall be interfaced with the central<br />
GHRSST-PP error log system, providing it with error messages or receiving error<br />
messages.<br />
SR.EXT.CTR.0520/I Each error log will be formatted in XML format, following the DTD in<br />
annex 4 (“Operation and error messages”).<br />
No format is specified in the GDS (although WP-ID1.3.1 refers to Appendix A7 which only<br />
specifies error codes) for the error messages. Information such as the name of the data<br />
file rejected or ingested shall be included within the error message.<br />
© 2004 SOC Page 66 of 193
Change language