https://github.com/gematik/erp-errorcodes
This repo lists the error codes for the electronic prescriptions.
https://github.com/gematik/erp-errorcodes
e-rezept errorcodes fhir specification
Last synced: 2 months ago
JSON representation
This repo lists the error codes for the electronic prescriptions.
- Host: GitHub
- URL: https://github.com/gematik/erp-errorcodes
- Owner: gematik
- License: apache-2.0
- Created: 2024-03-11T14:00:14.000Z (almost 2 years ago)
- Default Branch: main
- Last Pushed: 2024-03-26T14:09:10.000Z (almost 2 years ago)
- Last Synced: 2025-02-21T10:15:22.576Z (11 months ago)
- Topics: e-rezept, errorcodes, fhir, specification
- Language: HTML
- Homepage:
- Size: 11.5 MB
- Stars: 1
- Watchers: 11
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
- Code of conduct: .github/CODE_OF_CONDUCT.md
- Security: .github/SECURITY.md
Awesome Lists containing this project
README
# E-Rezept-ErrorCodes FHIR-Profiles
The error codes returned by the E-Rezept Fachdienst
Table of Contents
## About The Project
This Repo contains the fsh files to the published E-Rezept ErrorCodes files on and a script to validate them.
These are the error codes returned by the E-Rezept-Fachdienst when an error occurs. They are fixed and therefore defined by the code systems contained in this repository.
The complete error code can be found in GEM_ERP_CS_ErrorCode and has the following structure:
Issue-Type.ErrorComponent.SubErrorComponent.ErrorSuffix
An example could be: Value.IKNR.Invalid.0001
More details can be found in the [API Documentation](https://github.com/gematik/api-erp)
A short slide deck can also be found [here](https://gematik.github.io/erp-errorcodes/Slides/E-Rezept-Fehlercodes-Konzept.html)
### Release Notes
See [ReleaseNotes.md](./ReleaseNotes.md) for all information regarding the (newest) releases.
## License
Copyright 2024 gematik GmbH
Licensed under the **Apache License, Version 2.0** (the "License"); you may not use this file except in compliance with the License.
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the [LICENSE](./LICENSE) for the specific language governing permissions and limitations under the License.
## Usage
### Installing FHIR tools on your local machine
To set up a development environment with support for FHIR profile compilation and validation:
1. Ensure you have [Docker](https://www.docker.com/products/docker-desktop) installed on your machine.
2. Clone the repository and open it in [Visual Studio Code](https://code.visualstudio.com/).
3. When prompted, reopen the project in a container. This will build the Docker container based on the provided `Dockerfile`.
4. The container includes:
- [Firely Terminal](https://fire.ly/products/firely-terminal/) for FHIR operations.
- [SUSHI](https://fshschool.org/docs/sushi/) for compiling FHIR Shorthand (FSH) files.
- [HAPI FHIR Validator](https://github.com/hapifhir/hapi-fhir/releases) for validating FHIR profiles.
5. The [`codfsh` VS Code extension](https://marketplace.visualstudio.com/items?itemName=gematikde.codfsh) is also installed in the container for an enhanced FHIR profile development experience.
6. Once the container is built and running, you can use the integrated terminal in VS Code to run SUSHI and the HAPI FHIR Validator.
Note: The `codfsh` extension settings are pre-configured in the [`.devcontainer/devcontainer.json`](https://code.visualstudio.com/docs/devcontainers/containers) file to use the correct paths for the HAPI Validator and its configuration.
# Help
If you find issues with this template project, please leave an issue or create a Pull Request via the [template repository](https://github.com/gematik/spec-TemplateForSimplifierProjects).