e75usfxQ

1Mr Deputy Speaker, 
2
3The British Government is falling behind our European Friends on digital infrastructure and this bill aims to change that; by implementing “MultiPass” a new government app and the “Digital Spine” a digital data exchange layer. 
4
5Firstly, on the new MultiPass system. Multipass aims to be a government app for the purposes of interfacing with government, private companies via plugins and identifying one's self, something Europe has been doing for decades. This will make life much easier for citizens to interact with their digital self. 
6
7Secondly, the Digital Spine is a method for Government Departments and Private Services to work together easily, without the pointless duplication of data. This will make all our services work easier from Tax, the NHS and down to little things like local council planning.  
8
9This bill aims to put government in the background using new, digital connected technologies. No more faffing with paperwork and no more waiting for items to be mailed or faxed through. No more annoying bureaucracy. No more having a million 
10different accounts or apps to interact with digital government services. Simple, seamless in the background government, the future lies within this bill. 
11
12 
13**Pass and Road Bill**
14
15---
16
17**A** 
18 
19**BILL** 
20
21**TO** 
22
23 
24
25*Introduce a better version of the GovPass scheme added to the NHS (Digital Communications and Global Marketisation) bill; Introduce the X-Road digital exchange layer; join the Nordic Institute for Interoperable solutions and connected purposes.*
26 
27
28**BE IT ENACTED by the Queen's most Excellent Majesty, by and with the advice and consent of the Lords Temporal, and Commons, in this present Parliament assembled, and by the authority of the same, as follows: —** 
29
30 
31
32*** Section 1: MultiPass *** 
33
34(1)  The Secretary of State will require creation of a new Digital Government app named “MultiPass” for the purposes of interfacing with government, private companies via plugins and identifying one's self. 
35
36(2)  The MultiPass app with use methods such as the ones detailed in the subsections below to secure user data. 
37
38> (a) Use a mobile phone sim card with the ability to do encryption functions without using the phones internal processor. 
39
40> > (i) The Secretary of State is to contact phone operators in the attempt on producing sim cards compatible with both their mobile networks and MultiPass. 
41
42> (a) A mobile phone with a co-processing unit with the ability to do encryption functions similar in functionality to that of the ARM TrustZone and Apple Secure Enclave. 
43
44> > (i) The Secretary of State is to contact mobile manufacturers in the attempt to allow MultiPass to work on their current or future devices. 
45
46> (a) Using an external device to preform encryption functions supplied by the secretary of state. 
47
48> > (i) The device shall cost no more than 10% of the cost to supply the user the device 
49
50(3) The MultiPass app is too have a public API too allow for the interfacing of third-party software with MultiPass 
51
52(4) The MultiPass app is to have the functionality for third parties to add additional functionality that can be enabled by users of the MultiPass app named “Plugins”. 
53
54> (a) Plugins are to be developed using the MultiPass API and compatible World Wide Web programming languages. 
55
56> (b)  Third Parties must submit the plugins for approval as detailed in subsection 5 and submit a small administration fee to the Secretary of State. 
57
58> > (i) If the plugin is not approved the administration fee is to be refunded. 
59
60(5) The Secretary of State is to approve plugins for the addition to MultiPass considering the criteria detailed in the preceding subsections: 
61
62> (a) The stability of the plugin 
63
64> (b)  The usefulness of the plugin 
65
66> (c)  Whether the plugin fits the function or the design of the MultiPass app 
67
68> (d)  Whether the plugin is usable. 
69
70(6)  The user is to be the only party able to share data stored using the MultiPass app with Government Services and 3rd Parties unless the following is true: 
71> (a)  The user is not in a fit state to approve or deny the sharing of data 
72
73> (b)  The user is under 16 and the sharing of data has been approved by the user’s legal guardian. 
74
75(7)  The service is to employ a bounty program where the Secretary of State is to pay a reward to those who discover an exploit in MultiPass and offering employment to fix said exploit. 
76
77(8) The MultiPass App is to issue the user an “Public Key” this is to be defined as your “MultiPass Identifier” and may be shown via an QR Code or using Near Field Communication. 
78
79(9)  The MultiPass App is required to hold the following information on the user, the information requested below must be verified for legitimacy: 
80
81> (a)  Full Legal Name 
82
83>> (i)  A user may optionally a different preferred name to be used when a full legal name is not necessary.
84
85> (b)  Sex 
86
87> > (i)  A user may define preferred pronouns and gender for use when medical/legal sex is not necessary. 
88
89> (c)  Place of Birth 
90
91> (d)  Date of Birth 
92
93> (e)  Nationality 
94
95> (f)  Signature 
96
97> (g)  The Secretary of State may specify further requirements at any time. 
98
99> (h)  The MultiPass App and Plugins may request more information, this will only be required to access specific functions of the MultiPass App or access a Plugin, this does not have to be verified for legitimacy. 
100
101(10) The MultiPass App may be used as a form of Identification and may be used in place of a provisional driving licence. 
102
103**Section 2: X-Road/Digital Spine** 
104
105
106(1)  The Secretary of State is to launch the Open Source X-Road Digital Exchange Layer in the United Kingdom under the name “Digital Spine” 
107
108(2)  All government departments and services shall require that new equipment procurements where appropriate are to use the Digital Spine to transact information. 
109
110(3)  Government Departments are to securely store their own data, such data is to be connected to the Digital Spine. 
111
112>  (a)  The Secretary of State is to securely back up all Government Data, and store it in multiple locations, including outside the borders of the United Kingdom of Great Britain and Northern Ireland in what is to be named a "Data Embassy"
113
114(4)  MultiPass is to be the consumer front end for people to look at and interact with their data that has been stored on the Digital Spine. 
115
116> (a) Users are to be able to see when their data has been accessed and by which body. 
117
118> (b) Users are to be able to see their data stored on the Digital Spine.
119
120(5) 3rd Parties will be able to transact information using the Digital Spine using an Open API. 
121
122(6)  The Secretary of State is to federate with other nations X-Road systems to the best of his ability. 
123
124(7)  The Secretary of State is to affiliate with or join the Nordic Institute for Interoperable Solutions if they will accept the United Kingdom. 
125
126**Section 3: Amend the NHS (Digital Communications and Global Marketisation) Act** 
127
128(1) Amend Part 1 Section 2 Section 1 of the NHS (Digital Communications and Global Marketisation) Act to read: “All patient records by December 31st 2023, shall be digitised and stored by the Secretary of State for Health, and connected to the Digital Spine. Data available on the Digital Spine is not to be replicated.” 
129
130(2) Amend Part 2 Section 3 of the NHS (Digital Communications and Global Marketisation) Act to read: 
131
132> (a) Upon Royal Assent the Secretary of State for Health is to develop a plugin to MultiPass henceforth named the “NHS Plugin”, this will be released on the same day patient record digitisation is completed or at a later date at the digression of the Secretary of State. 
133
134> (b) The NHS Plugin will allow patients to have access to their own records. 
135
136> (c) The NHS Plugin will act as a portal to other services such as NHS Direct and NHS 111 
137
138> (d)  Relevant medical staff will be able to review medication administered as well as change any required changes to medication. 
139
140> (e) Patients will be able to use the NHS Plugin to book GP appointments, request repeat medication and inform GPs of relevant information 
141
142(3) Amend all mentions of “NHS App” to read “NHS Plugin” in the NHS (Digital Communications and Global Marketisation) Act 
143
144(4) Amend Part 5 of the NHS (Digital Communications and Global Marketisation) Act to read: 
145
146> (a) All confidential data is to be encrypted using AES 256-bit encryption. 
147
148> (b) Personal data is only to be accessed with the permission of the users MultiPass account according to section 1, 8 of the Digital Security Act. 
149
150> (c) The service is to employ a bounty program where the Secretary of State is to pay a reward to those who discover an exploit in MultiPass and offering employment to fix said exploit. 
151
152**Section 4: Plugins** 
153
154(1) The Secretary of State will require creation of develop the following plugins: 
155
156> (a) A plugin which has the capability to be used as a Network Rail Smart Ticket, where on compatible lines the app will allow you to tap in and out using the app and NFC technology and the plugin will determine the price you must pay for the ticket, including discounts 
157
158> (b)  A plugin which has the capability for one to purchase bus and other  local public transport tickets/tap in and out on buses and other local public transport including the capability for discounts and concessionary travel passes. 
159
160> (c) A plugin which has the capability for one to store their driving licence on. 
161
162> (d) A plugin which has the capability for one to see and pay fees to the government such as tax and fines. 
163
164> (e) A plugin for government or other approved services and departments to send mail or notifications to the user. 
165
166> (f) Others where he sees fit. 
167
168 
169**Section 8: Extent, commencement and short title**
170
171(1) This Act shall extend to the whole United Kingdom 
172
173(2) This Act shall come into force upon Royal Assent. 
174
175(3) This Act may be cited as the Pass and Road Act 2019. 
176
177---
178
179**This Bill was submitted by the Baroness of Abergavenny on behalf of the Her Majesty’s 22nd Government**