Skip to main content

TransportModel

How a day care client actually reaches the facility and gets home again.

An operational fact about the client, recordable whether or not the §41 catalogue prices it at all. In Mecklenburg-Vorpommern and Berlin the facility is obliged to drive its guests daily and forbidden to bill for it, so a model that could only describe billable journeys could not describe those two states (REQ-CP-023.1).

enum TransportModel {
  NONE
  OUTBOUND_AND_RETURN
  OUTBOUND_ONLY
  OWN_TRANSPORT
  RETURN_ONLY
}

Values​

TransportModel.NONE​

The client makes no journey at all, because they already live where day care is delivered. The default for every contract that never had a Transport Model set. Must never appear on a priced catalogue entry — no journeys settles nothing by definition.

TransportModel.OUTBOUND_AND_RETURN​

The facility drives both legs. The everyday case in every state that operates a Fahrdienst.

TransportModel.OUTBOUND_ONLY​

The facility drives the client to day care; the client arranges the way home.

TransportModel.OWN_TRANSPORT​

The client arranges their own transport for the full round trip. Distinct from NONE: a journey exists here, it is just not the facility's, and several states attach a consequence to it.

TransportModel.RETURN_ONLY​

The client arranges the way to day care; the facility drives them home.

Member Of​

ConfigureDayCareTransportInput input ● CreateDayCareTransportEntryInput input ● DayCareTransportConfiguration object