<commit_before>---
title: Business requirements
keywords: requirements
tags: [requirements]
sidebar: accessrecord_structured_sidebar
permalink: accessrecord_structured_requirements.html
summary: "Organisational requirements that have informed development work"
---

## User stories and logical data model ##

The [GP Connect Requirements Catalogue for Access Record Structured Data](pages/accessrecord_structured/GP%20Connect%20Req%20Cat%20-%20Access%20Record%20Structured%20Data%20v0.6.xlsx){:target="_blank"} contains the full set of business requirements that need to be met to support the retrieval of medications and allergy data in a structured format.

The requirements are described as a set of user stories with separate acceptance criteria for the provider and consumer systems.

The logical data model identifies and defines the data items that are required by the business. Each logical data item is mapped to the FHIR&reg; profile that will be used to transmit the data.

The Excel spreadsheet is split into 6 tabs:

1.	Document Management: revision history.
2.	NHS England Scenarios:	a set of scenarios defined by NHS England that identify the scope of the work.
3.	Processes – Use Cases:	an index of the use cases used to develop the user stories and logical model. Links to the individual use cases are given below.
4.	User Stories:	the user stories that describe the business requirements for the provider and consumer products.
5. User Stories - IG: the user stories that describe the standards and information governance requirements for the provider and consumer products.
6.	Logical Data Model:	the logical model that identifies and defines that data items that will be supplied.

## Use cases and business processes ##

The use cases define how and where there is a business need that can be supported by GP Connect structured data. They contain the following key components:

 - Description
 - Justification<commit_msg>Reqs - change to summary<commit_after>---
title: Business requirements
keywords: requirements
tags: [requirements]
sidebar: accessrecord_structured_sidebar
permalink: accessrecord_structured_requirements.html
summary: "Clinical, user and governance requirements that must be supported by the solution"
---

## User stories and logical data model ##

The [GP Connect Requirements Catalogue for Access Record Structured Data](pages/accessrecord_structured/GP%20Connect%20Req%20Cat%20-%20Access%20Record%20Structured%20Data%20v0.6.xlsx){:target="_blank"} contains the full set of business requirements that need to be met to support the retrieval of medications and allergy data in a structured format.

The requirements are described as a set of user stories with separate acceptance criteria for the provider and consumer systems.

The logical data model identifies and defines the data items that are required by the business. Each logical data item is mapped to the FHIR&reg; profile that will be used to transmit the data.

The Excel spreadsheet is split into 6 tabs:

1.	Document Management: revision history.
2.	NHS England Scenarios:	a set of scenarios defined by NHS England that identify the scope of the work.
3.	Processes – Use Cases:	an index of the use cases used to develop the user stories and logical model. Links to the individual use cases are given below.
4.	User Stories:	the user stories that describe the business requirements for the provider and consumer products.
5. User Stories - IG: the user stories that describe the standards and information governance requirements for the provider and consumer products.
6.	Logical Data Model:	the logical model that identifies and defines that data items that will be supplied.

## Use cases and business processes ##

The use cases define how and where there is a business need that can be supported by GP Connect structured data. They contain the following key components:

 - Description
 - Justification
{'fraction_non_alphanumeric': 0.0434449271658574, 'fraction_numerical': 0.013800153335037056, 'mean_word_length': 5.068217054263566, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '376281', 'n_tokens_mistral': 945, 'n_tokens_neox': 885, 'n_words': 539}