From 915b19cc2b9617fddf11cb3d1b1e67c158444154 Mon Sep 17 00:00:00 2001 From: Eric Hoekstra Date: Tue, 13 Aug 2024 16:31:48 +0200 Subject: [PATCH] The care group is part of the assignment of a practice to a care program. --- paths/customer_careprogram.yaml | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/paths/customer_careprogram.yaml b/paths/customer_careprogram.yaml index dc5daf4..a62ee49 100644 --- a/paths/customer_careprogram.yaml +++ b/paths/customer_careprogram.yaml @@ -4,10 +4,12 @@ get: - Customer management summary: Practices and care programs description: |- - Gets all practices of a care group and their participation in any care program. + Gets all practices of a care group and their participation in a care program. Enumerates all practices for which the current customer (user) is responsible in the care group. The customer identified with the JWT must be the group manager. The care group must be responsible for the underlying practices. Some care groups are organized in a way that they are not allowed to process data of the member practices. For these care groups no practices are shown. + Only care programs to which the practices was added by the authorised care group are shown. That means if a practices moves to another care group, then the registered care programs are gone. + If the JWT identifies a single practice, then API runs in bare mode. The response in this mode has the same structure, but the list of care programs of the care group is always empty and the list of practices holds exactly one practice. parameters: - name: refDate