> For the complete documentation index, see [llms.txt](https://i4trust.ishare.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://i4trust.ishare.eu/open-call-1/manuspace.md).

# MANUSPACE

Trusted Data Sharing in Pharmaceutical Contract Manufacturing

In today’s hyper-competitive pharmaceutical and biotechnology sectors, the challenges of data sharing, compliance, and operational efficiency are not only technologically outdated but also represent a direct cost to businesses. The involvement of multiple external partners, such as Contract Manufacturing Organizations (CMOs), further complicates the issue of data security, posing risks of severe financial penalties and damage to brand reputation. This outdated legacy system creates data silos, hindering effective decision-making in the industry.&#x20;

MANUSPACE addresses these challenges by establishing a digital trust ecosystem that enables the secure and efficient sharing of data across organisational boundaries. MANUSPACE leverages the i4Trust robust security protocol, empowered by iSHARE, a cross-domain [Trust Framework](https://framework.ishare.eu/). This ensures all data sharing is secure, authorised, and compliant with standardised protocols. With the use of FIWARE's Orion Context Broker and Keyrock Authorization Registry for user authentication and authorisation, it ensures secure access to specific data types. Meanwhile, [iSHARE Participant Registry](https://trustbok.ishare.eu/apply-ishare/participant-registry) serves as the Trust Anchor, validating and certifying all participants in the data space to ensure data sovereignty within organisational policies.&#x20;

To join the MANUSPACE Data Space, entities in the pharmaceutical and biotechnology sectors must register with the iSHARE Participant Registry, agree to terms of use, and undergo a verification process.&#x20;

Learn more about the MANUSPACE in the Impact Story.

{% file src="/files/TFZO6zmZ4A2ZGcVScaww" %}

#### Contributors:

<table data-view="cards"><thead><tr><th></th><th></th><th></th></tr></thead><tbody><tr><td><img src="https://1503555140-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2jEu4WMcHi3W2Hls1ewh%2Fuploads%2Fc1rFPNiWiK7pM6DPQRJm%2FServBLOCK.png?alt=media&amp;token=ad774e99-319a-4ef5-a32a-24f50fb8b365" alt="" data-size="original"></td><td></td><td></td></tr><tr><td></td><td></td><td><img src="https://1503555140-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2jEu4WMcHi3W2Hls1ewh%2Fuploads%2FCrkEVUY18Il7HTm98oRl%2FIRISH%20MANUFACTURING%20RESEARCH.png?alt=media&amp;token=2232cfbf-d12d-4ffe-aeaa-909ef722220a" alt="" data-size="original"></td></tr><tr><td><img src="https://1503555140-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2jEu4WMcHi3W2Hls1ewh%2Fuploads%2Fu7m5J4HWf9VY0OP3QlN3%2Funison%20process%20solutions.svg?alt=media&amp;token=c21a4aa8-b101-4be8-84e1-928dcf406760" alt="" data-size="original"></td><td></td><td></td></tr><tr><td><img src="https://1503555140-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2jEu4WMcHi3W2Hls1ewh%2Fuploads%2FbfBX7XU68hTWvNAIElGY%2Fplantquest.webp?alt=media&amp;token=db96899e-3534-4ecc-99c2-2dda8ab6e99d" alt="" data-size="original"></td><td></td><td></td></tr><tr><td><img src="https://1503555140-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2jEu4WMcHi3W2Hls1ewh%2Fuploads%2FjvPZP81ZvhIXIoS5fgxr%2FNEXA%20EAM.png?alt=media&amp;token=ae3848c7-15a9-4b5a-b027-9cdd34691e1d" alt="" data-size="original"></td><td></td><td></td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://i4trust.ishare.eu/open-call-1/manuspace.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
