|
| 1 | +--- |
| 2 | +title: "Introduction to Cases" |
| 3 | +description: "Overview of the ZGW Cases (ZRC) system, managing the registration and lifecycle of cases." |
| 4 | +keywords: [cases, introduction, ZRC, ZGW, API, OneGround, zaken, zaak, registration] |
| 5 | +slug: /cases/introduction |
| 6 | +--- |
| 7 | + |
| 8 | +# Introduction to Cases |
| 9 | + |
| 10 | +The Cases system (often referred to as **ZRC** or Zaak Registratie Component) is a core part of the ZGW API landscape provided by OneGround. It provides a standardized way to register, track, and manage cases ("Zaken") — the central objects representing any government process or service request. |
| 11 | + |
| 12 | +## How it works |
| 13 | + |
| 14 | +A "Zaak" represents an instance of a business process for a specific subject (e.g., a citizen or company). The ZRC manages the full lifecycle of these cases. |
| 15 | + |
| 16 | +1. **Creation**: A client application creates a new Case, referencing a **ZaakType** from the Catalogs (ZTC) to define its structure and rules. |
| 17 | +2. **Status Updates**: As the process progresses, the case status is updated through predefined status types. |
| 18 | +3. **Linking**: Related objects are attached to the case — documents (via DRC), decisions (Besluiten), roles (Rollen), and properties (Eigenschappen). |
| 19 | +4. **Closure**: Once the process is complete, the case is finalized with an end date and result. |
| 20 | + |
| 21 | +## Getting Started |
| 22 | + |
| 23 | +To work with the Cases API, your application typically performs these steps: |
| 24 | + |
| 25 | +1. **Determine the Case Type**: Look up the appropriate **ZaakType** in the Catalogs (ZTC) that matches your business process. |
| 26 | +2. **Create a Case**: Register a new Zaak using the ZaakType reference. |
| 27 | +3. **Manage Lifecycle**: Update the status, add roles, link documents, and record properties as the process evolves. |
| 28 | + |
| 29 | +## Documentation Overview |
| 30 | + |
| 31 | +We have guides to help you integrate with the Cases system: |
| 32 | + |
| 33 | +- **[Use of BSN](./use-of-bsn)**: Best practices for securely retrieving cases associated with a BSN (Dutch Social Security Number). |
| 34 | + |
| 35 | +## Key Concepts |
| 36 | + |
| 37 | +- **Zaak (Case)**: The core resource representing a single instance of a business process (e.g., a permit application or a complaint). |
| 38 | +- **Rol (Role)**: Links a person or organisation to a case in a specific capacity (e.g., initiator, behandelaar). |
| 39 | +- **Status**: Represents the current phase of the case within its defined lifecycle. |
| 40 | +- **Resultaat (Result)**: The final outcome of the case once it is closed. |
| 41 | +- **ZaakObject**: Links a case to an external real-world object (e.g., an address or a parcel of land). |
| 42 | + |
| 43 | +## Official Standards (VNG) |
| 44 | + |
| 45 | +The OneGround Cases system is implemented according to the standards defined by VNG Realisatie. The official standards provide the complete specification: |
| 46 | + |
| 47 | +- **[VNG Zaken Standard](https://vng-realisatie.github.io/gemma-zaken/standaard/zaken/)** |
| 48 | + The core specification for the Cases API (Zaken services). It defines the resources, behavior, and architecture for registering and managing cases. |
| 49 | + |
| 50 | +For further technical details, please refer to the specific pages in this section. |
0 commit comments