openapi: 3.2.0 info: title: organisation-data-terminology-api Code System API version: 1.0.1-alpha contact: name: ODS FHIR API Support url: https://digital.nhs.uk/developer/help-and-support email: api.management@nhs.net description: "\n\n## Overview\nUse this API to access a dataset of health and social care organisations, such as trusts or GP practices, using the [Organisation Data Service (ODS)](https://digital.nhs.uk/services/organisation-data-service). \n\nThe FHIR API contains the majority of ODS Content, including Organisations, practitioners and geographic information. It contains all the content found within the [ODS ORD API](http://digital.nhs.uk/developer/api-catalogue/organisation-data-service-ord) and the [ODS STU3 API](https://digital.nhs.uk/developer/api-catalogue/organisation-data-service-fhir)\n\nODS holds information for many different types of organisation related to health and social care – mostly in England but also other countries depending on the type of Organisation. For the full scope of data coverage of the ODS APIs, see [Organisation Data Service - data coverage](https://digital.nhs.uk/services/organisation-data-service/ods-data-coverage). \n\nEvery organisation in ODS has a unique identifier called an ODS code. \n\nUsing this API, you can:\n\n - search for an organisation to find its ODS code \n - get organisation details for a given ODS code\n - get details of related organisations\n - search for a practitioner to find their ODS code \n - get practitioner details for a given ODS code \n - get geographic boundaries for a postcode \n - get details of recently deleted or partially deleted records \n\nYou can also limit the number of results returned, or just request a count of the number of search results.\n\nThis FHIR API makes use of the Organization and OrganizationAffiliation FHIR resources plus range of CodeSystems to deliver the full suite of data, which you will use will depend on your need. \n\n\n### Organisation Data\n\nWe have been able to align the majority of data we hold for an organisation into the FHIR resources Organization and OrganizationAffiliation, through the limited use of extensions, however some previously available information could not be included.\n\nTo access the Organisation attributes which are not included in the Organization resource use the ods-organization-code CodeSystem. The CodeSystem resource returns the following additional information:\n\n - organisation – Assigning Authority \n - related entities, the current related entity of any supported relationships \n - succession - any predecessors and/or successors and a flag to indicate the successor has also been succeeded \n - geographic - the appropriate mapping from the postcode dataset including Local Authority, Integrated Care Board or Lower Super Output Area (LSOA) \n\n### Practitioner Data\nODS publishes a limited set of prescribers held by the Business Services Authority, which includes General Practitioners and Nurse Prescribers, alongside Hospital and Dental Consultants provided by the workforce census returns.\n\nThese codes have not been made available within the Pracitioner Resource as it is felt thet they do not accurately represent an indindiual, but rather reflect their prescribing activities.\n\nTo access the Practitioner data you will need to use the practitioner CodeSystem in conjunction with the practitioner-relationship-instance CodeSystem which contians the relationship between a practitioner and the organisation at which they work. \n\n### Postcodes and geographic boundaries available\n\nFor every postcode within the NHS Postcode Directory, we have compiled a CodeSystem which contains the postcode along with its key Health and Social Care boundaries, including, Primary Care Organisations, Integrated Care Boards, Local Authority 2011 Lower Super Output Areas (LSOA11), Cancer Alliances and NHS England Regions \n\n### CodeSystems to support the full range of ODS Content\n\nIn Addition to the ods-organisation-code CodeSystem mentioned above, there are also CodeSystems for:\n\n- practitioner - includes details about related organisation (where a practitioner is based/works) and type of practitioner\n- postcode - contains various geographic values/boundaries for a postcode including which Lower Super Output Area, Parliamentary Constituency, Local Authority and Integrated Care Board boundary a postcode falls within\n- organization-relationship-instance – contains historic and current relationships\n- organization-role-instance – contains historic and current role instances \n- practitioner-role – contains the role a practitioner performs (currently limited to prescriber types/roles and consultants)\n- practitioner-relationship-instance – contains the associations between Prescribers (GPs) and GP Practices only \n- ODSOrganisationRole – reference Data for Primary and Non Primary Roles (Role ID, Role Name, and Primary/Non Primary indicator)\n- ODSRelationship – reference data for Relationships (Relationship Type ID and Relationship Name) \n- ODSRecordClass – reference data for record classes ie org or site \n- ODSRecordUseType – reference data for the type of use – Full for current records, refOnly for minimal records included for referential integrity\n- geography-name – reference data for ONS identifiers used within the Postcode CodeSystem \n\n\n
\n
\n
\n
\n \n \"\"\n \n
\n
\n
\n

For a non-technical overview of how to build software that deals with organisations and healthcare services, see Building healthcare software - organisations and healthcare services.

\n
\n
\n
\n\n\n## Who can use this API\nThere are no particular restrictions on what this API can be used for. \n\nIt can be used free of charge by public sector organisations in England, Scotland and Wales, including the NHS. This includes use by software developers building software for the public sector.\n\n## Related APIs\nThe following APIs also gives access to the Organisation Data Service:\n- [ODS Organisation Reference Data (ORD) API](https://digital.nhs.uk/developer/api-catalogue/organisation-data-service-ord) - a richer version conforming to DCB000090 Standard, soon to be deprecated.\n- [ODS Organisation Reference Data (FHIR - STU3) API](https://digital.nhs.uk/developer/api-catalogue/organisation-data-service-fhir) - STU3 version contains a minimal organization record, soon to be deprecated.\n\n\n## API status and roadmap\nThis API is [in development](https://digital.nhs.uk/developer/guides-and-documentation/reference-guide#statuses).\n\nTo see our roadmap, or to suggest, comment or vote on features for this API, see our [interactive product backlog](https://nhs-digital-api-management.featureupvote.com/?order=popular&filter=allexceptdone&tag=ods-api#controls).\n\nIf you have any other queries, [contact us](https://digital.nhs.uk/developer/help-and-support).\n\n## Service level\nThis API is a bronze service, meaning it is operational and supported only during business hours (8am to 6pm), Monday to Friday excluding bank holidays.\n\nFor more details, see [service levels](https://digital.nhs.uk/developer/guides-and-documentation/reference-guide#service-levels).\n\n## Technology\nThis API is [RESTful](https://digital.nhs.uk/developer/guides-and-documentation/our-api-technologies#basic-rest).\n\nIt also conforms to the [FHIR](https://digital.nhs.uk/developer/guides-and-documentation/our-api-technologies#fhir) global standard for health care data exchange. Specifically to FHIR R4 (v4.0.1), we have been working closely with the Interoperability team to develop and publish [Implementation guidance](https://simplifier.net/guide/organisation-data-services).\n\nYou do not need to know much about FHIR to use this API - FHIR APIs are just RESTful APIs that follow specific rules. In particular:\n- resource names are capitalised, singular and in American English, for example `/Organization` not `/organisations`\n- array names are singular, for example `line` not `lines` for address lines\n- data items that are country-specific and thus not included in the FHIR global base resources are usually wrapped in an `extension` object\n\nThere are [libraries and SDKs available](https://digital.nhs.uk/developer/guides-and-documentation/api-technologies-at-nhs-digital#fhir-libraries-and-sdks) to help with FHIR API integration.\n\n## Network access\nThis API is available on the internet and, indirectly, on the [Health and Social Care Network (HSCN)](https://digital.nhs.uk/services/health-and-social-care-network).\n\nFor more details see [Network access for APIs](https://digital.nhs.uk/developer/guides-and-documentation/network-access-for-apis).\n\n## Security and authorisation\n### Application-restricted access\n#### still to be decided\nThis API is [application-restricted](https://digital.nhs.uk/developer/guides-and-documentation/security-and-authorisation#application-restricted-apis), meaning we authenticate the calling application but not the end user.\n\n## Errors\nWe use standard HTTP status codes to show whether an API request succeeded or not. They are usually in the range:\n- 200 to 299 if it succeeded, including code 202 if it was accepted by an API that needs to wait for further action\n- 400 to 499 if it failed because of a client error by your application\n- 500 to 599 if it failed because of an error on our server\n\nErrors specific to each API are shown in the Endpoints section, under Response. See our [reference guide](https://digital.nhs.uk/developer/guides-and-documentation/reference-guide#http-status-codes) for more on errors.\n\n\n## Environments and testing\n\n| Environments | Base URLs |\n| ----------------- | ---------------------------------------------------------------------- |\n| User acceptance test (UAT) |TBC |\n| Production |TBC |\n\nFor example:\n`TBC/fhir/Organization/RJY`\nreturns the dataset for the organisation whose ODS code is RJY.\n\n### Integration testing\nYou can use the UAT environment to perform your integration testing.\n\n## Onboarding\n\n\n#### still to be decided if we use the Term server\nIndividual users can access content on the NHS England Terminology Server(ODS Instance) with a registered account.\n\nShrimp is a terminology browser that is freely available on the internet, but it is only for browsing the content. The Terminology Server does not come with a built-in browser, so Shrimp is given as an example of a browsing tool, freely accessible on the internet. Other browsers can be used.\n\nIf you are interested in integrating a software application with the Terminology Server, or if you want to [syndicate content to your own Terminology Server](https://digital.nhs.uk/services/terminology-server#syndication), you will need to complete a [system-to-system request form]https://digital.nhs.uk/services/terminology-server/system-to-system-account-request-form.\n" servers: - url: https://beta.ods.dc4h.link/fhir/ description: User acceptance test (UAT) environment. - url: https://jenkins.ods.dc4h.link/fhir/ description: Production environment. tags: - name: CodeSystem paths: /CodeSystem/: get: summary: Search for additional instance and reference data operationId: search-codesystem description: "## Overview \n\nUse this endpoint to access a range of information contained in CodeSystems to meet your needs. We have CodeSystems that contain regularly changing data such as organisations, practitioners and relationships plus more traditional reference based CodeSystems.\n\nCodeSystem names include the date when they were last updated i.e. `ods-organization-code-2024-03-07` so when searching for individual concepts (records within the CodeSystem) it is necessary to perform a search using a `$lookup` providing the system and code required in addition to any properties you wish to return.\n\nFor example:\n\n`/CodeSystem/$lookup?system=https://fhir.nhs.uk/Id/ods-organization-code&code=G81086&property=*`\n\n### Summary information\nA summary of each codeSystem can be returned to see which properties are available and which search operations are supported, without attempting to return the data. organisation, role, relationship, postcode and geography information will all generate errors as they are too large to be returned.\n\nPerforming a search will default to summary mode and list each instance of the CodeSystem currently stored on the Server. it is expected that we will retain 2-3 versions at any given point. \n\nFor example:\n`/CodeSystem?url=https://fhir.nhs.uk/Id/ods-organization-code`\n\nThe smaller reference based CodeSystems these can be retrieved in full using `_summary=false` which will return all versions stored on the server in full.\n\n For example:\n`/CodeSystem?system=https://digital.nhs.uk/services/organisation-data-service/CodeSystem/practitioner-role&_summary=false`\n\n## Code Validation\nUsing the $validate operation you can check whether a code is present within any given ValueSet and you can also provide additional properties to validate their values.\n \nFor example:\n `CodeSystem/$validate-code?url=https://fhir.nhs.uk/Id/ods-organization-code&code=RH8&status=active`\n\n## Organisation Data\n### ods-organization-code \nhttps://fhir.nhs.uk/Id/ods-organization-code\n\nIn addition to the data available through the FHIR Organization resource we also have the following properties:\n\n * related organisations using a Relationship ID such as RE4 (commissioned by), RE6 (operated by), RE8 is Partner to and Nomonated Payee for (RE10) \n * presence of successor or predecessor information\n * indicator for onward succession\n * geographic values such as Local Authority boundary, Integrated Care Board boundary or Lower Super Output Area (LSOA) \n\n### organisation-relationship-instance \nhttps://digital.nhs.uk/services/organisation-data-service/CodeSystem/organization-relationship-instance \nContains relationship history\n\n### organisation-role-instance \n\nContains role history\n\n\n## Practitioner Data\n### practitioner\nhttps://digital.nhs.uk/services/organisation-data-service/CodeSystem/practitioner\n\nContains the prescribing practitioner and consultants in a single CodeSystem to enable lookup and validation of Practitioner codes. Practitioners are categorised with a type and role. roles and types can be validated against the practitioner-role CodeSystem.\n\n Types include `PGP` (General Practitioner), `PNURSE` - Prescribing Nurse and `PDENTCON` Dental Consultants. \n \n Roles include `PHOSPCON120` (ear nose and throat), `PGP1` (principal GP), `PNURSE1` (district nurse / health visitor)\n\nWhere practitioners are associated to an organisation, the current/latest values is held in a membership property, these include `ME1` Parent Practice for GPs and `ME4` Parent Trust for a Dental Consultant. More information about the associations can be found in the practitioner-relationship-instance CodeSystem.\n\nThis CodeSystem has been designed to enable pracitioners with multiple codes, i.e a Prescribing Code and a General Medical Council (GMC) code to be returned or validated.\n\nProperties numbered from 1 to 8 contain a specific identifier issued by a range of authorities, more information about each assigned identifier including start date and issuing Authority can be found in the practitioner-additional-attribute CodeSystem \n\n### practitioner-relationship-instance\nhttps://digital.nhs.uk/services/organisation-data-service/CodeSystem/practitioner-relationship-instance\n\nContains relationship history where practitioners are associated with an organisation.\n\n### practitioner-additional-attribute\nhttps://digital.nhs.uk/services/organisation-data-service/CodeSystem/practitioner-additional-attribute\n\nContains additional information about the identifier issued to a practitioner, in addition to the identifier, the name and ODS code of the Issing authority, start and end dates for the identifier are included.\n\n## Geographic Data\n#### https://digital.nhs.uk/services/organisation-data-service/CodeSystem/geography-name\n\nSupports the identification of Office for National Statistics (ONS) identifiers for geographic boundaries used within the ods-organization-code CodeSytem. ODS identifiers for geographic organisations such as `ICB` and `Local Authority` can be retreived from the `Organization` Endpoint.\n\n#### https://digital.nhs.uk/services/organisation-data-service/CodeSystem/postcode\n\nContains every postcode within the NHS Postcode Directory and a selection of their geographic boundaries.\n\nMore information about how this data is compiled can be found in the [NHSPD user guide](https://digital.nhs.uk/binaries/content/assets/website-assets/services/ods/user_guide.pdf).\n\nthe following Geographic boundaries are included:\n * `CA` cancer alliance\n * `EW` electoral ward\n * `GOR` government office region\n * `ICB` integrated care board\n * `LA` local authority\n * `LSOA11` 2011 lower super output areas\n * `NHSER` NHS England region\n * `PC` parliamentary constituency\n * `PCO` primary care organisation \n * `SMHPC AED` strategic mental health provider collaborative - adult eating disorder\n * `SMHPC AS` strategic mental health provider collaborative - adult secure\n * `SMHPC CT4` strategic mental health provider collaborative - CYPMH tier 4\n\n## Reference Data\n#### https://digital.nhs.uk/services/organisation-data-service/CodeSystem/ODSOrganisationRole\n\nEvery organisation has at least one role; a primary role. It may also have additional roles which provide more information about the organisation's function or purpose.\n\nThe full list of role codes is contained in this CodeSystem and can be retreived in full or \nindividual role codes can be returned or validated.\n\nThis CodeSystem has 1 additional Property: `primaryRole` which contains a true/false value if the role is a primary role or not.\n\n#### https://digital.nhs.uk/services/organisation-data-service/CodeSystem/ODSRelationship\n\nEvery relationship has a type to describe the nature of the relationship, which includes: `is Commissioned by`, `is operated by` and `is partner to`.\n\n#### https://digital.nhs.uk/services/organisation-data-service/CodeSystem/practitioner-role\n\nWithin the former CSV publications for practitioners, any classifications against a practitioner such as consultant speciality code or nurse prescriber type have been converted to roles and can be returned or validated with this CodeSystem. \n" parameters: - in: query name: system description: 'The Unique Resource Indicator (URI) of the codesystem ' required: false schema: type: string examples: Organisation-Data: summary: ods-organization-code value: https://fhir.nhs.uk/Id/ods-organization-code Relationship-Data: summary: organization-relationship-instance value: https://fhir.nhs.uk/Id/ods-organization-code practitioner: summary: practitioner value: https://digital.nhs.uk/services/organisation-data-service/CodeSystem/practitioner ODSOrganisationRole: summary: ODSOrganisationRole value: https://digital.nhs.uk/services/organisation-data-service/CodeSystem/ODSOrganisationRole ODSRecordUseType: summary: ODSRecordUseType value: https://fhir.nhs.uk/England/CodeSystem/England-ODSRecordUseType ODSRecordUseClass: summary: ODSRecordClass value: https://fhir.nhs.uk/England/CodeSystem/England-ODSRecordUseType - in: query name: code description: "The code of the concept stored within the CodeSystem \n" required: false schema: type: string example: G7112418 - in: query name: property description: "Include all or specific properties from a CodeSystem. \n\nTo return all use asterisk ‘*’ \n\nTo return multiple properties, include each one as a separate parameter \n" required: false schema: type: string examples: return-all: summary: return all properties value: '*' return-one: summary: return a single property value: opStartDate - in: query name: _summmary description: "override default behaviour to retreive a subset of the CodeSystem content when searching.\n\n `data` and `false` will generate errors on larger CodeSystems.\n" required: false schema: type: boolean example: false responses: '200': description: Valid request that returns every paramter for a single concept for the specified code. content: application/json: example: resourceType: Parameters parameter: - name: code valueCode: G81086 - name: display valueString: BIRD-IN-EYE SURGERY - name: name valueString: ODS Organisation - name: system valueUri: https://fhir.nhs.uk/Id/ods-organization-code - name: version valueString: '2024-03-07' - name: designation part: - name: use valueCoding: system: http://terminology.hl7.org/CodeSystem/designation-usage code: display - name: value valueString: BIRD-IN-EYE SURGERY - name: property part: - name: code valueCode: status - name: value valueCode: active - name: property part: - name: code valueCode: RE4 - name: value valueCode: 97R - name: property part: - name: code valueCode: RE6 - name: value valueCode: 97R - name: property part: - name: code valueCode: RE8 - name: value valueCode: U36842 - name: property part: - name: code valueCode: inactive - name: value valueBoolean: false - name: valueBoolean valueBoolean: false - name: property part: - name: code valueCode: country - name: valueString valueString: ENGLAND - name: value valueString: ENGLAND - name: property part: - name: code valueCode: opStartDate - name: valueDateTime valueDateTime: '1974-04-01' - name: value valueDateTime: '1974-04-01' - name: property part: - name: code valueCode: SMHPC CT4 - name: valueCoding valueCoding: system: https://digital.nhs.uk/services/organisation-data-service/CodeSystem/geography-name code: B0N9F - name: value valueCoding: system: https://digital.nhs.uk/services/organisation-data-service/CodeSystem/geography-name code: B0N9F - name: property part: - name: code valueCode: LSOA11 - name: valueCoding valueCoding: system: https://digital.nhs.uk/services/organisation-data-service/CodeSystem/geography-name code: E01021221 - name: value valueCoding: system: https://digital.nhs.uk/services/organisation-data-service/CodeSystem/geography-name code: E01021221 - name: property part: - name: code valueCode: uprn - name: valueString valueString: '10091054340' - name: value valueString: '10091054340' - name: property part: - name: code valueCode: town - name: valueString valueString: UCKFIELD - name: value valueString: UCKFIELD - name: property part: - name: code valueCode: postcode - name: valueString valueString: TN22 5AW - name: value valueString: TN22 5AW - name: property part: - name: code valueCode: telephone - name: valueString valueString: 01825 763196 - name: value valueString: 01825 763196 - name: property part: - name: code valueCode: NHSER - name: valueCoding valueCoding: system: https://digital.nhs.uk/services/organisation-data-service/CodeSystem/geography-name code: Y59 - name: value valueCoding: system: https://digital.nhs.uk/services/organisation-data-service/CodeSystem/geography-name code: Y59 - name: property part: - name: code valueCode: EW - name: valueCoding valueCoding: system: https://digital.nhs.uk/services/organisation-data-service/CodeSystem/geography-name code: E05011661 - name: value valueCoding: system: https://digital.nhs.uk/services/organisation-data-service/CodeSystem/geography-name code: E05011661 - name: property part: - name: code valueCode: SMHPC AS - name: valueCoding valueCoding: system: https://digital.nhs.uk/services/organisation-data-service/CodeSystem/geography-name code: H3F5A - name: value valueCoding: system: https://digital.nhs.uk/services/organisation-data-service/CodeSystem/geography-name code: H3F5A - name: property part: - name: code valueCode: name - name: valueString valueString: BIRD-IN-EYE SURGERY - name: value valueString: BIRD-IN-EYE SURGERY - name: property part: - name: code valueCode: PCO - name: valueCoding valueCoding: system: https://digital.nhs.uk/services/organisation-data-service/CodeSystem/geography-name code: 97R - name: value valueCoding: system: https://digital.nhs.uk/services/organisation-data-service/CodeSystem/geography-name code: 97R - name: property part: - name: code valueCode: role - name: valueCoding valueCoding: system: https://digital.nhs.uk/services/organisation-data-service/CodeSystem/ODSOrganisationRole code: RO177 - name: value valueCoding: system: https://digital.nhs.uk/services/organisation-data-service/CodeSystem/ODSOrganisationRole code: RO177 - name: property part: - name: code valueCode: role - name: valueCoding valueCoding: system: https://digital.nhs.uk/services/organisation-data-service/CodeSystem/ODSOrganisationRole code: RO76 - name: value valueCoding: system: https://digital.nhs.uk/services/organisation-data-service/CodeSystem/ODSOrganisationRole code: RO76 - name: property part: - name: code valueCode: SMHPC AED - name: valueCoding valueCoding: system: https://digital.nhs.uk/services/organisation-data-service/CodeSystem/geography-name code: R7G8O - name: value valueCoding: system: https://digital.nhs.uk/services/organisation-data-service/CodeSystem/geography-name code: R7G8O - name: property part: - name: code valueCode: primaryRole - name: valueCoding valueCoding: system: https://digital.nhs.uk/services/organisation-data-service/CodeSystem/ODSOrganisationRole code: RO177 - name: value valueCoding: system: https://digital.nhs.uk/services/organisation-data-service/CodeSystem/ODSOrganisationRole code: RO177 - name: property part: - name: code valueCode: assigningAuth - name: valueString valueString: NHS BUSINESS SERVICES AUTHORITY - name: value valueString: NHS BUSINESS SERVICES AUTHORITY - name: property part: - name: code valueCode: CA - name: valueCoding valueCoding: system: https://digital.nhs.uk/services/organisation-data-service/CodeSystem/geography-name code: E56000012 - name: value valueCoding: system: https://digital.nhs.uk/services/organisation-data-service/CodeSystem/geography-name code: E56000012 - name: property part: - name: code valueCode: address2 - name: valueString valueString: FRAMFIELD ROAD - name: value valueString: FRAMFIELD ROAD - name: property part: - name: code valueCode: address1 - name: valueString valueString: UCKFIELD COMMUNITY HOSPITAL - name: value valueString: UCKFIELD COMMUNITY HOSPITAL - name: property part: - name: code valueCode: lastChangeDate - name: valueDateTime valueDateTime: '2023-08-22' - name: value valueDateTime: '2023-08-22' - name: property part: - name: code valueCode: ICB - name: valueCoding valueCoding: system: https://digital.nhs.uk/services/organisation-data-service/CodeSystem/geography-name code: QNX - name: value valueCoding: system: https://digital.nhs.uk/services/organisation-data-service/CodeSystem/geography-name code: QNX - name: property part: - name: code valueCode: GOR - name: valueCoding valueCoding: system: https://digital.nhs.uk/services/organisation-data-service/CodeSystem/geography-name code: J - name: value valueCoding: system: https://digital.nhs.uk/services/organisation-data-service/CodeSystem/geography-name code: J - name: property part: - name: code valueCode: PC - name: valueCoding valueCoding: system: https://digital.nhs.uk/services/organisation-data-service/CodeSystem/geography-name code: E14001023 - name: value valueCoding: system: https://digital.nhs.uk/services/organisation-data-service/CodeSystem/geography-name code: E14001023 - name: property part: - name: code valueCode: LA - name: valueCoding valueCoding: system: https://digital.nhs.uk/services/organisation-data-service/CodeSystem/geography-name code: '815' - name: value valueCoding: system: https://digital.nhs.uk/services/organisation-data-service/CodeSystem/geography-name code: '815' - name: property part: - name: code valueCode: legStartDate - name: valueDateTime valueDateTime: '1974-04-01' - name: value valueDateTime: '1974-04-01' - name: property part: - name: code valueCode: orgRecordClass - name: valueCoding valueCoding: system: https://digital.nhs.uk/services/organisation-data-service/CodeSystem/ODSRecordClass code: RC1 - name: value valueCoding: system: https://digital.nhs.uk/services/organisation-data-service/CodeSystem/ODSRecordClass code: RC1 - name: property part: - name: code valueCode: refOnly - name: valueBoolean valueBoolean: false - name: value valueBoolean: false 4XX: description: "\nAn error occurred as follows:\n \n | HTTP Code | issue.severity | issue.code | issue.details.code | issue.details.display |\n |------------ |----------------|---------------|---------------------|--------------------- |\n |400 |error |invalid |HAPI-1940 |Invalid Date/Time/Quantity format |\n |400 |error |invalid |HAPI-0524 |Unknown Search Parameter|\n |404 |error |invalid |HAPI-2001 |Organization not found |\n |405 |error |method not allowed|HAPI-0427 |Method Not Allowed |\n |422 |unprocessable |too-costly |Too many records requested (Use _count and _offset)|Invalid parameter |\n |422 |unprocessable |processing |No declared filter on Codesystem |An input field has an invalid value for its type |\n" tags: - CodeSystem