[PRM-659] GitHub Org migration changes (nhsconnect -> NHSDigital)

Author: chrisbloe

.github/CODEOWNERS

@@ -0,0 +1 @@
+* @NHSDigital/patient-record-management

.github/workflows/base-java-service-jobs.yml

@@ -137,7 +137,7 @@ jobs:
   deploy_infra:
     name: Deploy Infrastructure
     needs: [build_and_publish]
-    uses: nhsconnect/orphaned-record-continuity-infrastructure/.github/workflows/deploy-stack.yml@v3
+    uses: NHSDigital/orphaned-record-continuity-infrastructure/.github/workflows/deploy-stack.yml@v3
 
     with:
       stack: ${{ inputs.service }}

.github/workflows/base-node-service-jobs.yml

@@ -169,7 +169,7 @@ jobs:
   deploy_infra:
     name: Deploy Infrastructure
     needs: [build_and_publish]
-    uses: nhsconnect/orphaned-record-continuity-infrastructure/.github/workflows/deploy-stack.yml@v3
+    uses: NHSDigital/orphaned-record-continuity-infrastructure/.github/workflows/deploy-stack.yml@v3
     with:
       stack: ${{ inputs.service }}
       environment: ${{ inputs.environment }}

.github/workflows/base-python-service-jobs.yml

@@ -120,7 +120,7 @@ jobs:
     if: ${{ inputs.deploy_infra && inputs.is_deployment }}
     name: Deploy Infrastructure
     needs: [build-and-publish-service]
-    uses: nhsconnect/orphaned-record-continuity-infrastructure/.github/workflows/deploy-stack.yml@v3
+    uses: NHSDigital/orphaned-record-continuity-infrastructure/.github/workflows/deploy-stack.yml@v3
     with:
       stack: ${{ inputs.service }}
       environment: ${{ inputs.environment }}

.github/workflows/service-ci.yml

@@ -47,8 +47,8 @@ jobs:
       - name: Get Changes
         id: get_changes
         run: |
-          git fetch origin ${{ github.event.pull_request.base.ref }}
-          changed=$(git diff --name-only origin/${{ github.event.pull_request.base.ref }}...HEAD | tr '\n' ' ')
+          git fetch origin main
+          changed=$(git diff --name-only origin/main... | tr '\n' ' ')
           echo "changed=$changed" >> $GITHUB_OUTPUT
 
   ehr-repo:

CONTRIBUTING.md

@@ -0,0 +1,27 @@
+# Welcome to the Orphaned Record Continuity contributors guide
+
+Thank you for your interest in improving the codebase.
+
+In this guide you will get an overview of the contribution workflow from creating a PR, reviewing, and merging the PR.
+
+The codebase covers:
+
+- The [Orphaned Record Continuity service](https://digital.nhs.uk/services/orphaned-record-continuity).
+
+To raise an issue, please contact one of the [CODEOWNERS](.github/CODEOWNERS) directly, or raise a PR.
+
+If you're new to GitHub and/or Markdown, GitHub's own [contributor's guide](https://github.com/github/docs/blob/main/.github/CONTRIBUTING.md) provides good signposting on these topics.
+
+## Pull requests and merging
+
+You can't push to the main branch. Therefore, for all changes you will need to create a new branch, and then a pull request to merge said branch into `main`. The [CODEOWNERS](.github/CODEOWNERS) will be nominated as reviewers of your PR by default, but feel free to add other people as well if you think they will have valuable input.
+
+## Contributing guidelines and etiquette
+
+- Preview your Markdown code to make sure the format is not broken.
+- Check grammar, spelling and punctuation - no-one wants to look pedantic by requesting changes due to typos or inconsistent grammar/syntax, but it's only fair to keep this tidy.
+- The codebase is open to the world. This has a few implications:
+  - Nothing in it should be confidential, private to NHSE or include any personal data.
+  - All links should be public.
+  - Consider comments and README.md text: comments in open source repos such as this are not official communications and don't go through the normal approval process for public communication. They can however still be interpreted as official communication, even if not intended as such.
+- Use [inclusive language](https://github.com/NHSDigital/software-engineering-quality-framework/blob/main/inclusive-language.md): avoid terms which cause hurt and offence, including if they have historically been considered industry-standard terms.

services/ehr-out-service/package.json

@@ -70,10 +70,6 @@
     "superagent": "8.0.8",
     "semver": ">=7.5.2"
   },
-  "repository": {
-    "type": "git",
-    "url": "git+https://github.com/nhsconnect/prm-repo-ehr-out-service.git"
-  },
   "jest": {
     "resetModules": true,
     "clearMocks": true,

services/ehr-out-service/sonar-project.properties

@@ -1,5 +1,5 @@
-sonar.projectKey=prm-orphaned-record-continuity_prm-repo-ehr-out-service
-sonar.organization=prm-orphaned-record-continuity
+sonar.projectKey=NHSDigital_orphaned-record-continuity
+sonar.organization=nhsdigital
 
 # This is the name and version displayed in the SonarCloud UI.
 sonar.projectName=prm-repo-ehr-out-service

services/ehr-transfer-service/build.gradle

@@ -169,8 +169,8 @@ spotbugsIntegration {
 
 sonar {
     properties {
-        property 'sonar.projectKey', 'prm-orphaned-record-continuity_prm-repo-ehr-transfer-service'
-        property 'sonar.organization', 'prm-orphaned-record-continuity'
+        property 'sonar.projectKey', 'NHSDigital_orphaned-record-continuity'
+        property 'sonar.organization', 'nhsdigital'
         property 'sonar.host.url', 'https://sonarcloud.io'
     }
 }

services/gp2gp-messenger/README.md

@@ -3,15 +3,15 @@
 This is an implementation of a component to handle the sending of the GP2GP message set used to transfer a patient's Electronic Health Record between GP Practices.
 It uses the GP2GP message format to transfer orphaned and stranded records out of a secure NHS repository.
 
-This component will communicate with the Message Handler Service (MHS) [GitHub nhsconnect/integration-adaptors](https://github.com/nhsconnect/integration-adaptors) and other components being developed by the Orphaned and Stranded Record programme.
+This component will communicate with the Message Handler Service (MHS) using the [NIA MHS Adaptor](https://github.com/NHSDigital/integration-adaptor-mhs) and other components being developed by the Orphaned Record Continuity programme.
 
 The initial version will send health records that are encoded in the HL7 format. A subsequent enhancement will be access to the components of the Health Record so that other services can use this component to send and receive Health Records with the need to implement the encoding and fragmentation strategies of the [GP2GP v2.2a](https://data.developer.nhs.uk/dms/mim/6.3.01/Domains/GP2GP/Document%20files/GP2GP%20IM.htm) message specification.
 
 ## Prerequisites
 
 - [Node](https://nodejs.org/en/download/package-manager/#nvm) - version 14.x
 - [Docker](https://docs.docker.com/install/)
- 
+
 ### AWS helpers
 
 This repository imports shared AWS helpers from [prm-deductions-support-infra](https://github.com/nhsconnect/prm-deductions-support-infra/).
@@ -20,22 +20,26 @@ They can be found `utils` directory after running any task from `tasks` file.
 ## Set up
 
 If you would like to run the app locally, you need to:
+
 1. Run `npm install` to install all node dependencies as per `package.json`.
-2. Set up the env variables and/or copy them into your IDE configurations (`Run -> Edit Configurations ->Environment Variables` in IntelliJ):
-```
-export E2E_TEST_AUTHORIZATION_KEYS_FOR_GP2GP_MESSENGER=auth-key-2
-export REPOSITORY_URI=$IMAGE_REPO_NAME   
-export NHS_SERVICE=gp2gp-messenger
-export SERVICE_URL=http://${NHS_SERVICE}:3000
-export NHS_ENVIRONMENT=local
-export GP2GP_MESSENGER_REPOSITORY_ASID=deduction-asid
-export GP2GP_MESSENGER_REPOSITORY_ODS_CODE=deduction-ods
-```
-- Locally, the variables `GP2GP_MESSENGER_REPOSITORY_ASID`, `GP2GP_MESSENGER_REPOSITORY_ODS_CODE` can be set
-  to any value
+
+1. Set up the env variables and/or copy them into your IDE configurations (`Run -> Edit Configurations ->Environment Variables` in IntelliJ):
+
+    ```bash
+    export E2E_TEST_AUTHORIZATION_KEYS_FOR_GP2GP_MESSENGER=auth-key-2
+    export REPOSITORY_URI=$IMAGE_REPO_NAME   
+    export NHS_SERVICE=gp2gp-messenger
+    export SERVICE_URL=http://${NHS_SERVICE}:3000
+    export NHS_ENVIRONMENT=local
+    export GP2GP_MESSENGER_REPOSITORY_ASID=deduction-asid
+    export GP2GP_MESSENGER_REPOSITORY_ODS_CODE=deduction-ods
+    ```
+
+    > Locally, the variables `GP2GP_MESSENGER_REPOSITORY_ASID`, `GP2GP_MESSENGER_REPOSITORY_ODS_CODE` can be set
+      to any value
 
-3. The app will use a fake MHS when `NHS_ENVIRONMENT` is set to `local` or `dev`. 
- 
+1. The app will use a fake MHS when `NHS_ENVIRONMENT` is set to `local` or `dev`.
+
 ## Running the tests
 
 Run the unit tests by  running `./tasks test_unit`
@@ -46,14 +50,12 @@ Run the integration tests with:
 
 You can also run them with `npm run test:integration` but that will require some additional manual set-up
 
-
 Run the coverage tests (unit test and integration test)
 
 By running `./tasks test_coverage`
 
 or run `npm run test:coverage` on your machine
 
-
 ## Start the app locally
 
 1. Run a development server with `npm run start:local`
@@ -65,7 +67,7 @@ The swagger documentation for the app can be found at `http://localhost:3000/swa
 
 ### Example request
 
-```
+```bash
 curl -X POST "http://localhost:3000/ehr-request" -H "accept: application/json" -H "Authorization: auth-key-1" -H "Content-Type: application/json" -d "{ \"nhsNumber\": \"some-nhs-number\", \"odsCode\": \"some-ods-code\"}"
 ```
 
@@ -75,8 +77,7 @@ Compile the code with `npm run build`, and then start the server with `npm start
 
 ## Config
 
-Ensure you have VPN connection set up to both `dev` and `test` environments:
-[CLICK HERE](https://gpitbjss.atlassian.net/wiki/spaces/TW/pages/1832779966/VPN+for+Deductions+Services)
+Ensure you have VPN connection set up to both `dev` and `test` environments ([see this Confluence page](https://gpitbjss.atlassian.net/wiki/spaces/TW/pages/1832779966/VPN+for+Deductions+Services)).
 
 ## Access to AWS from CLI
 
@@ -89,4 +90,4 @@ As a note, this set-up is based on the README of assume-role [tool](https://gith
 
 ## Assume role with elevated permissions
 
-In order to get sufficient access to work with terraform or AWS CLI, please export secrets from the AWS Access Portal for the environment you are using
+In order to get sufficient access to work with terraform or AWS CLI, please export secrets from the AWS Access Portal for the environment you are using