customer careprogram: Updated docs to reflect that single practice bare mode is not enabled yet but will be soon. Also some slight rewording.

paths/customer_careprogram.yaml

@@ -8,7 +8,7 @@ get:
     
     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.
     
-    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.
+    FUTURE: Soon this API will be updated to allow asking for a single practice; optionally, if a care group's AGB is also provided, the list of care programs contracted by the care group is also provided.
   parameters:
     - name: refDate
       in: query
@@ -30,14 +30,10 @@ get:
                     type: string
                     description: |-
                       Identifying tag name of the care group.
-
-                      In bare mode the first of possible several care groups is written in the response (see above for bare mode).
                     example: demo_fabel
                   careprograms:
                     description: |-
-                      All possible care programs for the care group. For every group it known to which programs they are participating. From this set the actual care programs reported in practices property can be substracted to get a list of missing programs.
+                      All care programs contracted by the care group. Subtract from this set the active care programs from any practice reported in `practices` to know which care programs they may want to activate.
-                      
-                      Empty array in bare mode (see description above).
                     example:
                       - OuderenZorg
                       - DM
@@ -86,11 +82,11 @@ post:
   operationId: setCustomerCareProgram
   summary: Add a practice to a care program.
   description: |-
-    Allows a care group manager to classify practices into care groups (ziektebeelden, ketens).
+    Allows a care group manager to configure which care programs are actively participated in by a GP practice. (care programs = ziektebeelden, ketens).
     
     The caller must authorize itself as a care group (manager).
     
-    The care group must be allowed to take responsibility for the practices it holds. If not, the request is ignored and an empty Json-object is sent back to the caller. Indicating that processing was not successful.
+    The care group must be allowed to take responsibility for the practices it holds. If not, the request is ignored and an empty Json-object is sent back to the caller, indicating that processing was not successful.
     
     The practice must be one of the care group practices. If not, the request is ignored and an empty Json-object is sent back to the caller.