ISiK Stufe 3 data objects overview
ISiK Stufe 3 groups the information a hospital needs to exchange into twelve data objects. Each one maps to a standard FHIR resource, so systems built on Kodjin can rely on one consistent interface instead of a different message format for every source system.
| Category | Data object (German) | FHIR resource | What it represents |
|---|---|---|---|
| Patient & care team | Patient | Patient | The patient's identifying and demographic details |
| Patient & care team | Kontakt/Fall | Encounter | A single visit or stay: admission, transfer, discharge |
| Patient & care team | Angehöriger | RelatedPerson | A person connected to the patient, typically for insurance or payment purposes |
| Patient & care team | Person im Gesundheitsberuf | Practitioner | The clinician who performed or documented a piece of care |
| Clinical documentation | Diagnose | Condition | A patient's diagnoses |
| Clinical documentation | Prozedur | Procedure | Procedures performed on or planned for a patient |
| Billing & insurance | Abrechnungsfall | Account | The billing case a patient's services are grouped and charged under |
| Billing & insurance | Versicherungsverhältnis | Coverage | The patient's insurance relationship |
| Reports & documents | Bericht aus Subsystemen | Composition (as a document Bundle) | A structured report sent back from a hospital subsystem, e.g. lab or radiology |
| Reports & documents | Binary | Binary | File attachments referenced by other data objects, such as a PDF or scanned image |
| Supporting terminology | Katalog | CodeSystem | A hospital's own internal codes, published so other systems can interpret them |
| Supporting terminology | ValueSet | ValueSet | A curated list of allowed values built from standard and/or internal codes |
Reports from hospital subsystems (Bericht aus Subsystemen) are treated differently from the other data objects: ISiK requires them to be submitted as one complete document, not built up field by field. See the "Bericht aus Subsystemen (Document Bundle)" page for how Kodjin handles this.