{{-- Which services the clinic runs itself. Two answers, and both change what the product does rather than how it looks. Said plainly on the screen, because somebody setting this up is deciding how their clinic works, not ticking a preference. --}}
@csrf @method('PUT')

{{ __('settings::messages.services.title') }}

{{ __('settings::messages.services.intro') }}

@php $services = [ [ 'name' => 'own_laboratory', 'on' => $clinicServices->ownsLaboratory(), 'icon' => 'bi-clipboard2-data', 'label' => __('settings::messages.services.own_laboratory'), 'yes' => __('settings::messages.services.laboratory_yes'), 'no' => __('settings::messages.services.laboratory_no'), ], [ 'name' => 'own_pharmacy', 'on' => $clinicServices->ownsPharmacy(), 'icon' => 'bi-capsule', 'label' => __('settings::messages.services.own_pharmacy'), 'yes' => __('settings::messages.services.pharmacy_yes'), 'no' => __('settings::messages.services.pharmacy_no'), ], ]; @endphp @foreach ($services as $service)
{{-- Both outcomes spelled out, not just the one being turned on. The consequence of "no" is a different flow, not a missing feature, and somebody choosing needs to see both. --}}
  • {{ $service['yes'] }}
  • {{ $service['no'] }}
@endforeach
@if ($canUpdate)
@endif