Pharmaceutical traceability for serialized product records and partner data.
Explore Connect RXSECURITY AND STANDARDS
EDI security and standards.
Clear responsibilities.
Review access, document handling and security requirements for an EDI processing implementation, with evidence matched to your procurement needs.

DATA
FURTHER
GOOD
01 / THE WORK, MADE CLEAR
Know where the document goes.
EDI messages can include commercially sensitive customer, supplier and pricing information. Identify where documents enter the workflow, who can access the content and how the resulting data reaches the destination. Those boundaries determine the questions your security team should ask.
- 01
Access
Identify the users, services and partner connections that need access.
- 02
Data handling
Agree retention, logging and the treatment of sensitive fields.
- 03
Evidence
Request documentation that supports the controls required by your organization.
02 / THE CONNECTION THAT MATTERS
Distinguish standards from assurance.
| Context | What matters | The handoff |
|---|---|---|
| X12 / UN/EDIFACT | Business-message standards | Transaction and version coverage |
| ISO/IEC 27001 | Information-security management requirements | A valid certificate and scope, if certification is required |
| SOC 2 | An attestation report on scoped controls | Report type, period and covered services |

03 / BUILT AROUND YOUR WORK
Ask for the evidence your review requires.
Certification, an attestation report and adherence to a technical standard are different things. This page explains procurement requirements; it does not assert that Maltexi holds ISO certification or a SOC 2 report. Share your security questionnaire so the team can confirm which evidence and controls are available for the proposed implementation.
Start a focused conversationA CLEARER PICTURE
Good questions.
Clear answers.
Does EDI compatibility imply a security certification?
No. Message-format compatibility describes document processing. Security assurance requires separate evidence for the service and scope being evaluated.
Should examples include sensitive production information?
Use anonymized documents for an initial review. Agree an appropriate channel before sharing sensitive data.
ONE FAMILY. FOCUSED PRODUCTS.
Built for what connects.
Exchange business files between your systems and trading partners.
Explore File ExchangeLET’S CONNECT
Bring your documents.
Let’s make the next step clear.
Your systems. Your partners. The task your business needs to complete.
Discuss your workflow