<!-- Derived Markdown alternate of index.md; canonical repository sources and registered evidence retain authority. -->


# NHS Smartcard Printing

Technical architecture, dependencies and connectivity · **Reviewed 20 October 2026**

<blockquote class="governing-question"><p>What hardware, software and connectivity are needed to issue and manage NHS smartcards reliably?</p></blockquote>

Build the design around a supported Windows RA workstation, appropriate readers, the Magicard DoH 300 and Smartcard Connect. Internet-based CIS2 authentication is supported. A successful sign-in alone does not prove that card issuance, electronic personalisation and printing work together. [SRC-002](https://nhs-smartcard-printing-wiki.pages.dev/sources/index.md#src-002), [SRC-003](https://nhs-smartcard-printing-wiki.pages.dev/sources/index.md#src-003)

This independent research wiki helps RA teams, IT support and architects define a deployment and test it. It is organisation-neutral and is not an NHS publication or an operational approval.

## Start with the decision you need to make

- **Plan the system:** read the [architecture](https://nhs-smartcard-printing-wiki.pages.dev/architecture/index.md) and [requirements](https://nhs-smartcard-printing-wiki.pages.dev/requirements/index.md).
- **Prepare a workstation:** use the [hardware and software baseline](https://nhs-smartcard-printing-wiki.pages.dev/workstation/index.md).
- **Configure access:** check [connectivity and browser policies](https://nhs-smartcard-printing-wiki.pages.dev/connectivity/index.md).
- **Choose card and desktop support:** review [Series 10](https://nhs-smartcard-printing-wiki.pages.dev/series-10/index.md) and [virtual desktops](https://nhs-smartcard-printing-wiki.pages.dev/virtual-desktops/index.md).
- **Accept the deployment:** run the [issuance workflow](https://nhs-smartcard-printing-wiki.pages.dev/issuance/index.md) and [acceptance checklist](https://nhs-smartcard-printing-wiki.pages.dev/acceptance/index.md).
- **Investigate a fault:** follow the [support and maintenance guide](https://nhs-smartcard-printing-wiki.pages.dev/operations/index.md).

## Four boundaries to preserve

| Decision | Research position |
|---|---|
| Authentication vs issuance | Validate them as separate activities. |
| Product capability vs NHS support | Apply the current NHS configuration guidance. |
| Published requirement vs local recommendation | The [requirements](https://nhs-smartcard-printing-wiki.pages.dev/requirements/index.md) label each separately. |
| Research verification vs physical testing | Sources were checked; no card was issued during this research. |

```mermaid
flowchart TB
  accTitle: Deployment assurance path
  accDescr: Published guidance informs the chosen configuration, which must pass local acceptance before operational use.
  guidance["Published guidance"] --> setup["Chosen configuration"]
  setup --> tests["Local acceptance"]
  tests --> use["Operational use"]
```

Explore the [source register](https://nhs-smartcard-printing-wiki.pages.dev/sources/index.md), [evidence matrix](https://nhs-smartcard-printing-wiki.pages.dev/evidence-matrix/index.md), [knowledge graph](https://nhs-smartcard-printing-wiki.pages.dev/graph/index.md) or [agent guide](https://nhs-smartcard-printing-wiki.pages.dev/llm-wiki/index.md). The [scope and corrections](https://nhs-smartcard-printing-wiki.pages.dev/scope/index.md) explain what changed from the supplied draft.