You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This repository contains the infrastructure and code required to deliver letters digitally that would traditionally be printed and posted.
7
+
8
+
NHS Trusts currently generate a high volume of letters for patients and other care providers, most of which are still sent in printed form. This project enables those letters to be delivered through the NHS App in digital form, with a fallback to printed letter.
5
9
6
10
## Table of Contents
7
11
8
12
-[NHS Notify Digital Letters](#nhs-notify-digital-letters)
9
-
-[Table of Contents](#table-of-contents)
10
-
-[Documentation](#documentation)
11
13
-[Setup](#setup)
12
14
-[Prerequisites](#prerequisites)
13
15
-[Configuration](#configuration)
14
16
-[Usage](#usage)
15
17
-[Testing](#testing)
16
18
-[Design](#design)
17
19
-[Diagrams](#diagrams)
18
-
-[Modularity](#modularity)
19
-
-[Contributing](#contributing)
20
20
-[Contacts](#contacts)
21
21
-[Licence](#licence)
22
22
23
-
## Documentation
24
-
25
-
-[Built](/)
26
-
-[Source](/docs/README.md)
27
-
28
23
## Setup
29
24
30
-
By including preferably a one-liner or if necessary a set of clear CLI instructions we improve user experience. This should be a frictionless installation process that works on various operating systems (macOS, Linux, Windows WSL) and handles all the dependencies.
31
-
32
25
Clone the repository
33
26
34
27
```shell
@@ -47,7 +40,7 @@ make debug
47
40
48
41
The following software packages, or their equivalents, are expected to be installed and configured:
49
42
50
-
-[Docker](https://www.docker.com/) container runtime or a compatible tool, e.g. [Podman](https://podman.io/),
43
+
-[Docker](https://www.docker.com/) container runtime or a compatible tool, e.g. [Podman](https://podman.io/),[Rancher](https://rancherdesktop.io/)
51
44
-[asdf](https://asdf-vm.com/) version manager,
52
45
-[GNU make](https://www.gnu.org/software/make/) 3.82 or later,
53
46
@@ -79,8 +72,6 @@ make config
79
72
80
73
## Usage
81
74
82
-
After a successful installation, provide an informative example of how this project can be used. Additional code snippets, screenshots and demos work well in this space. You may also link to the other documentation resources, e.g. the [User Guide](./docs/user-guide.md) to demonstrate more use cases and to show more features.
83
-
84
75
### Testing
85
76
86
77
There are `make` tasks for you to configure to run your tests. Run `make test` to see how they work. You should be able to use the same entry points for local development as in your CI pipeline.
@@ -89,44 +80,16 @@ There are `make` tasks for you to configure to run your tests. Run `make test`
89
80
90
81
### Diagrams
91
82
92
-
The [C4 model](https://c4model.com/) is a simple and intuitive way to create software architecture diagrams that are clear, consistent, scalable and most importantly collaborative. This should result in documenting all the system interfaces, external dependencies and integration points.
The source for diagrams should be in Git for change control and review purposes. Recommendations are [draw.io](https://app.diagrams.net/) (example above in [docs](.docs/diagrams/) folder) and [Mermaids](https://github.com/mermaid-js/mermaid). Here is an example Mermaids sequence diagram:
97
-
98
-
```mermaid
99
-
sequenceDiagram
100
-
User->>+Service: GET /users?params=...
101
-
Service->>Service: auth request
102
-
Service->>Database: get all users
103
-
Database-->>Service: list of users
104
-
Service->>Service: filter users
105
-
Service-->>-User: list[User]
106
-
```
107
-
108
-
### Modularity
109
-
110
-
Most of the projects are built with customisability and extendability in mind. At a minimum, this can be achieved by implementing service level configuration options and settings. The intention of this section is to show how this can be used. If the system processes data, you could mention here for example how the input is prepared for testing - anonymised, synthetic or live data.
111
-
112
-
## Contributing
113
-
114
-
Describe or link templates on how to raise an issue, feature request or make a contribution to the codebase. Reference the other documentation files, like
115
-
116
-
- Environment setup for contribution, i.e. `CONTRIBUTING.md`
117
-
- Coding standards, branching, linting, practices for development and testing
118
-
- Release process, versioning, changelog
119
-
- Backlog, board, roadmap, ways of working
120
-
- High-level requirements, guiding principles, decision records, etc.
Provide a way to contact the owners of this project. It can be a team, an individual or information on the means of getting in touch via active communication channels, e.g. opening a GitHub discussion, raising an issue, etc.
The source code for the repository's documentation can be found under [/docs](docs) and is deployed by the CD pipeline to [NHS Notify Digital Letters](https://nhsdigital.github.io/nhs-notify-digital-letters).
0 commit comments