Executive summary
simpledotorg/simple-android falls short of our standard for production, in part because it has pipeline tools referenced by a changeable name. It scores 66.3 out of 100 and is rated Adequate, and all 44 of its critical findings are security problems in the build pipeline.
Security and Compliance, at 59.9, is the weakest lens and counts most in the score. The best first step is protecting the secrets in build commands, worth about 4.0 points. Restricting the build's access tokens comes next, worth about 3.9 points. Raising Security and Compliance to 70 would lift the score to about 70.1.
Thirty-six pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Seven secrets can leak from the build pipeline, and one pipeline step puts outside input straight into a shell command, so an attacker can run commands in the build pipeline. Pinning each tool to an exact version, limiting each secret to its own step and passing outside input through environment variables would close these risks.
The product code is 87,124 lines, about €260,000 to rebuild.
If Security and Compliance rose from 59.9 to 70, the lowest score rated Strong, the score would rise from 66.3 to about 70.1.
Rebuild cost: about €260,000 · Estimate
| Cost to rebuild | €88,000 to €440,000, for 1,463 to 4,641 hours of work, about 1.8 person-years for 1 to 4 engineers |
|---|---|
| Difficulty of the problem | High, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.9 at a score of 66. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Medium: 87,124 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 mobius | 2 navigation.v2.ScreenKey | 3 patient.businessid | 4 util.room | 5 util.scheduler | 6 medicalhistory | 7 navigation.v2 | 8 navigation.v2.fragments | 9 widgets | 10 drugs.search | 11 drugs | 12 user | 13 registration.phone | 14 sync | 15 home.overdue | 16 overdue | 17 bloodsugar.entry | 18 bloodsugar | 19 contactpatient | 20 patient | 21 facility | 22 remoteconfig | 23 feature | 24 registerorlogin | 25 util | 26 instantsearch | 27 scanid | 28 storage | 29 appconfig | 30 main | 31 bp | 32 di | 33 editpatient | 34 home.overdue.search | 35 newentry | 36 org.simple.clinic | 37 bp.entry | 38 summary | 39 scheduleappointment | 40 summary.teleconsultation.contactdoctor |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 mobius | ||||||||||||||||||||||||||||||||||||||||
| 2 navigation.v2.ScreenKey | ||||||||||||||||||||||||||||||||||||||||
| 3 patient.businessid | ||||||||||||||||||||||||||||||||||||||||
| 4 util.room | ||||||||||||||||||||||||||||||||||||||||
| 5 util.scheduler | ||||||||||||||||||||||||||||||||||||||||
| 6 medicalhistory | 1 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 7 navigation.v2 | 1 | |||||||||||||||||||||||||||||||||||||||
| 8 navigation.v2.fragments | 8 | |||||||||||||||||||||||||||||||||||||||
| 9 widgets | 1 | 3 | 1 | |||||||||||||||||||||||||||||||||||||
| 10 drugs.search | 1 | 1 | 1 | 1 | 2 | 1 | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||
| 11 drugs | 2 | 1 | 1 | 2 | 1 | 1 | 2 | 2 | 2 | 1 | 1 | |||||||||||||||||||||||||||||
| 12 user | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 2 | |||||||||||||||||||||||||||||
| 13 registration.phone | 2 | 1 | 2 | 1 | 1 | 8 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||
| 14 sync | 3 | 1 | 1 | 4 | 2 | 1 | 2 | 2 | 3 | 1 | 3 | 1 | 1 | |||||||||||||||||||||||||||
| 15 home.overdue | 2 | 1 | 2 | 1 | 1 | 1 | 4 | 4 | 4 | 1 | 2 | 7 | 1 | |||||||||||||||||||||||||||
| 16 overdue | 6 | 1 | 2 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||||
| 17 bloodsugar.entry | 2 | 1 | 1 | 1 | 2 | 1 | 1 | 20 | 1 | 1 | 1 | 5 | 1 | |||||||||||||||||||||||||||
| 18 bloodsugar | 1 | 1 | 1 | 1 | 2 | 1 | 3 | 1 | 1 | |||||||||||||||||||||||||||||||
| 19 contactpatient | 2 | 1 | 2 | 1 | 1 | 1 | 2 | 19 | 1 | 6 | 4 | 1 | 7 | 1 | ||||||||||||||||||||||||||
| 20 patient | 9 | 3 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 4 | 2 | 1 | ||||||||||||||||||||||||||
| 21 facility | 5 | 3 | 1 | |||||||||||||||||||||||||||||||||||||
| 22 remoteconfig | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 23 feature | 2 | |||||||||||||||||||||||||||||||||||||||
| 24 registerorlogin | 1 | 1 | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 25 util | 1 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 26 instantsearch | 2 | 7 | 1 | 3 | 1 | 2 | 13 | 10 | 1 | 1 | 2 | |||||||||||||||||||||||||||||
| 27 scanid | 2 | 9 | 1 | 2 | 1 | 2 | 11 | 1 | 2 | |||||||||||||||||||||||||||||||
| 28 storage | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 29 appconfig | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 30 main | 1 | 1 | 8 | 1 | 5 | 2 | 1 | 1 | 2 | 2 | ||||||||||||||||||||||||||||||
| 31 bp | 1 | 1 | 1 | 2 | 1 | 3 | 2 | 1 | ||||||||||||||||||||||||||||||||
| 32 di | 1 | 2 | 2 | 4 | 1 | 5 | ||||||||||||||||||||||||||||||||||
| 33 editpatient | 2 | 10 | 1 | 4 | 1 | 1 | 1 | 3 | 19 | 1 | 2 | 3 | 2 | |||||||||||||||||||||||||||
| 34 home.overdue.search | 2 | 1 | 2 | 1 | 2 | 4 | 2 | 1 | 1 | 1 | 1 | 5 | 1 | |||||||||||||||||||||||||||
| 35 newentry | 2 | 4 | 1 | 1 | 1 | 1 | 2 | 16 | 1 | 1 | 2 | 1 | ||||||||||||||||||||||||||||
| 36 org.simple.clinic | 2 | 2 | 1 | 1 | 2 | 5 | 4 | 2 | 1 | 2 | 1 | 2 | 3 | |||||||||||||||||||||||||||
| 37 bp.entry | 1 | 1 | 3 | 1 | 1 | 1 | 1 | 1 | 5 | 8 | 1 | |||||||||||||||||||||||||||||
| 38 summary | 4 | 5 | 1 | 11 | 4 | 1 | 2 | 12 | 2 | 1 | 3 | 2 | 11 | 13 | 3 | 2 | 6 | 2 | 2 | 1 | ||||||||||||||||||||
| 39 scheduleappointment | 3 | 1 | 2 | 1 | 1 | 11 | 2 | 9 | 1 | 3 | 1 | 1 | ||||||||||||||||||||||||||||
| 40 summary.teleconsultation.contactdoctor | 1 | 1 | 1 | 3 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 6 |
6→14 medicalhistory uses sync part of a loop✕
- Connections
- 1 pair of types, where a type in medicalhistory uses a type in sync.
- The types involved
org.simple.clinic.medicalhistory.MedicalHistoryRepository→org.simple.clinic.sync.SynceableRepository
- Direction
- medicalhistory uses sync, so a change to sync can break medicalhistory, while a change to medicalhistory can't break sync.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→20 medicalhistory uses patient part of a loop✕
- Connections
- 2 pairs of types, where a type in medicalhistory uses a type in patient.
- The types involved
org.simple.clinic.medicalhistory.MedicalHistory→org.simple.clinic.patient.SyncStatusorg.simple.clinic.medicalhistory.MedicalHistoryRepository→org.simple.clinic.patient.SyncStatus
- Direction
- medicalhistory uses patient, so a change to patient can break medicalhistory, while a change to medicalhistory can't break patient.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→25 medicalhistory uses util part of a loop✕
- Connections
- 1 pair of types, where a type in medicalhistory uses a type in util.
- The types involved
org.simple.clinic.medicalhistory.MedicalHistoryRepository→org.simple.clinic.util.UtcClock
- Direction
- medicalhistory uses util, so a change to util can break medicalhistory, while a change to medicalhistory can't break util.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→36 medicalhistory uses org.simple.clinic part of a loop✕
- Connections
- 1 pair of types, where a type in medicalhistory uses a type in org.simple.clinic.
- The types involved
org.simple.clinic.medicalhistory.MedicalHistoryModule→org.simple.clinic.AppDatabase
- Direction
- medicalhistory uses org.simple.clinic, so a change to org.simple.clinic can break medicalhistory, while a change to medicalhistory can't break org.simple.clinic.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→2 navigation.v2 uses navigation.v2.ScreenKey✕
- Connections
- 1 pair of types, where a type in navigation.v2 uses a type in navigation.v2.ScreenKey.
- The types involved
org.simple.clinic.navigation.v2.ScreenKey→org.simple.clinic.navigation.v2.ScreenKey.ScreenType
- Direction
- navigation.v2 uses navigation.v2.ScreenKey, so a change to navigation.v2.ScreenKey can break navigation.v2, while a change to navigation.v2 can't break navigation.v2.ScreenKey.
- Position
- Below the diagonal: navigation.v2 uses a module listed above it, which is the healthy direction.
8→1 navigation.v2.fragments uses mobius✕
- Connections
- 8 pairs of types, where a type in navigation.v2.fragments uses a type in mobius.
- The types involved
org.simple.clinic.navigation.v2.fragments.BaseBottomSheet→org.simple.clinic.mobius.ViewEffectsHandlerorg.simple.clinic.navigation.v2.fragments.BaseBottomSheet→org.simple.clinic.mobius.ViewRendererorg.simple.clinic.navigation.v2.fragments.BaseDialog→org.simple.clinic.mobius.ViewEffectsHandlerorg.simple.clinic.navigation.v2.fragments.BaseDialog→org.simple.clinic.mobius.ViewRendererorg.simple.clinic.navigation.v2.fragments.BaseScreen→org.simple.clinic.mobius.ViewEffectsHandlerorg.simple.clinic.navigation.v2.fragments.BaseScreen→org.simple.clinic.mobius.ViewRendererorg.simple.clinic.navigation.v2.fragments.NoopViewEffectsHandler→org.simple.clinic.mobius.ViewEffectsHandlerorg.simple.clinic.navigation.v2.fragments.NoopViewRenderer→org.simple.clinic.mobius.ViewRenderer
- Direction
- navigation.v2.fragments uses mobius, so a change to mobius can break navigation.v2.fragments, while a change to navigation.v2.fragments can't break mobius.
- Position
- Below the diagonal: navigation.v2.fragments uses a module listed above it, which is the healthy direction.
9→3 widgets uses patient.businessid✕
- Connections
- 1 pair of types, where a type in widgets uses a type in patient.businessid.
- The types involved
org.simple.clinic.widgets.PatientSearchResultItemView→org.simple.clinic.patient.businessid.Identifier
- Direction
- widgets uses patient.businessid, so a change to patient.businessid can break widgets, while a change to widgets can't break patient.businessid.
- Position
- Below the diagonal: widgets uses a module listed above it, which is the healthy direction.
9→20 widgets uses patient part of a loop✕
- Connections
- 3 pairs of types, where a type in widgets uses a type in patient.
- The types involved
org.simple.clinic.widgets.PatientSearchResultItemView→org.simple.clinic.patient.PatientAddressorg.simple.clinic.widgets.PatientSearchResultItemView→org.simple.clinic.patient.PatientAgeDetailsorg.simple.clinic.widgets.PatientSearchResultItemView→org.simple.clinic.patient.PatientStatus
- Direction
- widgets uses patient, so a change to patient can break widgets, while a change to widgets can't break patient.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→25 widgets uses util part of a loop✕
- Connections
- 1 pair of types, where a type in widgets uses a type in util.
- The types involved
org.simple.clinic.widgets.PatientSearchResultItemView→org.simple.clinic.util.UserClock
- Direction
- widgets uses util, so a change to util can break widgets, while a change to widgets can't break util.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→1 drugs.search uses mobius✕
- Connections
- 1 pair of types, where a type in drugs.search uses a type in mobius.
- The types involved
org.simple.clinic.drugs.search.DrugSearchUiRenderer→org.simple.clinic.mobius.ViewRenderer
- Direction
- drugs.search uses mobius, so a change to mobius can break drugs.search, while a change to drugs.search can't break mobius.
- Position
- Below the diagonal: drugs.search uses a module listed above it, which is the healthy direction.
10→5 drugs.search uses util.scheduler✕
- Connections
- 1 pair of types, where a type in drugs.search uses a type in util.scheduler.
- The types involved
org.simple.clinic.drugs.search.DrugSearchEffectHandler→org.simple.clinic.util.scheduler.SchedulersProvider
- Direction
- drugs.search uses util.scheduler, so a change to util.scheduler can break drugs.search, while a change to drugs.search can't break util.scheduler.
- Position
- Below the diagonal: drugs.search uses a module listed above it, which is the healthy direction.
10→7 drugs.search uses navigation.v2✕
- Connections
- 1 pair of types, where a type in drugs.search uses a type in navigation.v2.
- The types involved
org.simple.clinic.drugs.search.DrugsSearchScreen→org.simple.clinic.navigation.v2.Router
- Direction
- drugs.search uses navigation.v2, so a change to navigation.v2 can break drugs.search, while a change to drugs.search can't break navigation.v2.
- Position
- Below the diagonal: drugs.search uses a module listed above it, which is the healthy direction.
10→8 drugs.search uses navigation.v2.fragments✕
- Connections
- 1 pair of types, where a type in drugs.search uses a type in navigation.v2.fragments.
- The types involved
org.simple.clinic.drugs.search.DrugsSearchScreen→org.simple.clinic.navigation.v2.fragments.BaseScreen
- Direction
- drugs.search uses navigation.v2.fragments, so a change to navigation.v2.fragments can break drugs.search, while a change to drugs.search can't break navigation.v2.fragments.
- Position
- Below the diagonal: drugs.search uses a module listed above it, which is the healthy direction.
10→9 drugs.search uses widgets✕
- Connections
- 2 pairs of types, where a type in drugs.search uses a type in widgets.
- The types involved
org.simple.clinic.drugs.search.DrugSearchEvent→org.simple.clinic.widgets.UiEventorg.simple.clinic.drugs.search.DrugsSearchScreen→org.simple.clinic.widgets.UiEvent
- Direction
- drugs.search uses widgets, so a change to widgets can break drugs.search, while a change to drugs.search can't break widgets.
- Position
- Below the diagonal: drugs.search uses a module listed above it, which is the healthy direction.
10→14 drugs.search uses sync part of a loop✕
- Connections
- 1 pair of types, where a type in drugs.search uses a type in sync.
- The types involved
org.simple.clinic.drugs.search.DrugRepository→org.simple.clinic.sync.SynceableRepository
- Direction
- drugs.search uses sync, so a change to sync can break drugs.search, while a change to drugs.search can't break sync.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→20 drugs.search uses patient part of a loop✕
- Connections
- 1 pair of types, where a type in drugs.search uses a type in patient.
- The types involved
org.simple.clinic.drugs.search.DrugRepository→org.simple.clinic.patient.SyncStatus
- Direction
- drugs.search uses patient, so a change to patient can break drugs.search, while a change to drugs.search can't break patient.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→21 drugs.search uses facility part of a loop✕
- Connections
- 1 pair of types, where a type in drugs.search uses a type in facility.
- The types involved
org.simple.clinic.drugs.search.DrugSearchEffectHandler→org.simple.clinic.facility.Facility
- Direction
- drugs.search uses facility, so a change to facility can break drugs.search, while a change to drugs.search can't break facility.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→25 drugs.search uses util part of a loop✕
- Connections
- 1 pair of types, where a type in drugs.search uses a type in util.
- The types involved
org.simple.clinic.drugs.search.DrugSearchEffectHandler→org.simple.clinic.util.PagerFactory
- Direction
- drugs.search uses util, so a change to util can break drugs.search, while a change to drugs.search can't break util.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→28 drugs.search uses storage part of a loop✕
- Connections
- 1 pair of types, where a type in drugs.search uses a type in storage.
- The types involved
org.simple.clinic.drugs.search.Drug→org.simple.clinic.storage.Timestamps
- Direction
- drugs.search uses storage, so a change to storage can break drugs.search, while a change to drugs.search can't break storage.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→36 drugs.search uses org.simple.clinic part of a loop✕
- Connections
- 1 pair of types, where a type in drugs.search uses a type in org.simple.clinic.
- The types involved
org.simple.clinic.drugs.search.DrugModule→org.simple.clinic.AppDatabase
- Direction
- drugs.search uses org.simple.clinic, so a change to org.simple.clinic can break drugs.search, while a change to drugs.search can't break org.simple.clinic.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→1 drugs uses mobius✕
- Connections
- 2 pairs of types, where a type in drugs uses a type in mobius.
- The types involved
org.simple.clinic.drugs.EditMedicinesUiRenderer→org.simple.clinic.mobius.ViewRendererorg.simple.clinic.drugs.EditMedicinesViewEffectHandler→org.simple.clinic.mobius.ViewEffectsHandler
- Direction
- drugs uses mobius, so a change to mobius can break drugs, while a change to drugs can't break mobius.
- Position
- Below the diagonal: drugs uses a module listed above it, which is the healthy direction.
11→5 drugs uses util.scheduler✕
- Connections
- 1 pair of types, where a type in drugs uses a type in util.scheduler.
- The types involved
org.simple.clinic.drugs.EditMedicinesEffectHandler→org.simple.clinic.util.scheduler.SchedulersProvider
- Direction
- drugs uses util.scheduler, so a change to util.scheduler can break drugs, while a change to drugs can't break util.scheduler.
- Position
- Below the diagonal: drugs uses a module listed above it, which is the healthy direction.
11→9 drugs uses widgets✕
- Connections
- 1 pair of types, where a type in drugs uses a type in widgets.
- The types involved
org.simple.clinic.drugs.EditMedicinesEvent→org.simple.clinic.widgets.UiEvent
- Direction
- drugs uses widgets, so a change to widgets can break drugs, while a change to drugs can't break widgets.
- Position
- Below the diagonal: drugs uses a module listed above it, which is the healthy direction.
11→10 drugs uses drugs.search✕
- Connections
- 2 pairs of types, where a type in drugs uses a type in drugs.search.
- The types involved
org.simple.clinic.drugs.DrugFrequencyChoiceItemsLoaded→org.simple.clinic.drugs.search.DrugFrequencyorg.simple.clinic.drugs.EditMedicinesEffectHandler→org.simple.clinic.drugs.search.DrugFrequency
- Direction
- drugs uses drugs.search, so a change to drugs.search can break drugs, while a change to drugs can't break drugs.search.
- Position
- Below the diagonal: drugs uses a module listed above it, which is the healthy direction.
11→14 drugs uses sync part of a loop✕
- Connections
- 1 pair of types, where a type in drugs uses a type in sync.
- The types involved
org.simple.clinic.drugs.PrescriptionRepository→org.simple.clinic.sync.SynceableRepository
- Direction
- drugs uses sync, so a change to sync can break drugs, while a change to drugs can't break sync.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→16 drugs uses overdue part of a loop✕
- Connections
- 1 pair of types, where a type in drugs uses a type in overdue.
- The types involved
org.simple.clinic.drugs.EditMedicinesEffectHandler→org.simple.clinic.overdue.AppointmentRepository
- Direction
- drugs uses overdue, so a change to overdue can break drugs, while a change to drugs can't break overdue.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→20 drugs uses patient part of a loop✕
- Connections
- 2 pairs of types, where a type in drugs uses a type in patient.
- The types involved
org.simple.clinic.drugs.PrescribedDrug→org.simple.clinic.patient.SyncStatusorg.simple.clinic.drugs.PrescriptionRepository→org.simple.clinic.patient.SyncStatus
- Direction
- drugs uses patient, so a change to patient can break drugs, while a change to drugs can't break patient.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→21 drugs uses facility part of a loop✕
- Connections
- 2 pairs of types, where a type in drugs uses a type in facility.
- The types involved
org.simple.clinic.drugs.EditMedicinesEffectHandler→org.simple.clinic.facility.Facilityorg.simple.clinic.drugs.PrescriptionRepository→org.simple.clinic.facility.Facility
- Direction
- drugs uses facility, so a change to facility can break drugs, while a change to drugs can't break facility.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→25 drugs uses util part of a loop✕
- Connections
- 2 pairs of types, where a type in drugs uses a type in util.
- The types involved
org.simple.clinic.drugs.PrescribedDrug→org.simple.clinic.util.UtcClockorg.simple.clinic.drugs.PrescriptionRepository→org.simple.clinic.util.UtcClock
- Direction
- drugs uses util, so a change to util can break drugs, while a change to drugs can't break util.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→28 drugs uses storage part of a loop✕
- Connections
- 1 pair of types, where a type in drugs uses a type in storage.
- The types involved
org.simple.clinic.drugs.PrescribedDrug→org.simple.clinic.storage.Timestamps
- Direction
- drugs uses storage, so a change to storage can break drugs, while a change to drugs can't break storage.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→36 drugs uses org.simple.clinic part of a loop✕
- Connections
- 1 pair of types, where a type in drugs uses a type in org.simple.clinic.
- The types involved
org.simple.clinic.drugs.PrescriptionModule→org.simple.clinic.AppDatabase
- Direction
- drugs uses org.simple.clinic, so a change to org.simple.clinic can break drugs, while a change to drugs can't break org.simple.clinic.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→5 user uses util.scheduler✕
- Connections
- 1 pair of types, where a type in user uses a type in util.scheduler.
- The types involved
org.simple.clinic.user.UnauthorizeUser→org.simple.clinic.util.scheduler.SchedulersProvider
- Direction
- user uses util.scheduler, so a change to util.scheduler can break user, while a change to user can't break util.scheduler.
- Position
- Below the diagonal: user uses a module listed above it, which is the healthy direction.
12→6 user uses medicalhistory✕
- Connections
- 1 pair of types, where a type in user uses a type in medicalhistory.
- The types involved
org.simple.clinic.user.ReportPendingRecordsToAnalytics→org.simple.clinic.medicalhistory.MedicalHistoryRepository
- Direction
- user uses medicalhistory, so a change to medicalhistory can break user, while a change to user can't break medicalhistory.
- Position
- Below the diagonal: user uses a module listed above it, which is the healthy direction.
12→11 user uses drugs✕
- Connections
- 1 pair of types, where a type in user uses a type in drugs.
- The types involved
org.simple.clinic.user.ReportPendingRecordsToAnalytics→org.simple.clinic.drugs.PrescriptionRepository
- Direction
- user uses drugs, so a change to drugs can break user, while a change to user can't break drugs.
- Position
- Below the diagonal: user uses a module listed above it, which is the healthy direction.
12→14 user uses sync part of a loop✕
- Connections
- 1 pair of types, where a type in user uses a type in sync.
- The types involved
org.simple.clinic.user.UnauthorizeUser→org.simple.clinic.sync.DataSync
- Direction
- user uses sync, so a change to sync can break user, while a change to user can't break sync.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→16 user uses overdue part of a loop✕
- Connections
- 1 pair of types, where a type in user uses a type in overdue.
- The types involved
org.simple.clinic.user.ReportPendingRecordsToAnalytics→org.simple.clinic.overdue.AppointmentRepository
- Direction
- user uses overdue, so a change to overdue can break user, while a change to user can't break overdue.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→20 user uses patient part of a loop✕
- Connections
- 1 pair of types, where a type in user uses a type in patient.
- The types involved
org.simple.clinic.user.ReportPendingRecordsToAnalytics→org.simple.clinic.patient.PatientRepository
- Direction
- user uses patient, so a change to patient can break user, while a change to user can't break patient.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→21 user uses facility part of a loop✕
- Connections
- 1 pair of types, where a type in user uses a type in facility.
- The types involved
org.simple.clinic.user.SessionModule→org.simple.clinic.facility.Facility
- Direction
- user uses facility, so a change to facility can break user, while a change to user can't break facility.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→25 user uses util part of a loop✕
- Connections
- 1 pair of types, where a type in user uses a type in util.
- The types involved
org.simple.clinic.user.User→org.simple.clinic.util.UtcClock
- Direction
- user uses util, so a change to util can break user, while a change to user can't break util.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→29 user uses appconfig part of a loop✕
- Connections
- 1 pair of types, where a type in user uses a type in appconfig.
- The types involved
org.simple.clinic.user.UserSession→org.simple.clinic.appconfig.Country
- Direction
- user uses appconfig, so a change to appconfig can break user, while a change to user can't break appconfig.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→31 user uses bp part of a loop✕
- Connections
- 1 pair of types, where a type in user uses a type in bp.
- The types involved
org.simple.clinic.user.ReportPendingRecordsToAnalytics→org.simple.clinic.bp.BloodPressureRepository
- Direction
- user uses bp, so a change to bp can break user, while a change to user can't break bp.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→36 user uses org.simple.clinic part of a loop✕
- Connections
- 2 pairs of types, where a type in user uses a type in org.simple.clinic.
- The types involved
org.simple.clinic.user.SessionModule→org.simple.clinic.AppDatabaseorg.simple.clinic.user.UserSession→org.simple.clinic.AppDatabase
- Direction
- user uses org.simple.clinic, so a change to org.simple.clinic can break user, while a change to user can't break org.simple.clinic.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→1 registration.phone uses mobius✕
- Connections
- 2 pairs of types, where a type in registration.phone uses a type in mobius.
- The types involved
org.simple.clinic.registration.phone.RegistrationPhoneUiRenderer→org.simple.clinic.mobius.ViewRendererorg.simple.clinic.registration.phone.RegistrationPhoneViewEffectHandler→org.simple.clinic.mobius.ViewEffectsHandler
- Direction
- registration.phone uses mobius, so a change to mobius can break registration.phone, while a change to registration.phone can't break mobius.
- Position
- Below the diagonal: registration.phone uses a module listed above it, which is the healthy direction.
13→5 registration.phone uses util.scheduler✕
- Connections
- 1 pair of types, where a type in registration.phone uses a type in util.scheduler.
- The types involved
org.simple.clinic.registration.phone.RegistrationPhoneEffectHandler→org.simple.clinic.util.scheduler.SchedulersProvider
- Direction
- registration.phone uses util.scheduler, so a change to util.scheduler can break registration.phone, while a change to registration.phone can't break util.scheduler.
- Position
- Below the diagonal: registration.phone uses a module listed above it, which is the healthy direction.
13→7 registration.phone uses navigation.v2✕
- Connections
- 2 pairs of types, where a type in registration.phone uses a type in navigation.v2.
- The types involved
org.simple.clinic.registration.phone.RegistrationPhoneScreen→org.simple.clinic.navigation.v2.Routerorg.simple.clinic.registration.phone.RegistrationPhoneScreenKey→org.simple.clinic.navigation.v2.ScreenKey
- Direction
- registration.phone uses navigation.v2, so a change to navigation.v2 can break registration.phone, while a change to registration.phone can't break navigation.v2.
- Position
- Below the diagonal: registration.phone uses a module listed above it, which is the healthy direction.
13→8 registration.phone uses navigation.v2.fragments✕
- Connections
- 1 pair of types, where a type in registration.phone uses a type in navigation.v2.fragments.
- The types involved
org.simple.clinic.registration.phone.RegistrationPhoneScreen→org.simple.clinic.navigation.v2.fragments.BaseScreen
- Direction
- registration.phone uses navigation.v2.fragments, so a change to navigation.v2.fragments can break registration.phone, while a change to registration.phone can't break navigation.v2.fragments.
- Position
- Below the diagonal: registration.phone uses a module listed above it, which is the healthy direction.
13→9 registration.phone uses widgets✕
- Connections
- 1 pair of types, where a type in registration.phone uses a type in widgets.
- The types involved
org.simple.clinic.registration.phone.RegistrationPhoneEvent→org.simple.clinic.widgets.UiEvent
- Direction
- registration.phone uses widgets, so a change to widgets can break registration.phone, while a change to registration.phone can't break widgets.
- Position
- Below the diagonal: registration.phone uses a module listed above it, which is the healthy direction.
13→12 registration.phone uses user✕
- Connections
- 8 pairs of types, where a type in registration.phone uses a type in user.
- The types involved
org.simple.clinic.registration.phone.ContinueRegistration→org.simple.clinic.user.OngoingRegistrationEntryorg.simple.clinic.registration.phone.CreateUserLocally→org.simple.clinic.user.UserStatusorg.simple.clinic.registration.phone.PrefillFields→org.simple.clinic.user.OngoingRegistrationEntryorg.simple.clinic.registration.phone.RegistrationPhoneEffectHandler→org.simple.clinic.user.UserSessionorg.simple.clinic.registration.phone.RegistrationPhoneModel→org.simple.clinic.user.OngoingRegistrationEntryorg.simple.clinic.registration.phone.RegistrationPhoneScreen→org.simple.clinic.user.OngoingRegistrationEntryorg.simple.clinic.registration.phone.RegistrationPhoneUiActions→org.simple.clinic.user.OngoingRegistrationEntryorg.simple.clinic.registration.phone.RegistrationPhoneUpdate→org.simple.clinic.user.UserStatus
- Direction
- registration.phone uses user, so a change to user can break registration.phone, while a change to registration.phone can't break user.
- Position
- Below the diagonal: registration.phone uses a module listed above it, which is the healthy direction.
13→21 registration.phone uses facility part of a loop✕
- Connections
- 1 pair of types, where a type in registration.phone uses a type in facility.
- The types involved
org.simple.clinic.registration.phone.RegistrationPhoneEffectHandler→org.simple.clinic.facility.FacilitySync
- Direction
- registration.phone uses facility, so a change to facility can break registration.phone, while a change to registration.phone can't break facility.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→25 registration.phone uses util part of a loop✕
- Connections
- 1 pair of types, where a type in registration.phone uses a type in util.
- The types involved
org.simple.clinic.registration.phone.RegistrationPhoneUiRenderer→org.simple.clinic.util.ValueChangedCallback
- Direction
- registration.phone uses util, so a change to util can break registration.phone, while a change to registration.phone can't break util.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→29 registration.phone uses appconfig part of a loop✕
- Connections
- 1 pair of types, where a type in registration.phone uses a type in appconfig.
- The types involved
org.simple.clinic.registration.phone.RegistrationPhoneScreen→org.simple.clinic.appconfig.Country
- Direction
- registration.phone uses appconfig, so a change to appconfig can break registration.phone, while a change to registration.phone can't break appconfig.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→5 sync uses util.scheduler✕
- Connections
- 3 pairs of types, where a type in sync uses a type in util.scheduler.
- The types involved
org.simple.clinic.sync.DataSync→org.simple.clinic.util.scheduler.SchedulersProviderorg.simple.clinic.sync.DataSyncOnApprovalModule→org.simple.clinic.util.scheduler.SchedulersProviderorg.simple.clinic.sync.SyncDataOnApproval→org.simple.clinic.util.scheduler.SchedulersProvider
- Direction
- sync uses util.scheduler, so a change to util.scheduler can break sync, while a change to sync can't break util.scheduler.
- Position
- Below the diagonal: sync uses a module listed above it, which is the healthy direction.
14→6 sync uses medicalhistory✕
- Connections
- 1 pair of types, where a type in sync uses a type in medicalhistory.
- The types involved
org.simple.clinic.sync.SyncModule→org.simple.clinic.medicalhistory.MedicalHistoryRepository
- Direction
- sync uses medicalhistory, so a change to medicalhistory can break sync, while a change to sync can't break medicalhistory.
- Position
- Below the diagonal: sync uses a module listed above it, which is the healthy direction.
14→11 sync uses drugs✕
- Connections
- 1 pair of types, where a type in sync uses a type in drugs.
- The types involved
org.simple.clinic.sync.SyncModule→org.simple.clinic.drugs.PrescriptionRepository
- Direction
- sync uses drugs, so a change to drugs can break sync, while a change to sync can't break drugs.
- Position
- Below the diagonal: sync uses a module listed above it, which is the healthy direction.
14→12 sync uses user✕
- Connections
- 4 pairs of types, where a type in sync uses a type in user.
- The types involved
org.simple.clinic.sync.DataSync→org.simple.clinic.user.Userorg.simple.clinic.sync.DataSync→org.simple.clinic.user.UserSessionorg.simple.clinic.sync.DataSyncOnApprovalModule→org.simple.clinic.user.UserSessionorg.simple.clinic.sync.SyncDataOnApproval→org.simple.clinic.user.UserSession
- Direction
- sync uses user, so a change to user can break sync, while a change to sync can't break user.
- Position
- Below the diagonal: sync uses a module listed above it, which is the healthy direction.
14→16 sync uses overdue part of a loop✕
- Connections
- 2 pairs of types, where a type in sync uses a type in overdue.
- The types involved
org.simple.clinic.sync.SyncModule→org.simple.clinic.overdue.AppointmentRepositoryorg.simple.clinic.sync.SyncModule→org.simple.clinic.overdue.AppointmentSync
- Direction
- sync uses overdue, so a change to overdue can break sync, while a change to sync can't break overdue.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→18 sync uses bloodsugar part of a loop✕
- Connections
- 1 pair of types, where a type in sync uses a type in bloodsugar.
- The types involved
org.simple.clinic.sync.SyncModule→org.simple.clinic.bloodsugar.BloodSugarRepository
- Direction
- sync uses bloodsugar, so a change to bloodsugar can break sync, while a change to sync can't break bloodsugar.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→20 sync uses patient part of a loop✕
- Connections
- 2 pairs of types, where a type in sync uses a type in patient.
- The types involved
org.simple.clinic.sync.SyncModule→org.simple.clinic.patient.PatientRepositoryorg.simple.clinic.sync.SynceableRepository→org.simple.clinic.patient.SyncStatus
- Direction
- sync uses patient, so a change to patient can break sync, while a change to sync can't break patient.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→21 sync uses facility part of a loop✕
- Connections
- 2 pairs of types, where a type in sync uses a type in facility.
- The types involved
org.simple.clinic.sync.PurgeOnSync→org.simple.clinic.facility.Facilityorg.simple.clinic.sync.SyncModule→org.simple.clinic.facility.FacilitySync
- Direction
- sync uses facility, so a change to facility can break sync, while a change to sync can't break facility.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→22 sync uses remoteconfig part of a loop✕
- Connections
- 3 pairs of types, where a type in sync uses a type in remoteconfig.
- The types involved
org.simple.clinic.sync.DataSync→org.simple.clinic.remoteconfig.RemoteConfigServiceorg.simple.clinic.sync.PurgeOnSync→org.simple.clinic.remoteconfig.ConfigReaderorg.simple.clinic.sync.SyncConfigModule→org.simple.clinic.remoteconfig.ConfigReader
- Direction
- sync uses remoteconfig, so a change to remoteconfig can break sync, while a change to sync can't break remoteconfig.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→23 sync uses feature part of a loop✕
- Connections
- 1 pair of types, where a type in sync uses a type in feature.
- The types involved
org.simple.clinic.sync.SyncModule→org.simple.clinic.feature.Features
- Direction
- sync uses feature, so a change to feature can break sync, while a change to sync can't break feature.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→25 sync uses util part of a loop✕
- Connections
- 3 pairs of types, where a type in sync uses a type in util.
- The types involved
org.simple.clinic.sync.DataSync→org.simple.clinic.util.ResolvedErrororg.simple.clinic.sync.LastSyncedState→org.simple.clinic.util.UtcClockorg.simple.clinic.sync.PurgeOnSync→org.simple.clinic.util.UtcClock
- Direction
- sync uses util, so a change to util can break sync, while a change to sync can't break util.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→31 sync uses bp part of a loop✕
- Connections
- 1 pair of types, where a type in sync uses a type in bp.
- The types involved
org.simple.clinic.sync.SyncModule→org.simple.clinic.bp.BloodPressureRepository
- Direction
- sync uses bp, so a change to bp can break sync, while a change to sync can't break bp.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→36 sync uses org.simple.clinic part of a loop✕
- Connections
- 1 pair of types, where a type in sync uses a type in org.simple.clinic.
- The types involved
org.simple.clinic.sync.PurgeOnSync→org.simple.clinic.AppDatabase
- Direction
- sync uses org.simple.clinic, so a change to org.simple.clinic can break sync, while a change to sync can't break org.simple.clinic.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→1 home.overdue uses mobius✕
- Connections
- 2 pairs of types, where a type in home.overdue uses a type in mobius.
- The types involved
org.simple.clinic.home.overdue.OverdueUiRenderer→org.simple.clinic.mobius.ViewRendererorg.simple.clinic.home.overdue.OverdueViewEffectHandler→org.simple.clinic.mobius.ViewEffectsHandler
- Direction
- home.overdue uses mobius, so a change to mobius can break home.overdue, while a change to home.overdue can't break mobius.
- Position
- Below the diagonal: home.overdue uses a module listed above it, which is the healthy direction.
15→5 home.overdue uses util.scheduler✕
- Connections
- 1 pair of types, where a type in home.overdue uses a type in util.scheduler.
- The types involved
org.simple.clinic.home.overdue.OverdueEffectHandler→org.simple.clinic.util.scheduler.SchedulersProvider
- Direction
- home.overdue uses util.scheduler, so a change to util.scheduler can break home.overdue, while a change to home.overdue can't break util.scheduler.
- Position
- Below the diagonal: home.overdue uses a module listed above it, which is the healthy direction.
15→7 home.overdue uses navigation.v2✕
- Connections
- 2 pairs of types, where a type in home.overdue uses a type in navigation.v2.
- The types involved
org.simple.clinic.home.overdue.OverdueScreen→org.simple.clinic.navigation.v2.Routerorg.simple.clinic.home.overdue.OverdueScreen→org.simple.clinic.navigation.v2.ScreenResultBus
- Direction
- home.overdue uses navigation.v2, so a change to navigation.v2 can break home.overdue, while a change to home.overdue can't break navigation.v2.
- Position
- Below the diagonal: home.overdue uses a module listed above it, which is the healthy direction.
15→8 home.overdue uses navigation.v2.fragments✕
- Connections
- 1 pair of types, where a type in home.overdue uses a type in navigation.v2.fragments.
- The types involved
org.simple.clinic.home.overdue.OverdueScreen→org.simple.clinic.navigation.v2.fragments.BaseScreen
- Direction
- home.overdue uses navigation.v2.fragments, so a change to navigation.v2.fragments can break home.overdue, while a change to home.overdue can't break navigation.v2.fragments.
- Position
- Below the diagonal: home.overdue uses a module listed above it, which is the healthy direction.
15→9 home.overdue uses widgets✕
- Connections
- 1 pair of types, where a type in home.overdue uses a type in widgets.
- The types involved
org.simple.clinic.home.overdue.OverdueEvent→org.simple.clinic.widgets.UiEvent
- Direction
- home.overdue uses widgets, so a change to widgets can break home.overdue, while a change to home.overdue can't break widgets.
- Position
- Below the diagonal: home.overdue uses a module listed above it, which is the healthy direction.
15→14 home.overdue uses sync✕
- Connections
- 1 pair of types, where a type in home.overdue uses a type in sync.
- The types involved
org.simple.clinic.home.overdue.OverdueScreen→org.simple.clinic.sync.LastSyncedState
- Direction
- home.overdue uses sync, so a change to sync can break home.overdue, while a change to home.overdue can't break sync.
- Position
- Below the diagonal: home.overdue uses a module listed above it, which is the healthy direction.
15→16 home.overdue uses overdue part of a loop✕
- Connections
- 4 pairs of types, where a type in home.overdue uses a type in overdue.
- The types involved
org.simple.clinic.home.overdue.OverdueAppointment→org.simple.clinic.overdue.Appointmentorg.simple.clinic.home.overdue.OverdueEffectHandler→org.simple.clinic.overdue.AppointmentRepositoryorg.simple.clinic.home.overdue.OverdueEffectHandler→org.simple.clinic.overdue.OverdueAppointmentSelectororg.simple.clinic.home.overdue.OverdueScreen→org.simple.clinic.overdue.PendingAppointmentsConfig
- Direction
- home.overdue uses overdue, so a change to overdue can break home.overdue, while a change to home.overdue can't break overdue.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→20 home.overdue uses patient part of a loop✕
- Connections
- 4 pairs of types, where a type in home.overdue uses a type in patient.
- The types involved
org.simple.clinic.home.overdue.OverdueAppointment→org.simple.clinic.patient.Answerorg.simple.clinic.home.overdue.OverdueAppointment→org.simple.clinic.patient.Genderorg.simple.clinic.home.overdue.OverdueAppointment→org.simple.clinic.patient.PatientAgeDetailsorg.simple.clinic.home.overdue.OverdueAppointment→org.simple.clinic.patient.PatientPhoneNumber
- Direction
- home.overdue uses patient, so a change to patient can break home.overdue, while a change to home.overdue can't break patient.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→21 home.overdue uses facility part of a loop✕
- Connections
- 4 pairs of types, where a type in home.overdue uses a type in facility.
- The types involved
org.simple.clinic.home.overdue.CurrentFacilityLoaded→org.simple.clinic.facility.Facilityorg.simple.clinic.home.overdue.LoadOverdueAppointments→org.simple.clinic.facility.Facilityorg.simple.clinic.home.overdue.OverdueEffectHandler→org.simple.clinic.facility.Facilityorg.simple.clinic.home.overdue.OverdueModel→org.simple.clinic.facility.Facility
- Direction
- home.overdue uses facility, so a change to facility can break home.overdue, while a change to home.overdue can't break facility.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→22 home.overdue uses remoteconfig part of a loop✕
- Connections
- 1 pair of types, where a type in home.overdue uses a type in remoteconfig.
- The types involved
org.simple.clinic.home.overdue.OverdueAppointmentsConfigModule→org.simple.clinic.remoteconfig.ConfigReader
- Direction
- home.overdue uses remoteconfig, so a change to remoteconfig can break home.overdue, while a change to home.overdue can't break remoteconfig.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→23 home.overdue uses feature part of a loop✕
- Connections
- 2 pairs of types, where a type in home.overdue uses a type in feature.
- The types involved
org.simple.clinic.home.overdue.OverdueAppointmentSorter→org.simple.clinic.feature.Featuresorg.simple.clinic.home.overdue.OverdueScreen→org.simple.clinic.feature.Features
- Direction
- home.overdue uses feature, so a change to feature can break home.overdue, while a change to home.overdue can't break feature.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→25 home.overdue uses util part of a loop✕
- Connections
- 7 pairs of types, where a type in home.overdue uses a type in util.
- The types involved
org.simple.clinic.home.overdue.DownloadOverdueListClicked→org.simple.clinic.util.RequiresNetworkorg.simple.clinic.home.overdue.OverdueEffectHandler→org.simple.clinic.util.PagerFactoryorg.simple.clinic.home.overdue.OverdueEffectHandler→org.simple.clinic.util.UserClockorg.simple.clinic.home.overdue.OverdueScreen→org.simple.clinic.util.RuntimeNetworkStatusorg.simple.clinic.home.overdue.OverdueScreen→org.simple.clinic.util.UserClockorg.simple.clinic.home.overdue.OverdueScreen→org.simple.clinic.util.UtcClockorg.simple.clinic.home.overdue.ShareOverdueListClicked→org.simple.clinic.util.RequiresNetwork
- Direction
- home.overdue uses util, so a change to util can break home.overdue, while a change to home.overdue can't break util.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→29 home.overdue uses appconfig part of a loop✕
- Connections
- 1 pair of types, where a type in home.overdue uses a type in appconfig.
- The types involved
org.simple.clinic.home.overdue.OverdueScreen→org.simple.clinic.appconfig.Country
- Direction
- home.overdue uses appconfig, so a change to appconfig can break home.overdue, while a change to home.overdue can't break appconfig.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→14 overdue uses sync✕
- Connections
- 6 pairs of types, where a type in overdue uses a type in sync.
- The types involved
org.simple.clinic.overdue.AppointmentPullResponse→org.simple.clinic.sync.DataPullResponseorg.simple.clinic.overdue.AppointmentRepository→org.simple.clinic.sync.SynceableRepositoryorg.simple.clinic.overdue.AppointmentSync→org.simple.clinic.sync.ModelSyncorg.simple.clinic.overdue.AppointmentSync→org.simple.clinic.sync.SyncConfigorg.simple.clinic.overdue.AppointmentSync→org.simple.clinic.sync.SyncCoordinatororg.simple.clinic.overdue.AppointmentSyncApi→org.simple.clinic.sync.DataPushResponse
- Direction
- overdue uses sync, so a change to sync can break overdue, while a change to overdue can't break sync.
- Position
- Below the diagonal: overdue uses a module listed above it, which is the healthy direction.
16→15 overdue uses home.overdue✕
- Connections
- 1 pair of types, where a type in overdue uses a type in home.overdue.
- The types involved
org.simple.clinic.overdue.AppointmentRepository→org.simple.clinic.home.overdue.OverdueAppointment
- Direction
- overdue uses home.overdue, so a change to home.overdue can break overdue, while a change to overdue can't break home.overdue.
- Position
- Below the diagonal: overdue uses a module listed above it, which is the healthy direction.
16→20 overdue uses patient part of a loop✕
- Connections
- 2 pairs of types, where a type in overdue uses a type in patient.
- The types involved
org.simple.clinic.overdue.Appointment→org.simple.clinic.patient.SyncStatusorg.simple.clinic.overdue.AppointmentRepository→org.simple.clinic.patient.SyncStatus
- Direction
- overdue uses patient, so a change to patient can break overdue, while a change to overdue can't break patient.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→22 overdue uses remoteconfig part of a loop✕
- Connections
- 1 pair of types, where a type in overdue uses a type in remoteconfig.
- The types involved
org.simple.clinic.overdue.AppointmentModule→org.simple.clinic.remoteconfig.ConfigReader
- Direction
- overdue uses remoteconfig, so a change to remoteconfig can break overdue, while a change to overdue can't break remoteconfig.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→25 overdue uses util part of a loop✕
- Connections
- 2 pairs of types, where a type in overdue uses a type in util.
- The types involved
org.simple.clinic.overdue.AppointmentRepository→org.simple.clinic.util.UserClockorg.simple.clinic.overdue.AppointmentRepository→org.simple.clinic.util.UtcClock
- Direction
- overdue uses util, so a change to util can break overdue, while a change to overdue can't break util.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→36 overdue uses org.simple.clinic part of a loop✕
- Connections
- 1 pair of types, where a type in overdue uses a type in org.simple.clinic.
- The types involved
org.simple.clinic.overdue.AppointmentModule→org.simple.clinic.AppDatabase
- Direction
- overdue uses org.simple.clinic, so a change to org.simple.clinic can break overdue, while a change to overdue can't break org.simple.clinic.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→1 bloodsugar.entry uses mobius✕
- Connections
- 2 pairs of types, where a type in bloodsugar.entry uses a type in mobius.
- The types involved
org.simple.clinic.bloodsugar.entry.BloodSugarEntryUiRenderer→org.simple.clinic.mobius.ViewRendererorg.simple.clinic.bloodsugar.entry.BloodSugarEntryViewEffectHandler→org.simple.clinic.mobius.ViewEffectsHandler
- Direction
- bloodsugar.entry uses mobius, so a change to mobius can break bloodsugar.entry, while a change to bloodsugar.entry can't break mobius.
- Position
- Below the diagonal: bloodsugar.entry uses a module listed above it, which is the healthy direction.
17→5 bloodsugar.entry uses util.scheduler✕
- Connections
- 1 pair of types, where a type in bloodsugar.entry uses a type in util.scheduler.
- The types involved
org.simple.clinic.bloodsugar.entry.BloodSugarEntryEffectHandler→org.simple.clinic.util.scheduler.SchedulersProvider
- Direction
- bloodsugar.entry uses util.scheduler, so a change to util.scheduler can break bloodsugar.entry, while a change to bloodsugar.entry can't break util.scheduler.
- Position
- Below the diagonal: bloodsugar.entry uses a module listed above it, which is the healthy direction.
17→7 bloodsugar.entry uses navigation.v2✕
- Connections
- 1 pair of types, where a type in bloodsugar.entry uses a type in navigation.v2.
- The types involved
org.simple.clinic.bloodsugar.entry.BloodSugarEntrySheet→org.simple.clinic.navigation.v2.Router
- Direction
- bloodsugar.entry uses navigation.v2, so a change to navigation.v2 can break bloodsugar.entry, while a change to bloodsugar.entry can't break navigation.v2.
- Position
- Below the diagonal: bloodsugar.entry uses a module listed above it, which is the healthy direction.
17→8 bloodsugar.entry uses navigation.v2.fragments✕
- Connections
- 1 pair of types, where a type in bloodsugar.entry uses a type in navigation.v2.fragments.
- The types involved
org.simple.clinic.bloodsugar.entry.BloodSugarEntrySheet→org.simple.clinic.navigation.v2.fragments.BaseBottomSheet
- Direction
- bloodsugar.entry uses navigation.v2.fragments, so a change to navigation.v2.fragments can break bloodsugar.entry, while a change to bloodsugar.entry can't break navigation.v2.fragments.
- Position
- Below the diagonal: bloodsugar.entry uses a module listed above it, which is the healthy direction.
17→9 bloodsugar.entry uses widgets✕
- Connections
- 2 pairs of types, where a type in bloodsugar.entry uses a type in widgets.
- The types involved
org.simple.clinic.bloodsugar.entry.BloodSugarEntryEvent→org.simple.clinic.widgets.UiEventorg.simple.clinic.bloodsugar.entry.BloodSugarEntrySheet→org.simple.clinic.widgets.UiEvent
- Direction
- bloodsugar.entry uses widgets, so a change to widgets can break bloodsugar.entry, while a change to bloodsugar.entry can't break widgets.
- Position
- Below the diagonal: bloodsugar.entry uses a module listed above it, which is the healthy direction.
17→12 bloodsugar.entry uses user✕
- Connections
- 1 pair of types, where a type in bloodsugar.entry uses a type in user.
- The types involved
org.simple.clinic.bloodsugar.entry.BloodSugarEntryEffectHandler→org.simple.clinic.user.User
- Direction
- bloodsugar.entry uses user, so a change to user can break bloodsugar.entry, while a change to bloodsugar.entry can't break user.
- Position
- Below the diagonal: bloodsugar.entry uses a module listed above it, which is the healthy direction.
17→16 bloodsugar.entry uses overdue✕
- Connections
- 1 pair of types, where a type in bloodsugar.entry uses a type in overdue.
- The types involved
org.simple.clinic.bloodsugar.entry.BloodSugarEntryEffectHandler→org.simple.clinic.overdue.AppointmentRepository
- Direction
- bloodsugar.entry uses overdue, so a change to overdue can break bloodsugar.entry, while a change to bloodsugar.entry can't break overdue.
- Position
- Below the diagonal: bloodsugar.entry uses a module listed above it, which is the healthy direction.
17→18 bloodsugar.entry uses bloodsugar part of a loop✕
- Connections
- 20 pairs of types, where a type in bloodsugar.entry uses a type in bloodsugar.
- The types involved
org.simple.clinic.bloodsugar.entry.BloodSugarEntryEffectHandler→org.simple.clinic.bloodsugar.BloodSugarMeasurementorg.simple.clinic.bloodsugar.entry.BloodSugarEntryEffectHandler→org.simple.clinic.bloodsugar.BloodSugarRepositoryorg.simple.clinic.bloodsugar.entry.BloodSugarEntryEffectHandler→org.simple.clinic.bloodsugar.BloodSugarUnitPreferenceorg.simple.clinic.bloodsugar.entry.BloodSugarEntryModel→org.simple.clinic.bloodsugar.BloodSugarMeasurementTypeorg.simple.clinic.bloodsugar.entry.BloodSugarEntryModel→org.simple.clinic.bloodsugar.BloodSugarUnitPreferenceorg.simple.clinic.bloodsugar.entry.BloodSugarEntrySheet→org.simple.clinic.bloodsugar.BloodSugarMeasurementTypeorg.simple.clinic.bloodsugar.entry.BloodSugarEntrySheet→org.simple.clinic.bloodsugar.BloodSugarUnitPreferenceorg.simple.clinic.bloodsugar.entry.BloodSugarEntryUi→org.simple.clinic.bloodsugar.BloodSugarMeasurementTypeorg.simple.clinic.bloodsugar.entry.BloodSugarEntryUiActions→org.simple.clinic.bloodsugar.BloodSugarMeasurementTypeorg.simple.clinic.bloodsugar.entry.BloodSugarEntryUiActions→org.simple.clinic.bloodsugar.BloodSugarUnitPreferenceorg.simple.clinic.bloodsugar.entry.BloodSugarEntryUpdate→org.simple.clinic.bloodsugar.BloodSugarReadingorg.simple.clinic.bloodsugar.entry.BloodSugarEntryUpdate→org.simple.clinic.bloodsugar.BloodSugarUnitPreferenceorg.simple.clinic.bloodsugar.entry.BloodSugarEntryViewEffectHandler→org.simple.clinic.bloodsugar.BloodSugarUnitPreferenceorg.simple.clinic.bloodsugar.entry.BloodSugarMeasurementFetched→org.simple.clinic.bloodsugar.BloodSugarMeasurementorg.simple.clinic.bloodsugar.entry.BloodSugarUnitPreferenceLoaded→org.simple.clinic.bloodsugar.BloodSugarUnitPreferenceorg.simple.clinic.bloodsugar.entry.CreateNewBloodSugarEntry→org.simple.clinic.bloodsugar.BloodSugarReadingorg.simple.clinic.bloodsugar.entry.OpenAs→org.simple.clinic.bloodsugar.BloodSugarMeasurementTypeorg.simple.clinic.bloodsugar.entry.ShowBloodSugarUnitSelectionDialog→org.simple.clinic.bloodsugar.BloodSugarUnitPreferenceorg.simple.clinic.bloodsugar.entry.ShowBloodSugarValidationError→org.simple.clinic.bloodsugar.BloodSugarUnitPreferenceorg.simple.clinic.bloodsugar.entry.UpdateBloodSugarEntry→org.simple.clinic.bloodsugar.BloodSugarReading
- Direction
- bloodsugar.entry uses bloodsugar, so a change to bloodsugar can break bloodsugar.entry, while a change to bloodsugar.entry can't break bloodsugar.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→20 bloodsugar.entry uses patient part of a loop✕
- Connections
- 1 pair of types, where a type in bloodsugar.entry uses a type in patient.
- The types involved
org.simple.clinic.bloodsugar.entry.BloodSugarEntryEffectHandler→org.simple.clinic.patient.PatientRepository
- Direction
- bloodsugar.entry uses patient, so a change to patient can break bloodsugar.entry, while a change to bloodsugar.entry can't break patient.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→21 bloodsugar.entry uses facility part of a loop✕
- Connections
- 1 pair of types, where a type in bloodsugar.entry uses a type in facility.
- The types involved
org.simple.clinic.bloodsugar.entry.BloodSugarEntryEffectHandler→org.simple.clinic.facility.Facility
- Direction
- bloodsugar.entry uses facility, so a change to facility can break bloodsugar.entry, while a change to bloodsugar.entry can't break facility.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→23 bloodsugar.entry uses feature part of a loop✕
- Connections
- 1 pair of types, where a type in bloodsugar.entry uses a type in feature.
- The types involved
org.simple.clinic.bloodsugar.entry.BloodSugarEntrySheet→org.simple.clinic.feature.Features
- Direction
- bloodsugar.entry uses feature, so a change to feature can break bloodsugar.entry, while a change to bloodsugar.entry can't break feature.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→25 bloodsugar.entry uses util part of a loop✕
- Connections
- 5 pairs of types, where a type in bloodsugar.entry uses a type in util.
- The types involved
org.simple.clinic.bloodsugar.entry.BloodSugarEntryEffectHandler→org.simple.clinic.util.UserClockorg.simple.clinic.bloodsugar.entry.BloodSugarEntrySheet→org.simple.clinic.util.UserClockorg.simple.clinic.bloodsugar.entry.BloodSugarEntrySheet→org.simple.clinic.util.UserInputDatePaddingCharacterorg.simple.clinic.bloodsugar.entry.BloodSugarEntryUiRenderer→org.simple.clinic.util.ValueChangedCallbackorg.simple.clinic.bloodsugar.entry.BloodSugarEntryUpdate→org.simple.clinic.util.UserInputDatePaddingCharacter
- Direction
- bloodsugar.entry uses util, so a change to util can break bloodsugar.entry, while a change to bloodsugar.entry can't break util.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→36 bloodsugar.entry uses org.simple.clinic part of a loop✕
- Connections
- 1 pair of types, where a type in bloodsugar.entry uses a type in org.simple.clinic.
- The types involved
org.simple.clinic.bloodsugar.entry.BloodSugarEntryEffectHandler→org.simple.clinic.ReportAnalyticsEvents
- Direction
- bloodsugar.entry uses org.simple.clinic, so a change to org.simple.clinic can break bloodsugar.entry, while a change to bloodsugar.entry can't break org.simple.clinic.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
18→5 bloodsugar uses util.scheduler✕
- Connections
- 1 pair of types, where a type in bloodsugar uses a type in util.scheduler.
- The types involved
org.simple.clinic.bloodsugar.BloodSugarHistoryListItemPagingSource→org.simple.clinic.util.scheduler.SchedulersProvider
- Direction
- bloodsugar uses util.scheduler, so a change to util.scheduler can break bloodsugar, while a change to bloodsugar can't break util.scheduler.
- Position
- Below the diagonal: bloodsugar uses a module listed above it, which is the healthy direction.
18→12 bloodsugar uses user✕
- Connections
- 1 pair of types, where a type in bloodsugar uses a type in user.
- The types involved
org.simple.clinic.bloodsugar.BloodSugarRepository→org.simple.clinic.user.User
- Direction
- bloodsugar uses user, so a change to user can break bloodsugar, while a change to bloodsugar can't break user.
- Position
- Below the diagonal: bloodsugar uses a module listed above it, which is the healthy direction.
18→14 bloodsugar uses sync✕
- Connections
- 1 pair of types, where a type in bloodsugar uses a type in sync.
- The types involved
org.simple.clinic.bloodsugar.BloodSugarRepository→org.simple.clinic.sync.SynceableRepository
- Direction
- bloodsugar uses sync, so a change to sync can break bloodsugar, while a change to bloodsugar can't break sync.
- Position
- Below the diagonal: bloodsugar uses a module listed above it, which is the healthy direction.
18→17 bloodsugar uses bloodsugar.entry✕
- Connections
- 1 pair of types, where a type in bloodsugar uses a type in bloodsugar.entry.
- The types involved
org.simple.clinic.bloodsugar.BloodSugarReading→org.simple.clinic.bloodsugar.entry.ValidationResult
- Direction
- bloodsugar uses bloodsugar.entry, so a change to bloodsugar.entry can break bloodsugar, while a change to bloodsugar can't break bloodsugar.entry.
- Position
- Below the diagonal: bloodsugar uses a module listed above it, which is the healthy direction.
18→20 bloodsugar uses patient part of a loop✕
- Connections
- 2 pairs of types, where a type in bloodsugar uses a type in patient.
- The types involved
org.simple.clinic.bloodsugar.BloodSugarMeasurement→org.simple.clinic.patient.SyncStatusorg.simple.clinic.bloodsugar.BloodSugarRepository→org.simple.clinic.patient.SyncStatus
- Direction
- bloodsugar uses patient, so a change to patient can break bloodsugar, while a change to bloodsugar can't break patient.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
18→21 bloodsugar uses facility part of a loop✕
- Connections
- 1 pair of types, where a type in bloodsugar uses a type in facility.
- The types involved
org.simple.clinic.bloodsugar.BloodSugarRepository→org.simple.clinic.facility.Facility
- Direction
- bloodsugar uses facility, so a change to facility can break bloodsugar, while a change to bloodsugar can't break facility.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
18→25 bloodsugar uses util part of a loop✕
- Connections
- 3 pairs of types, where a type in bloodsugar uses a type in util.
- The types involved
org.simple.clinic.bloodsugar.BloodSugarHistoryListItemPagingSource→org.simple.clinic.util.UserClockorg.simple.clinic.bloodsugar.BloodSugarHistoryListItemPagingSource→org.simple.clinic.util.UtcClockorg.simple.clinic.bloodsugar.BloodSugarRepository→org.simple.clinic.util.UtcClock
- Direction
- bloodsugar uses util, so a change to util can break bloodsugar, while a change to bloodsugar can't break util.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
18→28 bloodsugar uses storage part of a loop✕
- Connections
- 1 pair of types, where a type in bloodsugar uses a type in storage.
- The types involved
org.simple.clinic.bloodsugar.BloodSugarMeasurement→org.simple.clinic.storage.Timestamps
- Direction
- bloodsugar uses storage, so a change to storage can break bloodsugar, while a change to bloodsugar can't break storage.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
18→36 bloodsugar uses org.simple.clinic part of a loop✕
- Connections
- 1 pair of types, where a type in bloodsugar uses a type in org.simple.clinic.
- The types involved
org.simple.clinic.bloodsugar.BloodSugarHistoryListItemPagingSource→org.simple.clinic.AppDatabase
- Direction
- bloodsugar uses org.simple.clinic, so a change to org.simple.clinic can break bloodsugar, while a change to bloodsugar can't break org.simple.clinic.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→1 contactpatient uses mobius✕
- Connections
- 2 pairs of types, where a type in contactpatient uses a type in mobius.
- The types involved
org.simple.clinic.contactpatient.ContactPatientUiRenderer→org.simple.clinic.mobius.ViewRendererorg.simple.clinic.contactpatient.ContactPatientViewEffectHandler→org.simple.clinic.mobius.ViewEffectsHandler
- Direction
- contactpatient uses mobius, so a change to mobius can break contactpatient, while a change to contactpatient can't break mobius.
- Position
- Below the diagonal: contactpatient uses a module listed above it, which is the healthy direction.
19→5 contactpatient uses util.scheduler✕
- Connections
- 1 pair of types, where a type in contactpatient uses a type in util.scheduler.
- The types involved
org.simple.clinic.contactpatient.ContactPatientEffectHandler→org.simple.clinic.util.scheduler.SchedulersProvider
- Direction
- contactpatient uses util.scheduler, so a change to util.scheduler can break contactpatient, while a change to contactpatient can't break util.scheduler.
- Position
- Below the diagonal: contactpatient uses a module listed above it, which is the healthy direction.
19→6 contactpatient uses medicalhistory✕
- Connections
- 2 pairs of types, where a type in contactpatient uses a type in medicalhistory.
- The types involved
org.simple.clinic.contactpatient.ContactPatientProfile→org.simple.clinic.medicalhistory.MedicalHistoryorg.simple.clinic.contactpatient.PatientDetails→org.simple.clinic.medicalhistory.Answer
- Direction
- contactpatient uses medicalhistory, so a change to medicalhistory can break contactpatient, while a change to contactpatient can't break medicalhistory.
- Position
- Below the diagonal: contactpatient uses a module listed above it, which is the healthy direction.
19→7 contactpatient uses navigation.v2✕
- Connections
- 1 pair of types, where a type in contactpatient uses a type in navigation.v2.
- The types involved
org.simple.clinic.contactpatient.ContactPatientBottomSheet→org.simple.clinic.navigation.v2.Router
- Direction
- contactpatient uses navigation.v2, so a change to navigation.v2 can break contactpatient, while a change to contactpatient can't break navigation.v2.
- Position
- Below the diagonal: contactpatient uses a module listed above it, which is the healthy direction.
19→8 contactpatient uses navigation.v2.fragments✕
- Connections
- 1 pair of types, where a type in contactpatient uses a type in navigation.v2.fragments.
- The types involved
org.simple.clinic.contactpatient.ContactPatientBottomSheet→org.simple.clinic.navigation.v2.fragments.BaseBottomSheet
- Direction
- contactpatient uses navigation.v2.fragments, so a change to navigation.v2.fragments can break contactpatient, while a change to contactpatient can't break navigation.v2.fragments.
- Position
- Below the diagonal: contactpatient uses a module listed above it, which is the healthy direction.
19→9 contactpatient uses widgets✕
- Connections
- 1 pair of types, where a type in contactpatient uses a type in widgets.
- The types involved
org.simple.clinic.contactpatient.ContactPatientEvent→org.simple.clinic.widgets.UiEvent
- Direction
- contactpatient uses widgets, so a change to widgets can break contactpatient, while a change to contactpatient can't break widgets.
- Position
- Below the diagonal: contactpatient uses a module listed above it, which is the healthy direction.
19→12 contactpatient uses user✕
- Connections
- 2 pairs of types, where a type in contactpatient uses a type in user.
- The types involved
org.simple.clinic.contactpatient.CreateReminderForAppointment→org.simple.clinic.user.Userorg.simple.clinic.contactpatient.RecordPatientAgreedToVisit→org.simple.clinic.user.User
- Direction
- contactpatient uses user, so a change to user can break contactpatient, while a change to contactpatient can't break user.
- Position
- Below the diagonal: contactpatient uses a module listed above it, which is the healthy direction.
19→16 contactpatient uses overdue✕
- Connections
- 19 pairs of types, where a type in contactpatient uses a type in overdue.
- The types involved
org.simple.clinic.contactpatient.ContactPatientBottomSheet→org.simple.clinic.overdue.Appointmentorg.simple.clinic.contactpatient.ContactPatientBottomSheet→org.simple.clinic.overdue.AppointmentConfigorg.simple.clinic.contactpatient.ContactPatientBottomSheet→org.simple.clinic.overdue.TimeToAppointmentorg.simple.clinic.contactpatient.ContactPatientEffectHandler→org.simple.clinic.overdue.AppointmentRepositoryorg.simple.clinic.contactpatient.ContactPatientModel→org.simple.clinic.overdue.Appointmentorg.simple.clinic.contactpatient.ContactPatientModel→org.simple.clinic.overdue.PotentialAppointmentDateorg.simple.clinic.contactpatient.ContactPatientUi→org.simple.clinic.overdue.TimeToAppointmentorg.simple.clinic.contactpatient.ContactPatientUiActions→org.simple.clinic.overdue.Appointmentorg.simple.clinic.contactpatient.ContactPatientUiRenderer→org.simple.clinic.overdue.PotentialAppointmentDateorg.simple.clinic.contactpatient.ContactPatientUiRenderer→org.simple.clinic.overdue.TimeToAppointmentorg.simple.clinic.contactpatient.ContactPatientUpdate→org.simple.clinic.overdue.PotentialAppointmentDateorg.simple.clinic.contactpatient.CreateReminderForAppointment→org.simple.clinic.overdue.Appointmentorg.simple.clinic.contactpatient.CreateReminderForAppointment→org.simple.clinic.overdue.AppointmentRepositoryorg.simple.clinic.contactpatient.MarkPatientAsAgreedToVisit→org.simple.clinic.overdue.Appointmentorg.simple.clinic.contactpatient.OpenRemoveOverdueAppointmentScreen→org.simple.clinic.overdue.Appointmentorg.simple.clinic.contactpatient.OverdueAppointmentLoaded→org.simple.clinic.overdue.Appointmentorg.simple.clinic.contactpatient.RecordPatientAgreedToVisit→org.simple.clinic.overdue.Appointmentorg.simple.clinic.contactpatient.RecordPatientAgreedToVisit→org.simple.clinic.overdue.AppointmentRepositoryorg.simple.clinic.contactpatient.SetReminderForAppointment→org.simple.clinic.overdue.Appointment
- Direction
- contactpatient uses overdue, so a change to overdue can break contactpatient, while a change to contactpatient can't break overdue.
- Position
- Below the diagonal: contactpatient uses a module listed above it, which is the healthy direction.
19→18 contactpatient uses bloodsugar✕
- Connections
- 1 pair of types, where a type in contactpatient uses a type in bloodsugar.
- The types involved
org.simple.clinic.contactpatient.ContactPatientProfile→org.simple.clinic.bloodsugar.BloodSugarMeasurement
- Direction
- contactpatient uses bloodsugar, so a change to bloodsugar can break contactpatient, while a change to contactpatient can't break bloodsugar.
- Position
- Below the diagonal: contactpatient uses a module listed above it, which is the healthy direction.
19→20 contactpatient uses patient part of a loop✕
- Connections
- 6 pairs of types, where a type in contactpatient uses a type in patient.
- The types involved
org.simple.clinic.contactpatient.ContactPatientEffectHandler→org.simple.clinic.patient.PatientRepositoryorg.simple.clinic.contactpatient.ContactPatientProfile→org.simple.clinic.patient.Patientorg.simple.clinic.contactpatient.ContactPatientProfile→org.simple.clinic.patient.PatientAddressorg.simple.clinic.contactpatient.ContactPatientProfile→org.simple.clinic.patient.PatientPhoneNumberorg.simple.clinic.contactpatient.ContactPatientUiRenderer→org.simple.clinic.patient.PatientAddressorg.simple.clinic.contactpatient.PatientDetails→org.simple.clinic.patient.Gender
- Direction
- contactpatient uses patient, so a change to patient can break contactpatient, while a change to contactpatient can't break patient.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→21 contactpatient uses facility part of a loop✕
- Connections
- 4 pairs of types, where a type in contactpatient uses a type in facility.
- The types involved
org.simple.clinic.contactpatient.ContactPatientEffectHandler→org.simple.clinic.facility.Facilityorg.simple.clinic.contactpatient.ContactPatientModel→org.simple.clinic.facility.Facilityorg.simple.clinic.contactpatient.ContactPatientProfile→org.simple.clinic.facility.Facilityorg.simple.clinic.contactpatient.CurrentFacilityLoaded→org.simple.clinic.facility.Facility
- Direction
- contactpatient uses facility, so a change to facility can break contactpatient, while a change to contactpatient can't break facility.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→23 contactpatient uses feature part of a loop✕
- Connections
- 1 pair of types, where a type in contactpatient uses a type in feature.
- The types involved
org.simple.clinic.contactpatient.ContactPatientBottomSheet→org.simple.clinic.feature.Features
- Direction
- contactpatient uses feature, so a change to feature can break contactpatient, while a change to contactpatient can't break feature.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→25 contactpatient uses util part of a loop✕
- Connections
- 7 pairs of types, where a type in contactpatient uses a type in util.
- The types involved
org.simple.clinic.contactpatient.ContactPatientBottomSheet→org.simple.clinic.util.UserClockorg.simple.clinic.contactpatient.ContactPatientEffectHandler→org.simple.clinic.util.UserClockorg.simple.clinic.contactpatient.ContactPatientModel→org.simple.clinic.util.ParcelableOptionalorg.simple.clinic.contactpatient.ContactPatientUiRenderer→org.simple.clinic.util.UserClockorg.simple.clinic.contactpatient.CreateReminderForAppointment→org.simple.clinic.util.UtcClockorg.simple.clinic.contactpatient.RecordPatientAgreedToVisit→org.simple.clinic.util.UserClockorg.simple.clinic.contactpatient.RecordPatientAgreedToVisit→org.simple.clinic.util.UtcClock
- Direction
- contactpatient uses util, so a change to util can break contactpatient, while a change to contactpatient can't break util.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→31 contactpatient uses bp part of a loop✕
- Connections
- 1 pair of types, where a type in contactpatient uses a type in bp.
- The types involved
org.simple.clinic.contactpatient.ContactPatientProfile→org.simple.clinic.bp.BloodPressureMeasurement
- Direction
- contactpatient uses bp, so a change to bp can break contactpatient, while a change to contactpatient can't break bp.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→3 patient uses patient.businessid✕
- Connections
- 9 pairs of types, where a type in patient uses a type in patient.businessid.
- The types involved
org.simple.clinic.patient.OngoingNewPatientEntry→org.simple.clinic.patient.businessid.Identifierorg.simple.clinic.patient.PatientLineListRow→org.simple.clinic.patient.businessid.BusinessIdorg.simple.clinic.patient.PatientModule→org.simple.clinic.patient.businessid.BusinessIdMetaDataorg.simple.clinic.patient.PatientProfile→org.simple.clinic.patient.businessid.BusinessIdorg.simple.clinic.patient.PatientRepository→org.simple.clinic.patient.businessid.BusinessIdorg.simple.clinic.patient.PatientRepository→org.simple.clinic.patient.businessid.BusinessIdMetaDataorg.simple.clinic.patient.PatientRepository→org.simple.clinic.patient.businessid.Identifierorg.simple.clinic.patient.PatientSearchCriteria→org.simple.clinic.patient.businessid.Identifierorg.simple.clinic.patient.PatientSearchResult→org.simple.clinic.patient.businessid.Identifier
- Direction
- patient uses patient.businessid, so a change to patient.businessid can break patient, while a change to patient can't break patient.businessid.
- Position
- Below the diagonal: patient uses a module listed above it, which is the healthy direction.
20→6 patient uses medicalhistory✕
- Connections
- 3 pairs of types, where a type in patient uses a type in medicalhistory.
- The types involved
org.simple.clinic.patient.CompleteMedicalRecord→org.simple.clinic.medicalhistory.MedicalHistoryorg.simple.clinic.patient.PatientLineListRow→org.simple.clinic.medicalhistory.Answerorg.simple.clinic.patient.RecentPatient→org.simple.clinic.medicalhistory.Answer
- Direction
- patient uses medicalhistory, so a change to medicalhistory can break patient, while a change to patient can't break medicalhistory.
- Position
- Below the diagonal: patient uses a module listed above it, which is the healthy direction.
20→11 patient uses drugs✕
- Connections
- 1 pair of types, where a type in patient uses a type in drugs.
- The types involved
org.simple.clinic.patient.CompleteMedicalRecord→org.simple.clinic.drugs.PrescribedDrug
- Direction
- patient uses drugs, so a change to drugs can break patient, while a change to patient can't break drugs.
- Position
- Below the diagonal: patient uses a module listed above it, which is the healthy direction.
20→12 patient uses user✕
- Connections
- 1 pair of types, where a type in patient uses a type in user.
- The types involved
org.simple.clinic.patient.PatientRepository→org.simple.clinic.user.User
- Direction
- patient uses user, so a change to user can break patient, while a change to patient can't break user.
- Position
- Below the diagonal: patient uses a module listed above it, which is the healthy direction.
20→13 patient uses registration.phone✕
- Connections
- 1 pair of types, where a type in patient uses a type in registration.phone.
- The types involved
org.simple.clinic.patient.OngoingNewPatientEntry→org.simple.clinic.registration.phone.PhoneNumberValidator
- Direction
- patient uses registration.phone, so a change to registration.phone can break patient, while a change to patient can't break registration.phone.
- Position
- Below the diagonal: patient uses a module listed above it, which is the healthy direction.
20→14 patient uses sync✕
- Connections
- 1 pair of types, where a type in patient uses a type in sync.
- The types involved
org.simple.clinic.patient.PatientRepository→org.simple.clinic.sync.SynceableRepository
- Direction
- patient uses sync, so a change to sync can break patient, while a change to patient can't break sync.
- Position
- Below the diagonal: patient uses a module listed above it, which is the healthy direction.
20→16 patient uses overdue✕
- Connections
- 1 pair of types, where a type in patient uses a type in overdue.
- The types involved
org.simple.clinic.patient.CompleteMedicalRecord→org.simple.clinic.overdue.Appointment
- Direction
- patient uses overdue, so a change to overdue can break patient, while a change to patient can't break overdue.
- Position
- Below the diagonal: patient uses a module listed above it, which is the healthy direction.
20→18 patient uses bloodsugar✕
- Connections
- 1 pair of types, where a type in patient uses a type in bloodsugar.
- The types involved
org.simple.clinic.patient.CompleteMedicalRecord→org.simple.clinic.bloodsugar.BloodSugarMeasurement
- Direction
- patient uses bloodsugar, so a change to bloodsugar can break patient, while a change to patient can't break bloodsugar.
- Position
- Below the diagonal: patient uses a module listed above it, which is the healthy direction.
20→19 patient uses contactpatient✕
- Connections
- 1 pair of types, where a type in patient uses a type in contactpatient.
- The types involved
org.simple.clinic.patient.PatientRepository→org.simple.clinic.contactpatient.ContactPatientProfile
- Direction
- patient uses contactpatient, so a change to contactpatient can break patient, while a change to patient can't break contactpatient.
- Position
- Below the diagonal: patient uses a module listed above it, which is the healthy direction.
20→21 patient uses facility part of a loop✕
- Connections
- 1 pair of types, where a type in patient uses a type in facility.
- The types involved
org.simple.clinic.patient.PatientRepository→org.simple.clinic.facility.Facility
- Direction
- patient uses facility, so a change to facility can break patient, while a change to patient can't break facility.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→22 patient uses remoteconfig part of a loop✕
- Connections
- 1 pair of types, where a type in patient uses a type in remoteconfig.
- The types involved
org.simple.clinic.patient.PatientModule→org.simple.clinic.remoteconfig.ConfigReader
- Direction
- patient uses remoteconfig, so a change to remoteconfig can break patient, while a change to patient can't break remoteconfig.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→25 patient uses util part of a loop✕
- Connections
- 4 pairs of types, where a type in patient uses a type in util.
- The types involved
org.simple.clinic.patient.PatientAgeDetails→org.simple.clinic.util.UserClockorg.simple.clinic.patient.PatientAgeDetails→org.simple.clinic.util.UtcClockorg.simple.clinic.patient.PatientRepository→org.simple.clinic.util.UserClockorg.simple.clinic.patient.PatientRepository→org.simple.clinic.util.UtcClock
- Direction
- patient uses util, so a change to util can break patient, while a change to patient can't break util.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→31 patient uses bp part of a loop✕
- Connections
- 2 pairs of types, where a type in patient uses a type in bp.
- The types involved
org.simple.clinic.patient.CompleteMedicalRecord→org.simple.clinic.bp.BloodPressureMeasurementorg.simple.clinic.patient.PatientLineListRow→org.simple.clinic.bp.BloodPressureMeasurement
- Direction
- patient uses bp, so a change to bp can break patient, while a change to patient can't break bp.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→36 patient uses org.simple.clinic part of a loop✕
- Connections
- 1 pair of types, where a type in patient uses a type in org.simple.clinic.
- The types involved
org.simple.clinic.patient.PatientRepository→org.simple.clinic.AppDatabase
- Direction
- patient uses org.simple.clinic, so a change to org.simple.clinic can break patient, while a change to patient can't break org.simple.clinic.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
21→14 facility uses sync✕
- Connections
- 5 pairs of types, where a type in facility uses a type in sync.
- The types involved
org.simple.clinic.facility.FacilityPullResponse→org.simple.clinic.sync.DataPullResponseorg.simple.clinic.facility.FacilityRepository→org.simple.clinic.sync.SynceableRepositoryorg.simple.clinic.facility.FacilitySync→org.simple.clinic.sync.ModelSyncorg.simple.clinic.facility.FacilitySync→org.simple.clinic.sync.SyncConfigorg.simple.clinic.facility.FacilitySync→org.simple.clinic.sync.SyncCoordinator
- Direction
- facility uses sync, so a change to sync can break facility, while a change to facility can't break sync.
- Position
- Below the diagonal: facility uses a module listed above it, which is the healthy direction.
21→20 facility uses patient✕
- Connections
- 3 pairs of types, where a type in facility uses a type in patient.
- The types involved
org.simple.clinic.facility.Facility→org.simple.clinic.patient.SyncStatusorg.simple.clinic.facility.FacilityPayload→org.simple.clinic.patient.SyncStatusorg.simple.clinic.facility.FacilityRepository→org.simple.clinic.patient.SyncStatus
- Direction
- facility uses patient, so a change to patient can break facility, while a change to facility can't break patient.
- Position
- Below the diagonal: facility uses a module listed above it, which is the healthy direction.
21→36 facility uses org.simple.clinic part of a loop✕
- Connections
- 1 pair of types, where a type in facility uses a type in org.simple.clinic.
- The types involved
org.simple.clinic.facility.FacilityModule→org.simple.clinic.AppDatabase
- Direction
- facility uses org.simple.clinic, so a change to org.simple.clinic can break facility, while a change to facility can't break org.simple.clinic.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
22→5 remoteconfig uses util.scheduler✕
- Connections
- 1 pair of types, where a type in remoteconfig uses a type in util.scheduler.
- The types involved
org.simple.clinic.remoteconfig.UpdateFacilityRemoteConfig→org.simple.clinic.util.scheduler.SchedulersProvider
- Direction
- remoteconfig uses util.scheduler, so a change to util.scheduler can break remoteconfig, while a change to remoteconfig can't break util.scheduler.
- Position
- Below the diagonal: remoteconfig uses a module listed above it, which is the healthy direction.
22→21 remoteconfig uses facility✕
- Connections
- 1 pair of types, where a type in remoteconfig uses a type in facility.
- The types involved
org.simple.clinic.remoteconfig.UpdateFacilityRemoteConfig→org.simple.clinic.facility.Facility
- Direction
- remoteconfig uses facility, so a change to facility can break remoteconfig, while a change to remoteconfig can't break facility.
- Position
- Below the diagonal: remoteconfig uses a module listed above it, which is the healthy direction.
23→22 feature uses remoteconfig✕
- Connections
- 2 pairs of types, where a type in feature uses a type in remoteconfig.
- The types involved
org.simple.clinic.feature.Features→org.simple.clinic.remoteconfig.ConfigReaderorg.simple.clinic.feature.Features→org.simple.clinic.remoteconfig.RemoteConfigService
- Direction
- feature uses remoteconfig, so a change to remoteconfig can break feature, while a change to feature can't break remoteconfig.
- Position
- Below the diagonal: feature uses a module listed above it, which is the healthy direction.
24→1 registerorlogin uses mobius✕
- Connections
- 1 pair of types, where a type in registerorlogin uses a type in mobius.
- The types involved
org.simple.clinic.registerorlogin.AuthenticationActivity→org.simple.clinic.mobius.MobiusDelegate
- Direction
- registerorlogin uses mobius, so a change to mobius can break registerorlogin, while a change to registerorlogin can't break mobius.
- Position
- Below the diagonal: registerorlogin uses a module listed above it, which is the healthy direction.
24→5 registerorlogin uses util.scheduler✕
- Connections
- 1 pair of types, where a type in registerorlogin uses a type in util.scheduler.
- The types involved
org.simple.clinic.registerorlogin.AuthenticationEffectHandler→org.simple.clinic.util.scheduler.SchedulersProvider
- Direction
- registerorlogin uses util.scheduler, so a change to util.scheduler can break registerorlogin, while a change to registerorlogin can't break util.scheduler.
- Position
- Below the diagonal: registerorlogin uses a module listed above it, which is the healthy direction.
24→7 registerorlogin uses navigation.v2✕
- Connections
- 2 pairs of types, where a type in registerorlogin uses a type in navigation.v2.
- The types involved
org.simple.clinic.registerorlogin.AuthenticationActivity→org.simple.clinic.navigation.v2.Routerorg.simple.clinic.registerorlogin.AuthenticationActivity→org.simple.clinic.navigation.v2.ScreenResultBus
- Direction
- registerorlogin uses navigation.v2, so a change to navigation.v2 can break registerorlogin, while a change to registerorlogin can't break navigation.v2.
- Position
- Below the diagonal: registerorlogin uses a module listed above it, which is the healthy direction.
24→9 registerorlogin uses widgets✕
- Connections
- 1 pair of types, where a type in registerorlogin uses a type in widgets.
- The types involved
org.simple.clinic.registerorlogin.AuthenticationEvent→org.simple.clinic.widgets.UiEvent
- Direction
- registerorlogin uses widgets, so a change to widgets can break registerorlogin, while a change to registerorlogin can't break widgets.
- Position
- Below the diagonal: registerorlogin uses a module listed above it, which is the healthy direction.
24→23 registerorlogin uses feature✕
- Connections
- 1 pair of types, where a type in registerorlogin uses a type in feature.
- The types involved
org.simple.clinic.registerorlogin.AuthenticationActivity→org.simple.clinic.feature.Features
- Direction
- registerorlogin uses feature, so a change to feature can break registerorlogin, while a change to registerorlogin can't break feature.
- Position
- Below the diagonal: registerorlogin uses a module listed above it, which is the healthy direction.
25→5 util uses util.scheduler✕
- Connections
- 1 pair of types, where a type in util uses a type in util.scheduler.
- The types involved
org.simple.clinic.util.RuntimeNetworkStatus→org.simple.clinic.util.scheduler.SchedulersProvider
- Direction
- util uses util.scheduler, so a change to util.scheduler can break util, while a change to util can't break util.scheduler.
- Position
- Below the diagonal: util uses a module listed above it, which is the healthy direction.
25→7 util uses navigation.v2✕
- Connections
- 2 pairs of types, where a type in util uses a type in navigation.v2.
- The types involved
org.simple.clinic.util.AndroidExtensionsKt→org.simple.clinic.navigation.v2.ActivityResultorg.simple.clinic.util.FragmentExtKt→org.simple.clinic.navigation.v2.ScreenResult
- Direction
- util uses navigation.v2, so a change to navigation.v2 can break util, while a change to util can't break navigation.v2.
- Position
- Below the diagonal: util uses a module listed above it, which is the healthy direction.
25→16 util uses overdue✕
- Connections
- 1 pair of types, where a type in util uses a type in overdue.
- The types involved
org.simple.clinic.util.TimeFunctionsKt→org.simple.clinic.overdue.TimeToAppointment
- Direction
- util uses overdue, so a change to overdue can break util, while a change to util can't break overdue.
- Position
- Below the diagonal: util uses a module listed above it, which is the healthy direction.
25→23 util uses feature✕
- Connections
- 1 pair of types, where a type in util uses a type in feature.
- The types involved
org.simple.clinic.util.AndroidExtensionsKt→org.simple.clinic.feature.Features
- Direction
- util uses feature, so a change to feature can break util, while a change to util can't break feature.
- Position
- Below the diagonal: util uses a module listed above it, which is the healthy direction.
26→1 instantsearch uses mobius✕
- Connections
- 2 pairs of types, where a type in instantsearch uses a type in mobius.
- The types involved
org.simple.clinic.instantsearch.InstantSearchUiRenderer→org.simple.clinic.mobius.ViewRendererorg.simple.clinic.instantsearch.InstantSearchViewEffectHandler→org.simple.clinic.mobius.ViewEffectsHandler
- Direction
- instantsearch uses mobius, so a change to mobius can break instantsearch, while a change to instantsearch can't break mobius.
- Position
- Below the diagonal: instantsearch uses a module listed above it, which is the healthy direction.
26→3 instantsearch uses patient.businessid✕
- Connections
- 7 pairs of types, where a type in instantsearch uses a type in patient.businessid.
- The types involved
org.simple.clinic.instantsearch.InstantSearchModel→org.simple.clinic.patient.businessid.Identifierorg.simple.clinic.instantsearch.InstantSearchScreen→org.simple.clinic.patient.businessid.Identifierorg.simple.clinic.instantsearch.InstantSearchScreenKey→org.simple.clinic.patient.businessid.Identifierorg.simple.clinic.instantsearch.InstantSearchUiActions→org.simple.clinic.patient.businessid.Identifierorg.simple.clinic.instantsearch.InstantSearchUpdate→org.simple.clinic.patient.businessid.Identifierorg.simple.clinic.instantsearch.OpenLinkIdWithPatientScreen→org.simple.clinic.patient.businessid.Identifierorg.simple.clinic.instantsearch.OpenScannedQrCodeSheet→org.simple.clinic.patient.businessid.Identifier
- Direction
- instantsearch uses patient.businessid, so a change to patient.businessid can break instantsearch, while a change to instantsearch can't break patient.businessid.
- Position
- Below the diagonal: instantsearch uses a module listed above it, which is the healthy direction.
26→5 instantsearch uses util.scheduler✕
- Connections
- 1 pair of types, where a type in instantsearch uses a type in util.scheduler.
- The types involved
org.simple.clinic.instantsearch.InstantSearchEffectHandler→org.simple.clinic.util.scheduler.SchedulersProvider
- Direction
- instantsearch uses util.scheduler, so a change to util.scheduler can break instantsearch, while a change to instantsearch can't break util.scheduler.
- Position
- Below the diagonal: instantsearch uses a module listed above it, which is the healthy direction.
26→7 instantsearch uses navigation.v2✕
- Connections
- 3 pairs of types, where a type in instantsearch uses a type in navigation.v2.
- The types involved
org.simple.clinic.instantsearch.InstantSearchScreen→org.simple.clinic.navigation.v2.Routerorg.simple.clinic.instantsearch.InstantSearchScreen→org.simple.clinic.navigation.v2.ScreenResultBusorg.simple.clinic.instantsearch.InstantSearchScreenKey→org.simple.clinic.navigation.v2.ScreenKey
- Direction
- instantsearch uses navigation.v2, so a change to navigation.v2 can break instantsearch, while a change to instantsearch can't break navigation.v2.
- Position
- Below the diagonal: instantsearch uses a module listed above it, which is the healthy direction.
26→8 instantsearch uses navigation.v2.fragments✕
- Connections
- 1 pair of types, where a type in instantsearch uses a type in navigation.v2.fragments.
- The types involved
org.simple.clinic.instantsearch.InstantSearchScreen→org.simple.clinic.navigation.v2.fragments.BaseScreen
- Direction
- instantsearch uses navigation.v2.fragments, so a change to navigation.v2.fragments can break instantsearch, while a change to instantsearch can't break navigation.v2.fragments.
- Position
- Below the diagonal: instantsearch uses a module listed above it, which is the healthy direction.
26→9 instantsearch uses widgets✕
- Connections
- 2 pairs of types, where a type in instantsearch uses a type in widgets.
- The types involved
org.simple.clinic.instantsearch.InstantSearchEvent→org.simple.clinic.widgets.UiEventorg.simple.clinic.instantsearch.InstantSearchScreen→org.simple.clinic.widgets.UiEvent
- Direction
- instantsearch uses widgets, so a change to widgets can break instantsearch, while a change to instantsearch can't break widgets.
- Position
- Below the diagonal: instantsearch uses a module listed above it, which is the healthy direction.
26→20 instantsearch uses patient✕
- Connections
- 13 pairs of types, where a type in instantsearch uses a type in patient.
- The types involved
org.simple.clinic.instantsearch.AllPatientsInFacilityLoaded→org.simple.clinic.patient.PatientSearchResultorg.simple.clinic.instantsearch.InstantSearchEffectHandler→org.simple.clinic.patient.PatientProfileorg.simple.clinic.instantsearch.InstantSearchEffectHandler→org.simple.clinic.patient.PatientRepositoryorg.simple.clinic.instantsearch.InstantSearchModel→org.simple.clinic.patient.PatientPrefillInfoorg.simple.clinic.instantsearch.InstantSearchScreen→org.simple.clinic.patient.PatientSearchResultorg.simple.clinic.instantsearch.InstantSearchScreenKey→org.simple.clinic.patient.PatientPrefillInfoorg.simple.clinic.instantsearch.InstantSearchUiActions→org.simple.clinic.patient.PatientSearchResultorg.simple.clinic.instantsearch.InstantSearchUpdate→org.simple.clinic.patient.PatientSearchCriteriaorg.simple.clinic.instantsearch.SaveNewOngoingPatientEntry→org.simple.clinic.patient.OngoingNewPatientEntryorg.simple.clinic.instantsearch.SearchResultsLoaded→org.simple.clinic.patient.PatientSearchResultorg.simple.clinic.instantsearch.SearchWithCriteria→org.simple.clinic.patient.PatientSearchCriteriaorg.simple.clinic.instantsearch.ShowAllPatients→org.simple.clinic.patient.PatientSearchResultorg.simple.clinic.instantsearch.ShowPatientSearchResults→org.simple.clinic.patient.PatientSearchResult
- Direction
- instantsearch uses patient, so a change to patient can break instantsearch, while a change to instantsearch can't break patient.
- Position
- Below the diagonal: instantsearch uses a module listed above it, which is the healthy direction.
26→21 instantsearch uses facility✕
- Connections
- 10 pairs of types, where a type in instantsearch uses a type in facility.
- The types involved
org.simple.clinic.instantsearch.CurrentFacilityLoaded→org.simple.clinic.facility.Facilityorg.simple.clinic.instantsearch.InstantSearchEffectHandler→org.simple.clinic.facility.Facilityorg.simple.clinic.instantsearch.InstantSearchModel→org.simple.clinic.facility.Facilityorg.simple.clinic.instantsearch.InstantSearchScreen→org.simple.clinic.facility.Facilityorg.simple.clinic.instantsearch.InstantSearchUiActions→org.simple.clinic.facility.Facilityorg.simple.clinic.instantsearch.LoadAllPatients→org.simple.clinic.facility.Facilityorg.simple.clinic.instantsearch.OpenPatientEntryScreen→org.simple.clinic.facility.Facilityorg.simple.clinic.instantsearch.SearchWithCriteria→org.simple.clinic.facility.Facilityorg.simple.clinic.instantsearch.ShowAllPatients→org.simple.clinic.facility.Facilityorg.simple.clinic.instantsearch.ShowPatientSearchResults→org.simple.clinic.facility.Facility
- Direction
- instantsearch uses facility, so a change to facility can break instantsearch, while a change to instantsearch can't break facility.
- Position
- Below the diagonal: instantsearch uses a module listed above it, which is the healthy direction.
26→22 instantsearch uses remoteconfig✕
- Connections
- 1 pair of types, where a type in instantsearch uses a type in remoteconfig.
- The types involved
org.simple.clinic.instantsearch.InstantSearchConfigModule→org.simple.clinic.remoteconfig.ConfigReader
- Direction
- instantsearch uses remoteconfig, so a change to remoteconfig can break instantsearch, while a change to instantsearch can't break remoteconfig.
- Position
- Below the diagonal: instantsearch uses a module listed above it, which is the healthy direction.
26→23 instantsearch uses feature✕
- Connections
- 1 pair of types, where a type in instantsearch uses a type in feature.
- The types involved
org.simple.clinic.instantsearch.InstantSearchScreen→org.simple.clinic.feature.Features
- Direction
- instantsearch uses feature, so a change to feature can break instantsearch, while a change to instantsearch can't break feature.
- Position
- Below the diagonal: instantsearch uses a module listed above it, which is the healthy direction.
26→25 instantsearch uses util✕
- Connections
- 2 pairs of types, where a type in instantsearch uses a type in util.
- The types involved
org.simple.clinic.instantsearch.InstantSearchEffectHandler→org.simple.clinic.util.PagerFactoryorg.simple.clinic.instantsearch.InstantSearchScreen→org.simple.clinic.util.UtcClock
- Direction
- instantsearch uses util, so a change to util can break instantsearch, while a change to instantsearch can't break util.
- Position
- Below the diagonal: instantsearch uses a module listed above it, which is the healthy direction.
27→1 scanid uses mobius✕
- Connections
- 2 pairs of types, where a type in scanid uses a type in mobius.
- The types involved
org.simple.clinic.scanid.ScanSimpleIdUiRenderer→org.simple.clinic.mobius.ViewRendererorg.simple.clinic.scanid.ScanSimpleIdViewEffectHandler→org.simple.clinic.mobius.ViewEffectsHandler
- Direction
- scanid uses mobius, so a change to mobius can break scanid, while a change to scanid can't break mobius.
- Position
- Below the diagonal: scanid uses a module listed above it, which is the healthy direction.
27→3 scanid uses patient.businessid✕
- Connections
- 9 pairs of types, where a type in scanid uses a type in patient.businessid.
- The types involved
org.simple.clinic.scanid.GoBackToEditPatientScreen→org.simple.clinic.patient.businessid.Identifierorg.simple.clinic.scanid.OnlinePatientLookupWithIdentifier→org.simple.clinic.patient.businessid.Identifierorg.simple.clinic.scanid.OnlinePatientLookupWithIdentifierCompleted→org.simple.clinic.patient.businessid.Identifierorg.simple.clinic.scanid.OpenPatientSearch→org.simple.clinic.patient.businessid.Identifierorg.simple.clinic.scanid.PatientSearchByIdentifierCompleted→org.simple.clinic.patient.businessid.Identifierorg.simple.clinic.scanid.ScanSimpleIdScreen→org.simple.clinic.patient.businessid.Identifierorg.simple.clinic.scanid.ScanSimpleIdUiActions→org.simple.clinic.patient.businessid.Identifierorg.simple.clinic.scanid.ScanSimpleIdUpdate→org.simple.clinic.patient.businessid.Identifierorg.simple.clinic.scanid.SearchPatientByIdentifier→org.simple.clinic.patient.businessid.Identifier
- Direction
- scanid uses patient.businessid, so a change to patient.businessid can break scanid, while a change to scanid can't break patient.businessid.
- Position
- Below the diagonal: scanid uses a module listed above it, which is the healthy direction.
27→5 scanid uses util.scheduler✕
- Connections
- 1 pair of types, where a type in scanid uses a type in util.scheduler.
- The types involved
org.simple.clinic.scanid.ScanSimpleIdEffectHandler→org.simple.clinic.util.scheduler.SchedulersProvider
- Direction
- scanid uses util.scheduler, so a change to util.scheduler can break scanid, while a change to scanid can't break util.scheduler.
- Position
- Below the diagonal: scanid uses a module listed above it, which is the healthy direction.
27→7 scanid uses navigation.v2✕
- Connections
- 2 pairs of types, where a type in scanid uses a type in navigation.v2.
- The types involved
org.simple.clinic.scanid.ScanSimpleIdScreen→org.simple.clinic.navigation.v2.Routerorg.simple.clinic.scanid.ScanSimpleIdScreenKey→org.simple.clinic.navigation.v2.ScreenKey
- Direction
- scanid uses navigation.v2, so a change to navigation.v2 can break scanid, while a change to scanid can't break navigation.v2.
- Position
- Below the diagonal: scanid uses a module listed above it, which is the healthy direction.
27→8 scanid uses navigation.v2.fragments✕
- Connections
- 1 pair of types, where a type in scanid uses a type in navigation.v2.fragments.
- The types involved
org.simple.clinic.scanid.ScanSimpleIdScreen→org.simple.clinic.navigation.v2.fragments.BaseScreen
- Direction
- scanid uses navigation.v2.fragments, so a change to navigation.v2.fragments can break scanid, while a change to scanid can't break navigation.v2.fragments.
- Position
- Below the diagonal: scanid uses a module listed above it, which is the healthy direction.
27→9 scanid uses widgets✕
- Connections
- 2 pairs of types, where a type in scanid uses a type in widgets.
- The types involved
org.simple.clinic.scanid.ScanSimpleIdEvent→org.simple.clinic.widgets.UiEventorg.simple.clinic.scanid.ScanSimpleIdScreen→org.simple.clinic.widgets.UiEvent
- Direction
- scanid uses widgets, so a change to widgets can break scanid, while a change to scanid can't break widgets.
- Position
- Below the diagonal: scanid uses a module listed above it, which is the healthy direction.
27→20 scanid uses patient✕
- Connections
- 11 pairs of types, where a type in scanid uses a type in patient.
- The types involved
org.simple.clinic.scanid.CompleteMedicalRecordsSaved→org.simple.clinic.patient.CompleteMedicalRecordorg.simple.clinic.scanid.IndiaNHIDInfoPayload→org.simple.clinic.patient.PatientPrefillInfoorg.simple.clinic.scanid.OpenPatientSearch→org.simple.clinic.patient.PatientPrefillInfoorg.simple.clinic.scanid.PatientSearchByIdentifierCompleted→org.simple.clinic.patient.Patientorg.simple.clinic.scanid.SaveCompleteMedicalRecords→org.simple.clinic.patient.CompleteMedicalRecordorg.simple.clinic.scanid.ScanSimpleIdEffectHandler→org.simple.clinic.patient.PatientRepositoryorg.simple.clinic.scanid.ScanSimpleIdModel→org.simple.clinic.patient.PatientPrefillInfoorg.simple.clinic.scanid.ScanSimpleIdScreen→org.simple.clinic.patient.PatientPrefillInfoorg.simple.clinic.scanid.ScanSimpleIdUiActions→org.simple.clinic.patient.PatientPrefillInfoorg.simple.clinic.scanid.ScanSimpleIdUpdate→org.simple.clinic.patient.CompleteMedicalRecordorg.simple.clinic.scanid.ScanSimpleIdUpdate→org.simple.clinic.patient.Patient
- Direction
- scanid uses patient, so a change to patient can break scanid, while a change to scanid can't break patient.
- Position
- Below the diagonal: scanid uses a module listed above it, which is the healthy direction.
27→23 scanid uses feature✕
- Connections
- 1 pair of types, where a type in scanid uses a type in feature.
- The types involved
org.simple.clinic.scanid.ScanSimpleIdScreen→org.simple.clinic.feature.Features
- Direction
- scanid uses feature, so a change to feature can break scanid, while a change to scanid can't break feature.
- Position
- Below the diagonal: scanid uses a module listed above it, which is the healthy direction.
27→25 scanid uses util✕
- Connections
- 2 pairs of types, where a type in scanid uses a type in util.
- The types involved
org.simple.clinic.scanid.ScanSimpleIdScreen→org.simple.clinic.util.BitmapUtilsorg.simple.clinic.scanid.ScanSimpleIdScreen→org.simple.clinic.util.UtcClock
- Direction
- scanid uses util, so a change to util can break scanid, while a change to scanid can't break util.
- Position
- Below the diagonal: scanid uses a module listed above it, which is the healthy direction.
28→25 storage uses util✕
- Connections
- 3 pairs of types, where a type in storage uses a type in util.
- The types involved
org.simple.clinic.storage.DatabaseEncryptor→org.simple.clinic.util.MinimumMemoryCheckerorg.simple.clinic.storage.StorageModule→org.simple.clinic.util.MinimumMemoryCheckerorg.simple.clinic.storage.Timestamps→org.simple.clinic.util.UtcClock
- Direction
- storage uses util, so a change to util can break storage, while a change to storage can't break util.
- Position
- Below the diagonal: storage uses a module listed above it, which is the healthy direction.
28→36 storage uses org.simple.clinic part of a loop✕
- Connections
- 1 pair of types, where a type in storage uses a type in org.simple.clinic.
- The types involved
org.simple.clinic.storage.StorageModule→org.simple.clinic.AppDatabase
- Direction
- storage uses org.simple.clinic, so a change to org.simple.clinic can break storage, while a change to storage can't break org.simple.clinic.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
29→25 appconfig uses util✕
- Connections
- 1 pair of types, where a type in appconfig uses a type in util.
- The types involved
org.simple.clinic.appconfig.FetchError→org.simple.clinic.util.ResolvedError
- Direction
- appconfig uses util, so a change to util can break appconfig, while a change to appconfig can't break util.
- Position
- Below the diagonal: appconfig uses a module listed above it, which is the healthy direction.
29→28 appconfig uses storage✕
- Connections
- 1 pair of types, where a type in appconfig uses a type in storage.
- The types involved
org.simple.clinic.appconfig.AppLockModule→org.simple.clinic.storage.MemoryValue
- Direction
- appconfig uses storage, so a change to storage can break appconfig, while a change to appconfig can't break storage.
- Position
- Below the diagonal: appconfig uses a module listed above it, which is the healthy direction.
30→1 main uses mobius✕
- Connections
- 1 pair of types, where a type in main uses a type in mobius.
- The types involved
org.simple.clinic.main.TheActivityUiRenderer→org.simple.clinic.mobius.ViewRenderer
- Direction
- main uses mobius, so a change to mobius can break main, while a change to main can't break mobius.
- Position
- Below the diagonal: main uses a module listed above it, which is the healthy direction.
30→5 main uses util.scheduler✕
- Connections
- 1 pair of types, where a type in main uses a type in util.scheduler.
- The types involved
org.simple.clinic.main.TheActivityEffectHandler→org.simple.clinic.util.scheduler.SchedulersProvider
- Direction
- main uses util.scheduler, so a change to util.scheduler can break main, while a change to main can't break util.scheduler.
- Position
- Below the diagonal: main uses a module listed above it, which is the healthy direction.
30→7 main uses navigation.v2✕
- Connections
- 8 pairs of types, where a type in main uses a type in navigation.v2.
- The types involved
org.simple.clinic.main.InitialScreenInfoLoaded→org.simple.clinic.navigation.v2.Historyorg.simple.clinic.main.SetCurrentScreenHistory→org.simple.clinic.navigation.v2.Historyorg.simple.clinic.main.TheActivity→org.simple.clinic.navigation.v2.Historyorg.simple.clinic.main.TheActivity→org.simple.clinic.navigation.v2.Routerorg.simple.clinic.main.TheActivity→org.simple.clinic.navigation.v2.ScreenResultBusorg.simple.clinic.main.TheActivityEffectHandler→org.simple.clinic.navigation.v2.Historyorg.simple.clinic.main.TheActivityUiActions→org.simple.clinic.navigation.v2.Historyorg.simple.clinic.main.TheActivityUpdate→org.simple.clinic.navigation.v2.History
- Direction
- main uses navigation.v2, so a change to navigation.v2 can break main, while a change to main can't break navigation.v2.
- Position
- Below the diagonal: main uses a module listed above it, which is the healthy direction.
30→9 main uses widgets✕
- Connections
- 1 pair of types, where a type in main uses a type in widgets.
- The types involved
org.simple.clinic.main.TheActivityEvent→org.simple.clinic.widgets.UiEvent
- Direction
- main uses widgets, so a change to widgets can break main, while a change to main can't break widgets.
- Position
- Below the diagonal: main uses a module listed above it, which is the healthy direction.
30→12 main uses user✕
- Connections
- 5 pairs of types, where a type in main uses a type in user.
- The types involved
org.simple.clinic.main.InitialScreenInfoLoaded→org.simple.clinic.user.Userorg.simple.clinic.main.TheActivity→org.simple.clinic.user.UnauthorizeUserorg.simple.clinic.main.TheActivity→org.simple.clinic.user.UserSessionorg.simple.clinic.main.TheActivityEffectHandler→org.simple.clinic.user.UserSessionorg.simple.clinic.main.TheActivityUpdate→org.simple.clinic.user.User
- Direction
- main uses user, so a change to user can break main, while a change to main can't break user.
- Position
- Below the diagonal: main uses a module listed above it, which is the healthy direction.
30→14 main uses sync✕
- Connections
- 2 pairs of types, where a type in main uses a type in sync.
- The types involved
org.simple.clinic.main.TheActivity→org.simple.clinic.sync.DataSyncorg.simple.clinic.main.TheActivity→org.simple.clinic.sync.SyncSetup
- Direction
- main uses sync, so a change to sync can break main, while a change to main can't break sync.
- Position
- Below the diagonal: main uses a module listed above it, which is the healthy direction.
30→20 main uses patient✕
- Connections
- 1 pair of types, where a type in main uses a type in patient.
- The types involved
org.simple.clinic.main.TheActivityEffectHandler→org.simple.clinic.patient.PatientRepository
- Direction
- main uses patient, so a change to patient can break main, while a change to main can't break patient.
- Position
- Below the diagonal: main uses a module listed above it, which is the healthy direction.
30→23 main uses feature✕
- Connections
- 1 pair of types, where a type in main uses a type in feature.
- The types involved
org.simple.clinic.main.TheActivity→org.simple.clinic.feature.Features
- Direction
- main uses feature, so a change to feature can break main, while a change to main can't break feature.
- Position
- Below the diagonal: main uses a module listed above it, which is the healthy direction.
30→25 main uses util✕
- Connections
- 2 pairs of types, where a type in main uses a type in util.
- The types involved
org.simple.clinic.main.TheActivity→org.simple.clinic.util.UtcClockorg.simple.clinic.main.TheActivityEffectHandler→org.simple.clinic.util.UtcClock
- Direction
- main uses util, so a change to util can break main, while a change to main can't break util.
- Position
- Below the diagonal: main uses a module listed above it, which is the healthy direction.
30→28 main uses storage✕
- Connections
- 2 pairs of types, where a type in main uses a type in storage.
- The types involved
org.simple.clinic.main.TheActivity→org.simple.clinic.storage.MemoryValueorg.simple.clinic.main.TheActivityEffectHandler→org.simple.clinic.storage.MemoryValue
- Direction
- main uses storage, so a change to storage can break main, while a change to main can't break storage.
- Position
- Below the diagonal: main uses a module listed above it, which is the healthy direction.
31→5 bp uses util.scheduler✕
- Connections
- 1 pair of types, where a type in bp uses a type in util.scheduler.
- The types involved
org.simple.clinic.bp.BloodPressureHistoryListItemPagingSource→org.simple.clinic.util.scheduler.SchedulersProvider
- Direction
- bp uses util.scheduler, so a change to util.scheduler can break bp, while a change to bp can't break util.scheduler.
- Position
- Below the diagonal: bp uses a module listed above it, which is the healthy direction.
31→12 bp uses user✕
- Connections
- 1 pair of types, where a type in bp uses a type in user.
- The types involved
org.simple.clinic.bp.BloodPressureRepository→org.simple.clinic.user.User
- Direction
- bp uses user, so a change to user can break bp, while a change to bp can't break user.
- Position
- Below the diagonal: bp uses a module listed above it, which is the healthy direction.
31→14 bp uses sync✕
- Connections
- 1 pair of types, where a type in bp uses a type in sync.
- The types involved
org.simple.clinic.bp.BloodPressureRepository→org.simple.clinic.sync.SynceableRepository
- Direction
- bp uses sync, so a change to sync can break bp, while a change to bp can't break sync.
- Position
- Below the diagonal: bp uses a module listed above it, which is the healthy direction.
31→20 bp uses patient✕
- Connections
- 2 pairs of types, where a type in bp uses a type in patient.
- The types involved
org.simple.clinic.bp.BloodPressureMeasurement→org.simple.clinic.patient.SyncStatusorg.simple.clinic.bp.BloodPressureRepository→org.simple.clinic.patient.SyncStatus
- Direction
- bp uses patient, so a change to patient can break bp, while a change to bp can't break patient.
- Position
- Below the diagonal: bp uses a module listed above it, which is the healthy direction.
31→21 bp uses facility✕
- Connections
- 1 pair of types, where a type in bp uses a type in facility.
- The types involved
org.simple.clinic.bp.BloodPressureRepository→org.simple.clinic.facility.Facility
- Direction
- bp uses facility, so a change to facility can break bp, while a change to bp can't break facility.
- Position
- Below the diagonal: bp uses a module listed above it, which is the healthy direction.
31→25 bp uses util✕
- Connections
- 3 pairs of types, where a type in bp uses a type in util.
- The types involved
org.simple.clinic.bp.BloodPressureHistoryListItemPagingSource→org.simple.clinic.util.UserClockorg.simple.clinic.bp.BloodPressureHistoryListItemPagingSource→org.simple.clinic.util.UtcClockorg.simple.clinic.bp.BloodPressureRepository→org.simple.clinic.util.UtcClock
- Direction
- bp uses util, so a change to util can break bp, while a change to bp can't break util.
- Position
- Below the diagonal: bp uses a module listed above it, which is the healthy direction.
31→29 bp uses appconfig✕
- Connections
- 2 pairs of types, where a type in bp uses a type in appconfig.
- The types involved
org.simple.clinic.bp.BloodPressureHistoryListItemPagingSource→org.simple.clinic.appconfig.Countryorg.simple.clinic.bp.BloodPressureRepository→org.simple.clinic.appconfig.Country
- Direction
- bp uses appconfig, so a change to appconfig can break bp, while a change to bp can't break appconfig.
- Position
- Below the diagonal: bp uses a module listed above it, which is the healthy direction.
31→36 bp uses org.simple.clinic part of a loop✕
- Connections
- 1 pair of types, where a type in bp uses a type in org.simple.clinic.
- The types involved
org.simple.clinic.bp.BloodPressureHistoryListItemPagingSource→org.simple.clinic.AppDatabase
- Direction
- bp uses org.simple.clinic, so a change to org.simple.clinic can break bp, while a change to bp can't break org.simple.clinic.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
32→5 di uses util.scheduler✕
- Connections
- 1 pair of types, where a type in di uses a type in util.scheduler.
- The types involved
org.simple.clinic.di.AppModule→org.simple.clinic.util.scheduler.SchedulersProvider
- Direction
- di uses util.scheduler, so a change to util.scheduler can break di, while a change to di can't break util.scheduler.
- Position
- Below the diagonal: di uses a module listed above it, which is the healthy direction.
32→14 di uses sync✕
- Connections
- 2 pairs of types, where a type in di uses a type in sync.
- The types involved
org.simple.clinic.di.AppComponent→org.simple.clinic.sync.DataSyncorg.simple.clinic.di.AppComponent→org.simple.clinic.sync.SyncWorker
- Direction
- di uses sync, so a change to sync can break di, while a change to di can't break sync.
- Position
- Below the diagonal: di uses a module listed above it, which is the healthy direction.
32→22 di uses remoteconfig✕
- Connections
- 2 pairs of types, where a type in di uses a type in remoteconfig.
- The types involved
org.simple.clinic.di.AppComponent→org.simple.clinic.remoteconfig.UpdateRemoteConfigWorkerorg.simple.clinic.di.PagingModule→org.simple.clinic.remoteconfig.ConfigReader
- Direction
- di uses remoteconfig, so a change to remoteconfig can break di, while a change to di can't break remoteconfig.
- Position
- Below the diagonal: di uses a module listed above it, which is the healthy direction.
32→25 di uses util✕
- Connections
- 4 pairs of types, where a type in di uses a type in util.
- The types involved
org.simple.clinic.di.AppModule→org.simple.clinic.util.ElapsedRealtimeClockorg.simple.clinic.di.AppModule→org.simple.clinic.util.MinimumMemoryCheckerorg.simple.clinic.di.AppModule→org.simple.clinic.util.UserClockorg.simple.clinic.di.AppModule→org.simple.clinic.util.UtcClock
- Direction
- di uses util, so a change to util can break di, while a change to di can't break util.
- Position
- Below the diagonal: di uses a module listed above it, which is the healthy direction.
32→29 di uses appconfig✕
- Connections
- 1 pair of types, where a type in di uses a type in appconfig.
- The types involved
org.simple.clinic.di.DateFormatterModule→org.simple.clinic.appconfig.Country
- Direction
- di uses appconfig, so a change to appconfig can break di, while a change to di can't break appconfig.
- Position
- Below the diagonal: di uses a module listed above it, which is the healthy direction.
32→36 di uses org.simple.clinic part of a loop✕
- Connections
- 5 pairs of types, where a type in di uses a type in org.simple.clinic.
- The types involved
org.simple.clinic.di.AppComponent→org.simple.clinic.ClinicApporg.simple.clinic.di.DebugAppComponent→org.simple.clinic.DebugClinicApporg.simple.clinic.di.DebugAppComponent→org.simple.clinic.DebugNotificationActionReceiverorg.simple.clinic.di.DebugAppComponent→org.simple.clinic.FakeDataGenerationReceiverorg.simple.clinic.di.DebugAppComponent→org.simple.clinic.WebviewTestActivity
- Direction
- di uses org.simple.clinic, so a change to org.simple.clinic can break di, while a change to di can't break org.simple.clinic.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
33→1 editpatient uses mobius✕
- Connections
- 2 pairs of types, where a type in editpatient uses a type in mobius.
- The types involved
org.simple.clinic.editpatient.EditPatientViewEffectHandler→org.simple.clinic.mobius.ViewEffectsHandlerorg.simple.clinic.editpatient.EditPatientViewRenderer→org.simple.clinic.mobius.ViewRenderer
- Direction
- editpatient uses mobius, so a change to mobius can break editpatient, while a change to editpatient can't break mobius.
- Position
- Below the diagonal: editpatient uses a module listed above it, which is the healthy direction.
33→3 editpatient uses patient.businessid✕
- Connections
- 10 pairs of types, where a type in editpatient uses a type in patient.businessid.
- The types involved
org.simple.clinic.editpatient.BpPassportAdded→org.simple.clinic.patient.businessid.Identifierorg.simple.clinic.editpatient.BpPassportsFetched→org.simple.clinic.patient.businessid.BusinessIdorg.simple.clinic.editpatient.EditPatientEffectHandler→org.simple.clinic.patient.businessid.BusinessIdorg.simple.clinic.editpatient.EditPatientModel→org.simple.clinic.patient.businessid.BusinessIdorg.simple.clinic.editpatient.EditPatientModel→org.simple.clinic.patient.businessid.Identifierorg.simple.clinic.editpatient.EditPatientScreen→org.simple.clinic.patient.businessid.Identifierorg.simple.clinic.editpatient.EditPatientUi→org.simple.clinic.patient.businessid.Identifierorg.simple.clinic.editpatient.EditPatientViewRenderer→org.simple.clinic.patient.businessid.BusinessIdorg.simple.clinic.editpatient.EditablePatientEntry→org.simple.clinic.patient.businessid.Identifierorg.simple.clinic.editpatient.SavePatientEffect→org.simple.clinic.patient.businessid.BusinessId
- Direction
- editpatient uses patient.businessid, so a change to patient.businessid can break editpatient, while a change to editpatient can't break patient.businessid.
- Position
- Below the diagonal: editpatient uses a module listed above it, which is the healthy direction.
33→5 editpatient uses util.scheduler✕
- Connections
- 1 pair of types, where a type in editpatient uses a type in util.scheduler.
- The types involved
org.simple.clinic.editpatient.EditPatientEffectHandler→org.simple.clinic.util.scheduler.SchedulersProvider
- Direction
- editpatient uses util.scheduler, so a change to util.scheduler can break editpatient, while a change to editpatient can't break util.scheduler.
- Position
- Below the diagonal: editpatient uses a module listed above it, which is the healthy direction.
33→7 editpatient uses navigation.v2✕
- Connections
- 4 pairs of types, where a type in editpatient uses a type in navigation.v2.
- The types involved
org.simple.clinic.editpatient.ConfirmDiscardChangesDialog→org.simple.clinic.navigation.v2.Routerorg.simple.clinic.editpatient.EditPatientScreen→org.simple.clinic.navigation.v2.HandlesBackorg.simple.clinic.editpatient.EditPatientScreen→org.simple.clinic.navigation.v2.Routerorg.simple.clinic.editpatient.EditPatientScreen→org.simple.clinic.navigation.v2.ScreenResultBus
- Direction
- editpatient uses navigation.v2, so a change to navigation.v2 can break editpatient, while a change to editpatient can't break navigation.v2.
- Position
- Below the diagonal: editpatient uses a module listed above it, which is the healthy direction.
33→8 editpatient uses navigation.v2.fragments✕
- Connections
- 1 pair of types, where a type in editpatient uses a type in navigation.v2.fragments.
- The types involved
org.simple.clinic.editpatient.EditPatientScreen→org.simple.clinic.navigation.v2.fragments.BaseScreen
- Direction
- editpatient uses navigation.v2.fragments, so a change to navigation.v2.fragments can break editpatient, while a change to editpatient can't break navigation.v2.fragments.
- Position
- Below the diagonal: editpatient uses a module listed above it, which is the healthy direction.
33→9 editpatient uses widgets✕
- Connections
- 1 pair of types, where a type in editpatient uses a type in widgets.
- The types involved
org.simple.clinic.editpatient.EditPatientEvent→org.simple.clinic.widgets.UiEvent
- Direction
- editpatient uses widgets, so a change to widgets can break editpatient, while a change to editpatient can't break widgets.
- Position
- Below the diagonal: editpatient uses a module listed above it, which is the healthy direction.
33→12 editpatient uses user✕
- Connections
- 1 pair of types, where a type in editpatient uses a type in user.
- The types involved
org.simple.clinic.editpatient.EditPatientEffectHandler→org.simple.clinic.user.User
- Direction
- editpatient uses user, so a change to user can break editpatient, while a change to editpatient can't break user.
- Position
- Below the diagonal: editpatient uses a module listed above it, which is the healthy direction.
33→13 editpatient uses registration.phone✕
- Connections
- 3 pairs of types, where a type in editpatient uses a type in registration.phone.
- The types involved
org.simple.clinic.editpatient.EditPatientScreen→org.simple.clinic.registration.phone.PhoneNumberValidatororg.simple.clinic.editpatient.EditPatientUpdate→org.simple.clinic.registration.phone.PhoneNumberValidatororg.simple.clinic.editpatient.EditablePatientEntry→org.simple.clinic.registration.phone.PhoneNumberValidator
- Direction
- editpatient uses registration.phone, so a change to registration.phone can break editpatient, while a change to editpatient can't break registration.phone.
- Position
- Below the diagonal: editpatient uses a module listed above it, which is the healthy direction.
33→20 editpatient uses patient✕
- Connections
- 19 pairs of types, where a type in editpatient uses a type in patient.
- The types involved
org.simple.clinic.editpatient.EditPatientEffectHandler→org.simple.clinic.patient.Patientorg.simple.clinic.editpatient.EditPatientEffectHandler→org.simple.clinic.patient.PatientAddressorg.simple.clinic.editpatient.EditPatientEffectHandler→org.simple.clinic.patient.PatientAgeDetailsorg.simple.clinic.editpatient.EditPatientEffectHandler→org.simple.clinic.patient.PatientPhoneNumberorg.simple.clinic.editpatient.EditPatientEffectHandler→org.simple.clinic.patient.PatientProfileorg.simple.clinic.editpatient.EditPatientEffectHandler→org.simple.clinic.patient.PatientRepositoryorg.simple.clinic.editpatient.EditPatientInit→org.simple.clinic.patient.Patientorg.simple.clinic.editpatient.EditPatientModel→org.simple.clinic.patient.Genderorg.simple.clinic.editpatient.EditPatientModel→org.simple.clinic.patient.Patientorg.simple.clinic.editpatient.EditPatientModel→org.simple.clinic.patient.PatientAddressorg.simple.clinic.editpatient.EditPatientModel→org.simple.clinic.patient.PatientPhoneNumberorg.simple.clinic.editpatient.EditPatientScreen→org.simple.clinic.patient.Genderorg.simple.clinic.editpatient.EditPatientUi→org.simple.clinic.patient.Genderorg.simple.clinic.editpatient.EditablePatientEntry→org.simple.clinic.patient.Genderorg.simple.clinic.editpatient.EditablePatientEntry→org.simple.clinic.patient.PatientPhoneNumberorg.simple.clinic.editpatient.GenderChanged→org.simple.clinic.patient.Genderorg.simple.clinic.editpatient.SavePatientEffect→org.simple.clinic.patient.Patientorg.simple.clinic.editpatient.SavePatientEffect→org.simple.clinic.patient.PatientAddressorg.simple.clinic.editpatient.SavePatientEffect→org.simple.clinic.patient.PatientPhoneNumber
- Direction
- editpatient uses patient, so a change to patient can break editpatient, while a change to editpatient can't break patient.
- Position
- Below the diagonal: editpatient uses a module listed above it, which is the healthy direction.
33→23 editpatient uses feature✕
- Connections
- 1 pair of types, where a type in editpatient uses a type in feature.
- The types involved
org.simple.clinic.editpatient.EditPatientScreen→org.simple.clinic.feature.Features
- Direction
- editpatient uses feature, so a change to feature can break editpatient, while a change to editpatient can't break feature.
- Position
- Below the diagonal: editpatient uses a module listed above it, which is the healthy direction.
33→25 editpatient uses util✕
- Connections
- 2 pairs of types, where a type in editpatient uses a type in util.
- The types involved
org.simple.clinic.editpatient.EditPatientEffectHandler→org.simple.clinic.util.UtcClockorg.simple.clinic.editpatient.EditPatientScreen→org.simple.clinic.util.UserClock
- Direction
- editpatient uses util, so a change to util can break editpatient, while a change to editpatient can't break util.
- Position
- Below the diagonal: editpatient uses a module listed above it, which is the healthy direction.
33→27 editpatient uses scanid✕
- Connections
- 3 pairs of types, where a type in editpatient uses a type in scanid.
- The types involved
org.simple.clinic.editpatient.EditPatientScreen→org.simple.clinic.scanid.OpenedFromorg.simple.clinic.editpatient.EditPatientUi→org.simple.clinic.scanid.OpenedFromorg.simple.clinic.editpatient.OpenSimpleScanIdScreen→org.simple.clinic.scanid.OpenedFrom
- Direction
- editpatient uses scanid, so a change to scanid can break editpatient, while a change to editpatient can't break scanid.
- Position
- Below the diagonal: editpatient uses a module listed above it, which is the healthy direction.
33→29 editpatient uses appconfig✕
- Connections
- 2 pairs of types, where a type in editpatient uses a type in appconfig.
- The types involved
org.simple.clinic.editpatient.EditPatientEffectHandler→org.simple.clinic.appconfig.Countryorg.simple.clinic.editpatient.EditPatientScreen→org.simple.clinic.appconfig.Country
- Direction
- editpatient uses appconfig, so a change to appconfig can break editpatient, while a change to editpatient can't break appconfig.
- Position
- Below the diagonal: editpatient uses a module listed above it, which is the healthy direction.
34→1 home.overdue.search uses mobius✕
- Connections
- 2 pairs of types, where a type in home.overdue.search uses a type in mobius.
- The types involved
org.simple.clinic.home.overdue.search.OverdueSearchUiRenderer→org.simple.clinic.mobius.ViewRendererorg.simple.clinic.home.overdue.search.OverdueSearchViewEffectHandler→org.simple.clinic.mobius.ViewEffectsHandler
- Direction
- home.overdue.search uses mobius, so a change to mobius can break home.overdue.search, while a change to home.overdue.search can't break mobius.
- Position
- Below the diagonal: home.overdue.search uses a module listed above it, which is the healthy direction.
34→5 home.overdue.search uses util.scheduler✕
- Connections
- 1 pair of types, where a type in home.overdue.search uses a type in util.scheduler.
- The types involved
org.simple.clinic.home.overdue.search.OverdueSearchEffectHandler→org.simple.clinic.util.scheduler.SchedulersProvider
- Direction
- home.overdue.search uses util.scheduler, so a change to util.scheduler can break home.overdue.search, while a change to home.overdue.search can't break util.scheduler.
- Position
- Below the diagonal: home.overdue.search uses a module listed above it, which is the healthy direction.
34→7 home.overdue.search uses navigation.v2✕
- Connections
- 2 pairs of types, where a type in home.overdue.search uses a type in navigation.v2.
- The types involved
org.simple.clinic.home.overdue.search.OverdueSearchScreen→org.simple.clinic.navigation.v2.Routerorg.simple.clinic.home.overdue.search.OverdueSearchScreen→org.simple.clinic.navigation.v2.ScreenResultBus
- Direction
- home.overdue.search uses navigation.v2, so a change to navigation.v2 can break home.overdue.search, while a change to home.overdue.search can't break navigation.v2.
- Position
- Below the diagonal: home.overdue.search uses a module listed above it, which is the healthy direction.
34→8 home.overdue.search uses navigation.v2.fragments✕
- Connections
- 1 pair of types, where a type in home.overdue.search uses a type in navigation.v2.fragments.
- The types involved
org.simple.clinic.home.overdue.search.OverdueSearchScreen→org.simple.clinic.navigation.v2.fragments.BaseScreen
- Direction
- home.overdue.search uses navigation.v2.fragments, so a change to navigation.v2.fragments can break home.overdue.search, while a change to home.overdue.search can't break navigation.v2.fragments.
- Position
- Below the diagonal: home.overdue.search uses a module listed above it, which is the healthy direction.
34→9 home.overdue.search uses widgets✕
- Connections
- 2 pairs of types, where a type in home.overdue.search uses a type in widgets.
- The types involved
org.simple.clinic.home.overdue.search.OverdueSearchEvent→org.simple.clinic.widgets.UiEventorg.simple.clinic.home.overdue.search.OverdueSearchScreen→org.simple.clinic.widgets.UiEvent
- Direction
- home.overdue.search uses widgets, so a change to widgets can break home.overdue.search, while a change to home.overdue.search can't break widgets.
- Position
- Below the diagonal: home.overdue.search uses a module listed above it, which is the healthy direction.
34→15 home.overdue.search uses home.overdue✕
- Connections
- 4 pairs of types, where a type in home.overdue.search uses a type in home.overdue.
- The types involved
org.simple.clinic.home.overdue.search.OverdueSearchModel→org.simple.clinic.home.overdue.OverdueAppointmentorg.simple.clinic.home.overdue.search.OverdueSearchResultsLoaded→org.simple.clinic.home.overdue.OverdueAppointmentorg.simple.clinic.home.overdue.search.OverdueSearchScreen→org.simple.clinic.home.overdue.OverdueAppointmentorg.simple.clinic.home.overdue.search.OverdueSearchUi→org.simple.clinic.home.overdue.OverdueAppointment
- Direction
- home.overdue.search uses home.overdue, so a change to home.overdue can break home.overdue.search, while a change to home.overdue.search can't break home.overdue.
- Position
- Below the diagonal: home.overdue.search uses a module listed above it, which is the healthy direction.
34→16 home.overdue.search uses overdue✕
- Connections
- 2 pairs of types, where a type in home.overdue.search uses a type in overdue.
- The types involved
org.simple.clinic.home.overdue.search.OverdueSearchEffectHandler→org.simple.clinic.overdue.AppointmentRepositoryorg.simple.clinic.home.overdue.search.OverdueSearchEffectHandler→org.simple.clinic.overdue.OverdueAppointmentSelector
- Direction
- home.overdue.search uses overdue, so a change to overdue can break home.overdue.search, while a change to home.overdue.search can't break overdue.
- Position
- Below the diagonal: home.overdue.search uses a module listed above it, which is the healthy direction.
34→20 home.overdue.search uses patient✕
- Connections
- 1 pair of types, where a type in home.overdue.search uses a type in patient.
- The types involved
org.simple.clinic.home.overdue.search.OverdueSearchEffectHandler→org.simple.clinic.patient.PatientRepository
- Direction
- home.overdue.search uses patient, so a change to patient can break home.overdue.search, while a change to home.overdue.search can't break patient.
- Position
- Below the diagonal: home.overdue.search uses a module listed above it, which is the healthy direction.
34→21 home.overdue.search uses facility✕
- Connections
- 1 pair of types, where a type in home.overdue.search uses a type in facility.
- The types involved
org.simple.clinic.home.overdue.search.OverdueSearchEffectHandler→org.simple.clinic.facility.Facility
- Direction
- home.overdue.search uses facility, so a change to facility can break home.overdue.search, while a change to home.overdue.search can't break facility.
- Position
- Below the diagonal: home.overdue.search uses a module listed above it, which is the healthy direction.
34→22 home.overdue.search uses remoteconfig✕
- Connections
- 1 pair of types, where a type in home.overdue.search uses a type in remoteconfig.
- The types involved
org.simple.clinic.home.overdue.search.OverdueSearchModule→org.simple.clinic.remoteconfig.ConfigReader
- Direction
- home.overdue.search uses remoteconfig, so a change to remoteconfig can break home.overdue.search, while a change to home.overdue.search can't break remoteconfig.
- Position
- Below the diagonal: home.overdue.search uses a module listed above it, which is the healthy direction.
34→23 home.overdue.search uses feature✕
- Connections
- 1 pair of types, where a type in home.overdue.search uses a type in feature.
- The types involved
org.simple.clinic.home.overdue.search.OverdueSearchScreen→org.simple.clinic.feature.Features
- Direction
- home.overdue.search uses feature, so a change to feature can break home.overdue.search, while a change to home.overdue.search can't break feature.
- Position
- Below the diagonal: home.overdue.search uses a module listed above it, which is the healthy direction.
34→25 home.overdue.search uses util✕
- Connections
- 5 pairs of types, where a type in home.overdue.search uses a type in util.
- The types involved
org.simple.clinic.home.overdue.search.DownloadButtonClicked→org.simple.clinic.util.RequiresNetworkorg.simple.clinic.home.overdue.search.OverdueSearchEffectHandler→org.simple.clinic.util.PagerFactoryorg.simple.clinic.home.overdue.search.OverdueSearchScreen→org.simple.clinic.util.RuntimeNetworkStatusorg.simple.clinic.home.overdue.search.OverdueSearchScreen→org.simple.clinic.util.UserClockorg.simple.clinic.home.overdue.search.ShareButtonClicked→org.simple.clinic.util.RequiresNetwork
- Direction
- home.overdue.search uses util, so a change to util can break home.overdue.search, while a change to home.overdue.search can't break util.
- Position
- Below the diagonal: home.overdue.search uses a module listed above it, which is the healthy direction.
34→29 home.overdue.search uses appconfig✕
- Connections
- 1 pair of types, where a type in home.overdue.search uses a type in appconfig.
- The types involved
org.simple.clinic.home.overdue.search.OverdueSearchScreen→org.simple.clinic.appconfig.Country
- Direction
- home.overdue.search uses appconfig, so a change to appconfig can break home.overdue.search, while a change to home.overdue.search can't break appconfig.
- Position
- Below the diagonal: home.overdue.search uses a module listed above it, which is the healthy direction.
35→1 newentry uses mobius✕
- Connections
- 2 pairs of types, where a type in newentry uses a type in mobius.
- The types involved
org.simple.clinic.newentry.PatientEntryUiRenderer→org.simple.clinic.mobius.ViewRendererorg.simple.clinic.newentry.PatientEntryViewEffectHandler→org.simple.clinic.mobius.ViewEffectsHandler
- Direction
- newentry uses mobius, so a change to mobius can break newentry, while a change to newentry can't break mobius.
- Position
- Below the diagonal: newentry uses a module listed above it, which is the healthy direction.
35→3 newentry uses patient.businessid✕
- Connections
- 4 pairs of types, where a type in newentry uses a type in patient.businessid.
- The types involved
org.simple.clinic.newentry.AlternativeIdChanged→org.simple.clinic.patient.businessid.Identifierorg.simple.clinic.newentry.PatientEntryModel→org.simple.clinic.patient.businessid.Identifierorg.simple.clinic.newentry.PatientEntryScreen→org.simple.clinic.patient.businessid.Identifierorg.simple.clinic.newentry.PatientEntryUiRenderer→org.simple.clinic.patient.businessid.Identifier
- Direction
- newentry uses patient.businessid, so a change to patient.businessid can break newentry, while a change to newentry can't break patient.businessid.
- Position
- Below the diagonal: newentry uses a module listed above it, which is the healthy direction.
35→5 newentry uses util.scheduler✕
- Connections
- 1 pair of types, where a type in newentry uses a type in util.scheduler.
- The types involved
org.simple.clinic.newentry.PatientEntryEffectHandler→org.simple.clinic.util.scheduler.SchedulersProvider
- Direction
- newentry uses util.scheduler, so a change to util.scheduler can break newentry, while a change to newentry can't break util.scheduler.
- Position
- Below the diagonal: newentry uses a module listed above it, which is the healthy direction.
35→7 newentry uses navigation.v2✕
- Connections
- 1 pair of types, where a type in newentry uses a type in navigation.v2.
- The types involved
org.simple.clinic.newentry.PatientEntryScreen→org.simple.clinic.navigation.v2.Router
- Direction
- newentry uses navigation.v2, so a change to navigation.v2 can break newentry, while a change to newentry can't break navigation.v2.
- Position
- Below the diagonal: newentry uses a module listed above it, which is the healthy direction.
35→8 newentry uses navigation.v2.fragments✕
- Connections
- 1 pair of types, where a type in newentry uses a type in navigation.v2.fragments.
- The types involved
org.simple.clinic.newentry.PatientEntryScreen→org.simple.clinic.navigation.v2.fragments.BaseScreen
- Direction
- newentry uses navigation.v2.fragments, so a change to navigation.v2.fragments can break newentry, while a change to newentry can't break navigation.v2.fragments.
- Position
- Below the diagonal: newentry uses a module listed above it, which is the healthy direction.
35→9 newentry uses widgets✕
- Connections
- 1 pair of types, where a type in newentry uses a type in widgets.
- The types involved
org.simple.clinic.newentry.PatientEntryEvent→org.simple.clinic.widgets.UiEvent
- Direction
- newentry uses widgets, so a change to widgets can break newentry, while a change to newentry can't break widgets.
- Position
- Below the diagonal: newentry uses a module listed above it, which is the healthy direction.
35→13 newentry uses registration.phone✕
- Connections
- 2 pairs of types, where a type in newentry uses a type in registration.phone.
- The types involved
org.simple.clinic.newentry.PatientEntryScreen→org.simple.clinic.registration.phone.PhoneNumberValidatororg.simple.clinic.newentry.PatientEntryUpdate→org.simple.clinic.registration.phone.PhoneNumberValidator
- Direction
- newentry uses registration.phone, so a change to registration.phone can break newentry, while a change to newentry can't break registration.phone.
- Position
- Below the diagonal: newentry uses a module listed above it, which is the healthy direction.
35→20 newentry uses patient✕
- Connections
- 16 pairs of types, where a type in newentry uses a type in patient.
- The types involved
org.simple.clinic.newentry.GenderChanged→org.simple.clinic.patient.Genderorg.simple.clinic.newentry.OngoingEntryFetched→org.simple.clinic.patient.OngoingNewPatientEntryorg.simple.clinic.newentry.PatientEntryEffectHandler→org.simple.clinic.patient.PatientRepositoryorg.simple.clinic.newentry.PatientEntryModel→org.simple.clinic.patient.Genderorg.simple.clinic.newentry.PatientEntryModel→org.simple.clinic.patient.OngoingNewPatientEntryorg.simple.clinic.newentry.PatientEntryModel→org.simple.clinic.patient.ReminderConsentorg.simple.clinic.newentry.PatientEntryScreen→org.simple.clinic.patient.Genderorg.simple.clinic.newentry.PatientEntryScreen→org.simple.clinic.patient.OngoingNewPatientEntryorg.simple.clinic.newentry.PatientEntryUiActions→org.simple.clinic.patient.OngoingNewPatientEntryorg.simple.clinic.newentry.PatientEntryUpdate→org.simple.clinic.patient.Genderorg.simple.clinic.newentry.PatientEntryUpdate→org.simple.clinic.patient.OngoingNewPatientEntryorg.simple.clinic.newentry.PatientEntryViewEffectHandler→org.simple.clinic.patient.PatientEntryValidationErrororg.simple.clinic.newentry.PrefillFields→org.simple.clinic.patient.OngoingNewPatientEntryorg.simple.clinic.newentry.ReminderConsentChanged→org.simple.clinic.patient.ReminderConsentorg.simple.clinic.newentry.SavePatient→org.simple.clinic.patient.OngoingNewPatientEntryorg.simple.clinic.newentry.ShowValidationErrors→org.simple.clinic.patient.PatientEntryValidationError
- Direction
- newentry uses patient, so a change to patient can break newentry, while a change to newentry can't break patient.
- Position
- Below the diagonal: newentry uses a module listed above it, which is the healthy direction.
35→21 newentry uses facility✕
- Connections
- 1 pair of types, where a type in newentry uses a type in facility.
- The types involved
org.simple.clinic.newentry.PatientEntryEffectHandler→org.simple.clinic.facility.FacilityRepository
- Direction
- newentry uses facility, so a change to facility can break newentry, while a change to newentry can't break facility.
- Position
- Below the diagonal: newentry uses a module listed above it, which is the healthy direction.
35→23 newentry uses feature✕
- Connections
- 1 pair of types, where a type in newentry uses a type in feature.
- The types involved
org.simple.clinic.newentry.PatientEntryScreen→org.simple.clinic.feature.Features
- Direction
- newentry uses feature, so a change to feature can break newentry, while a change to newentry can't break feature.
- Position
- Below the diagonal: newentry uses a module listed above it, which is the healthy direction.
35→25 newentry uses util✕
- Connections
- 2 pairs of types, where a type in newentry uses a type in util.
- The types involved
org.simple.clinic.newentry.PatientEntryUiRenderer→org.simple.clinic.util.ValueChangedCallbackorg.simple.clinic.newentry.PatientEntryViewEffectHandler→org.simple.clinic.util.ValueChangedCallback
- Direction
- newentry uses util, so a change to util can break newentry, while a change to newentry can't break util.
- Position
- Below the diagonal: newentry uses a module listed above it, which is the healthy direction.
35→29 newentry uses appconfig✕
- Connections
- 1 pair of types, where a type in newentry uses a type in appconfig.
- The types involved
org.simple.clinic.newentry.PatientEntryScreen→org.simple.clinic.appconfig.Country
- Direction
- newentry uses appconfig, so a change to appconfig can break newentry, while a change to newentry can't break appconfig.
- Position
- Below the diagonal: newentry uses a module listed above it, which is the healthy direction.
36→5 org.simple.clinic uses util.scheduler✕
- Connections
- 2 pairs of types, where a type in org.simple.clinic uses a type in util.scheduler.
- The types involved
org.simple.clinic.ClinicApp→org.simple.clinic.util.scheduler.SchedulersProviderorg.simple.clinic.FakeDataGenerationReceiver→org.simple.clinic.util.scheduler.SchedulersProvider
- Direction
- org.simple.clinic uses util.scheduler, so a change to util.scheduler can break org.simple.clinic, while a change to org.simple.clinic can't break util.scheduler.
- Position
- Below the diagonal: org.simple.clinic uses a module listed above it, which is the healthy direction.
36→9 org.simple.clinic uses widgets✕
- Connections
- 2 pairs of types, where a type in org.simple.clinic uses a type in widgets.
- The types involved
org.simple.clinic.ReplayUntilScreenIsDestroyed→org.simple.clinic.widgets.UiEventorg.simple.clinic.ReportAnalyticsEvents→org.simple.clinic.widgets.UiEvent
- Direction
- org.simple.clinic uses widgets, so a change to widgets can break org.simple.clinic, while a change to org.simple.clinic can't break widgets.
- Position
- Below the diagonal: org.simple.clinic uses a module listed above it, which is the healthy direction.
36→12 org.simple.clinic uses user✕
- Connections
- 1 pair of types, where a type in org.simple.clinic uses a type in user.
- The types involved
org.simple.clinic.FakeDataGenerationReceiver→org.simple.clinic.user.User
- Direction
- org.simple.clinic uses user, so a change to user can break org.simple.clinic, while a change to org.simple.clinic can't break user.
- Position
- Below the diagonal: org.simple.clinic uses a module listed above it, which is the healthy direction.
36→14 org.simple.clinic uses sync✕
- Connections
- 1 pair of types, where a type in org.simple.clinic uses a type in sync.
- The types involved
org.simple.clinic.DebugNotificationActionReceiver→org.simple.clinic.sync.DataSync
- Direction
- org.simple.clinic uses sync, so a change to sync can break org.simple.clinic, while a change to org.simple.clinic can't break sync.
- Position
- Below the diagonal: org.simple.clinic uses a module listed above it, which is the healthy direction.
36→16 org.simple.clinic uses overdue✕
- Connections
- 2 pairs of types, where a type in org.simple.clinic uses a type in overdue.
- The types involved
org.simple.clinic.FakeDataGenerationReceiver→org.simple.clinic.overdue.Appointmentorg.simple.clinic.FakeDataGenerationReceiver→org.simple.clinic.overdue.AppointmentRepository
- Direction
- org.simple.clinic uses overdue, so a change to overdue can break org.simple.clinic, while a change to org.simple.clinic can't break overdue.
- Position
- Below the diagonal: org.simple.clinic uses a module listed above it, which is the healthy direction.
36→20 org.simple.clinic uses patient✕
- Connections
- 5 pairs of types, where a type in org.simple.clinic uses a type in patient.
- The types involved
org.simple.clinic.FakeDataGenerationReceiver→org.simple.clinic.patient.Genderorg.simple.clinic.FakeDataGenerationReceiver→org.simple.clinic.patient.Patientorg.simple.clinic.FakeDataGenerationReceiver→org.simple.clinic.patient.PatientAddressorg.simple.clinic.FakeDataGenerationReceiver→org.simple.clinic.patient.PatientPhoneNumberorg.simple.clinic.FakeDataGenerationReceiver→org.simple.clinic.patient.PatientRepository
- Direction
- org.simple.clinic uses patient, so a change to patient can break org.simple.clinic, while a change to org.simple.clinic can't break patient.
- Position
- Below the diagonal: org.simple.clinic uses a module listed above it, which is the healthy direction.
36→21 org.simple.clinic uses facility✕
- Connections
- 4 pairs of types, where a type in org.simple.clinic uses a type in facility.
- The types involved
org.simple.clinic.AppDatabase→org.simple.clinic.facility.Facilityorg.simple.clinic.FakeDataGenerationReceiver→org.simple.clinic.facility.Facilityorg.simple.clinic.FakeDataGenerationReceiver→org.simple.clinic.facility.FacilityRepositoryorg.simple.clinic.GlobalsKt→org.simple.clinic.facility.Facility
- Direction
- org.simple.clinic uses facility, so a change to facility can break org.simple.clinic, while a change to org.simple.clinic can't break facility.
- Position
- Below the diagonal: org.simple.clinic uses a module listed above it, which is the healthy direction.
36→22 org.simple.clinic uses remoteconfig✕
- Connections
- 2 pairs of types, where a type in org.simple.clinic uses a type in remoteconfig.
- The types involved
org.simple.clinic.ClinicApp→org.simple.clinic.remoteconfig.ConfigReaderorg.simple.clinic.ClinicApp→org.simple.clinic.remoteconfig.UpdateFacilityRemoteConfig
- Direction
- org.simple.clinic uses remoteconfig, so a change to remoteconfig can break org.simple.clinic, while a change to org.simple.clinic can't break remoteconfig.
- Position
- Below the diagonal: org.simple.clinic uses a module listed above it, which is the healthy direction.
36→23 org.simple.clinic uses feature✕
- Connections
- 1 pair of types, where a type in org.simple.clinic uses a type in feature.
- The types involved
org.simple.clinic.WebviewTestActivity→org.simple.clinic.feature.Features
- Direction
- org.simple.clinic uses feature, so a change to feature can break org.simple.clinic, while a change to org.simple.clinic can't break feature.
- Position
- Below the diagonal: org.simple.clinic uses a module listed above it, which is the healthy direction.
36→25 org.simple.clinic uses util✕
- Connections
- 2 pairs of types, where a type in org.simple.clinic uses a type in util.
- The types involved
org.simple.clinic.DebugClinicApp→org.simple.clinic.util.AppSignatureorg.simple.clinic.FakeDataGenerationReceiver→org.simple.clinic.util.UtcClock
- Direction
- org.simple.clinic uses util, so a change to util can break org.simple.clinic, while a change to org.simple.clinic can't break util.
- Position
- Below the diagonal: org.simple.clinic uses a module listed above it, which is the healthy direction.
36→28 org.simple.clinic uses storage✕
- Connections
- 1 pair of types, where a type in org.simple.clinic uses a type in storage.
- The types involved
org.simple.clinic.ClinicApp→org.simple.clinic.storage.DatabaseEncryptor
- Direction
- org.simple.clinic uses storage, so a change to storage can break org.simple.clinic, while a change to org.simple.clinic can't break storage.
- Position
- Below the diagonal: org.simple.clinic uses a module listed above it, which is the healthy direction.
36→31 org.simple.clinic uses bp✕
- Connections
- 2 pairs of types, where a type in org.simple.clinic uses a type in bp.
- The types involved
org.simple.clinic.FakeDataGenerationReceiver→org.simple.clinic.bp.BloodPressureMeasurementorg.simple.clinic.FakeDataGenerationReceiver→org.simple.clinic.bp.BloodPressureRepository
- Direction
- org.simple.clinic uses bp, so a change to bp can break org.simple.clinic, while a change to org.simple.clinic can't break bp.
- Position
- Below the diagonal: org.simple.clinic uses a module listed above it, which is the healthy direction.
36→32 org.simple.clinic uses di✕
- Connections
- 3 pairs of types, where a type in org.simple.clinic uses a type in di.
- The types involved
org.simple.clinic.ClinicApp→org.simple.clinic.di.AppComponentorg.simple.clinic.DebugClinicApp→org.simple.clinic.di.AppComponentorg.simple.clinic.ReleaseClinicApp→org.simple.clinic.di.AppComponent
- Direction
- org.simple.clinic uses di, so a change to di can break org.simple.clinic, while a change to org.simple.clinic can't break di.
- Position
- Below the diagonal: org.simple.clinic uses a module listed above it, which is the healthy direction.
37→1 bp.entry uses mobius✕
- Connections
- 1 pair of types, where a type in bp.entry uses a type in mobius.
- The types involved
org.simple.clinic.bp.entry.BloodPressureEntryUiRenderer→org.simple.clinic.mobius.ViewRenderer
- Direction
- bp.entry uses mobius, so a change to mobius can break bp.entry, while a change to bp.entry can't break mobius.
- Position
- Below the diagonal: bp.entry uses a module listed above it, which is the healthy direction.
37→5 bp.entry uses util.scheduler✕
- Connections
- 1 pair of types, where a type in bp.entry uses a type in util.scheduler.
- The types involved
org.simple.clinic.bp.entry.BloodPressureEntryEffectHandler→org.simple.clinic.util.scheduler.SchedulersProvider
- Direction
- bp.entry uses util.scheduler, so a change to util.scheduler can break bp.entry, while a change to bp.entry can't break util.scheduler.
- Position
- Below the diagonal: bp.entry uses a module listed above it, which is the healthy direction.
37→9 bp.entry uses widgets✕
- Connections
- 3 pairs of types, where a type in bp.entry uses a type in widgets.
- The types involved
org.simple.clinic.bp.entry.BloodPressureEntryEvent→org.simple.clinic.widgets.UiEventorg.simple.clinic.bp.entry.BloodPressureEntrySheet→org.simple.clinic.widgets.BottomSheetActivityorg.simple.clinic.bp.entry.BloodPressureEntrySheet→org.simple.clinic.widgets.UiEvent
- Direction
- bp.entry uses widgets, so a change to widgets can break bp.entry, while a change to bp.entry can't break widgets.
- Position
- Below the diagonal: bp.entry uses a module listed above it, which is the healthy direction.
37→12 bp.entry uses user✕
- Connections
- 1 pair of types, where a type in bp.entry uses a type in user.
- The types involved
org.simple.clinic.bp.entry.BloodPressureEntryEffectHandler→org.simple.clinic.user.User
- Direction
- bp.entry uses user, so a change to user can break bp.entry, while a change to bp.entry can't break user.
- Position
- Below the diagonal: bp.entry uses a module listed above it, which is the healthy direction.
37→16 bp.entry uses overdue✕
- Connections
- 1 pair of types, where a type in bp.entry uses a type in overdue.
- The types involved
org.simple.clinic.bp.entry.BloodPressureEntryEffectHandler→org.simple.clinic.overdue.AppointmentRepository
- Direction
- bp.entry uses overdue, so a change to overdue can break bp.entry, while a change to bp.entry can't break overdue.
- Position
- Below the diagonal: bp.entry uses a module listed above it, which is the healthy direction.
37→20 bp.entry uses patient✕
- Connections
- 1 pair of types, where a type in bp.entry uses a type in patient.
- The types involved
org.simple.clinic.bp.entry.BloodPressureEntryEffectHandler→org.simple.clinic.patient.PatientRepository
- Direction
- bp.entry uses patient, so a change to patient can break bp.entry, while a change to bp.entry can't break patient.
- Position
- Below the diagonal: bp.entry uses a module listed above it, which is the healthy direction.
37→21 bp.entry uses facility✕
- Connections
- 1 pair of types, where a type in bp.entry uses a type in facility.
- The types involved
org.simple.clinic.bp.entry.BloodPressureEntryEffectHandler→org.simple.clinic.facility.Facility
- Direction
- bp.entry uses facility, so a change to facility can break bp.entry, while a change to bp.entry can't break facility.
- Position
- Below the diagonal: bp.entry uses a module listed above it, which is the healthy direction.
37→23 bp.entry uses feature✕
- Connections
- 1 pair of types, where a type in bp.entry uses a type in feature.
- The types involved
org.simple.clinic.bp.entry.BloodPressureEntrySheet→org.simple.clinic.feature.Features
- Direction
- bp.entry uses feature, so a change to feature can break bp.entry, while a change to bp.entry can't break feature.
- Position
- Below the diagonal: bp.entry uses a module listed above it, which is the healthy direction.
37→25 bp.entry uses util✕
- Connections
- 5 pairs of types, where a type in bp.entry uses a type in util.
- The types involved
org.simple.clinic.bp.entry.BloodPressureEntryEffectHandler→org.simple.clinic.util.UserClockorg.simple.clinic.bp.entry.BloodPressureEntrySheet→org.simple.clinic.util.UserClockorg.simple.clinic.bp.entry.BloodPressureEntrySheet→org.simple.clinic.util.UserInputDatePaddingCharacterorg.simple.clinic.bp.entry.BloodPressureEntryUiRenderer→org.simple.clinic.util.ValueChangedCallbackorg.simple.clinic.bp.entry.BloodPressureEntryUpdate→org.simple.clinic.util.UserInputDatePaddingCharacter
- Direction
- bp.entry uses util, so a change to util can break bp.entry, while a change to bp.entry can't break util.
- Position
- Below the diagonal: bp.entry uses a module listed above it, which is the healthy direction.
37→31 bp.entry uses bp✕
- Connections
- 8 pairs of types, where a type in bp.entry uses a type in bp.
- The types involved
org.simple.clinic.bp.entry.BloodPressureEntryEffectHandler→org.simple.clinic.bp.BloodPressureMeasurementorg.simple.clinic.bp.entry.BloodPressureEntryEffectHandler→org.simple.clinic.bp.BloodPressureRepositoryorg.simple.clinic.bp.entry.BloodPressureEntryEffectHandler→org.simple.clinic.bp.ValidationResultorg.simple.clinic.bp.entry.BloodPressureEntryUpdate→org.simple.clinic.bp.BloodPressureReadingorg.simple.clinic.bp.entry.BloodPressureEntryUpdate→org.simple.clinic.bp.ValidationResultorg.simple.clinic.bp.entry.CreateNewBpEntry→org.simple.clinic.bp.BloodPressureReadingorg.simple.clinic.bp.entry.ShowBpValidationError→org.simple.clinic.bp.ValidationResultorg.simple.clinic.bp.entry.UpdateBpEntry→org.simple.clinic.bp.BloodPressureReading
- Direction
- bp.entry uses bp, so a change to bp can break bp.entry, while a change to bp.entry can't break bp.
- Position
- Below the diagonal: bp.entry uses a module listed above it, which is the healthy direction.
37→36 bp.entry uses org.simple.clinic✕
- Connections
- 1 pair of types, where a type in bp.entry uses a type in org.simple.clinic.
- The types involved
org.simple.clinic.bp.entry.BloodPressureEntryEffectHandler→org.simple.clinic.ReportAnalyticsEvents
- Direction
- bp.entry uses org.simple.clinic, so a change to org.simple.clinic can break bp.entry, while a change to bp.entry can't break org.simple.clinic.
- Position
- Below the diagonal: bp.entry uses a module listed above it, which is the healthy direction.
38→1 summary uses mobius✕
- Connections
- 4 pairs of types, where a type in summary uses a type in mobius.
- The types involved
org.simple.clinic.summary.PatientSummaryScreen→org.simple.clinic.mobius.DeferredEventSourceorg.simple.clinic.summary.PatientSummaryScreen→org.simple.clinic.mobius.ViewRendererorg.simple.clinic.summary.PatientSummaryViewEffectHandler→org.simple.clinic.mobius.ViewEffectsHandlerorg.simple.clinic.summary.PatientSummaryViewRenderer→org.simple.clinic.mobius.ViewRenderer
- Direction
- summary uses mobius, so a change to mobius can break summary, while a change to summary can't break mobius.
- Position
- Below the diagonal: summary uses a module listed above it, which is the healthy direction.
38→3 summary uses patient.businessid✕
- Connections
- 5 pairs of types, where a type in summary uses a type in patient.businessid.
- The types involved
org.simple.clinic.summary.PatientSummaryProfile→org.simple.clinic.patient.businessid.BusinessIdorg.simple.clinic.summary.PatientSummaryProfile→org.simple.clinic.patient.businessid.Identifierorg.simple.clinic.summary.PatientSummaryScreen→org.simple.clinic.patient.businessid.Identifierorg.simple.clinic.summary.PatientSummaryUiActions→org.simple.clinic.patient.businessid.Identifierorg.simple.clinic.summary.ShowLinkIdWithPatientView→org.simple.clinic.patient.businessid.Identifier
- Direction
- summary uses patient.businessid, so a change to patient.businessid can break summary, while a change to summary can't break patient.businessid.
- Position
- Below the diagonal: summary uses a module listed above it, which is the healthy direction.
38→5 summary uses util.scheduler✕
- Connections
- 1 pair of types, where a type in summary uses a type in util.scheduler.
- The types involved
org.simple.clinic.summary.PatientSummaryEffectHandler→org.simple.clinic.util.scheduler.SchedulersProvider
- Direction
- summary uses util.scheduler, so a change to util.scheduler can break summary, while a change to summary can't break util.scheduler.
- Position
- Below the diagonal: summary uses a module listed above it, which is the healthy direction.
38→6 summary uses medicalhistory✕
- Connections
- 11 pairs of types, where a type in summary uses a type in medicalhistory.
- The types involved
org.simple.clinic.summary.CVDRiskInfoLoaded→org.simple.clinic.medicalhistory.MedicalHistoryorg.simple.clinic.summary.DataForBackClickLoaded→org.simple.clinic.medicalhistory.MedicalHistoryorg.simple.clinic.summary.DataForDoneClickLoaded→org.simple.clinic.medicalhistory.MedicalHistoryorg.simple.clinic.summary.PatientSummaryEffectHandler→org.simple.clinic.medicalhistory.Answerorg.simple.clinic.summary.PatientSummaryEffectHandler→org.simple.clinic.medicalhistory.MedicalHistoryRepositoryorg.simple.clinic.summary.PatientSummaryUpdate→org.simple.clinic.medicalhistory.MedicalHistoryorg.simple.clinic.summary.PatientTeleconsultationInfo→org.simple.clinic.medicalhistory.MedicalHistoryorg.simple.clinic.summary.StatinInfoLoaded→org.simple.clinic.medicalhistory.MedicalHistoryorg.simple.clinic.summary.StatinPrescriptionCheckInfoLoaded→org.simple.clinic.medicalhistory.MedicalHistoryorg.simple.clinic.summary.TobaccoUseAnswered→org.simple.clinic.medicalhistory.Answerorg.simple.clinic.summary.UpdateTobaccoUse→org.simple.clinic.medicalhistory.Answer
- Direction
- summary uses medicalhistory, so a change to medicalhistory can break summary, while a change to summary can't break medicalhistory.
- Position
- Below the diagonal: summary uses a module listed above it, which is the healthy direction.
38→7 summary uses navigation.v2✕
- Connections
- 4 pairs of types, where a type in summary uses a type in navigation.v2.
- The types involved
org.simple.clinic.summary.PatientSummaryScreen→org.simple.clinic.navigation.v2.HandlesBackorg.simple.clinic.summary.PatientSummaryScreen→org.simple.clinic.navigation.v2.Routerorg.simple.clinic.summary.PatientSummaryScreen→org.simple.clinic.navigation.v2.Succeededorg.simple.clinic.summary.PatientSummaryScreenKey→org.simple.clinic.navigation.v2.ScreenKey
- Direction
- summary uses navigation.v2, so a change to navigation.v2 can break summary, while a change to summary can't break navigation.v2.
- Position
- Below the diagonal: summary uses a module listed above it, which is the healthy direction.
38→8 summary uses navigation.v2.fragments✕
- Connections
- 1 pair of types, where a type in summary uses a type in navigation.v2.fragments.
- The types involved
org.simple.clinic.summary.PatientSummaryScreen→org.simple.clinic.navigation.v2.fragments.BaseScreen
- Direction
- summary uses navigation.v2.fragments, so a change to navigation.v2.fragments can break summary, while a change to summary can't break navigation.v2.fragments.
- Position
- Below the diagonal: summary uses a module listed above it, which is the healthy direction.
38→9 summary uses widgets✕
- Connections
- 2 pairs of types, where a type in summary uses a type in widgets.
- The types involved
org.simple.clinic.summary.PatientSummaryEvent→org.simple.clinic.widgets.UiEventorg.simple.clinic.summary.PatientSummaryScreen→org.simple.clinic.widgets.UiEvent
- Direction
- summary uses widgets, so a change to widgets can break summary, while a change to summary can't break widgets.
- Position
- Below the diagonal: summary uses a module listed above it, which is the healthy direction.
38→11 summary uses drugs✕
- Connections
- 12 pairs of types, where a type in summary uses a type in drugs.
- The types involved
org.simple.clinic.summary.CVDRiskInfoLoaded→org.simple.clinic.drugs.PrescribedDrugorg.simple.clinic.summary.DataForBackClickLoaded→org.simple.clinic.drugs.DiagnosisWarningPrescriptionsorg.simple.clinic.summary.DataForBackClickLoaded→org.simple.clinic.drugs.PrescribedDrugorg.simple.clinic.summary.DataForDoneClickLoaded→org.simple.clinic.drugs.DiagnosisWarningPrescriptionsorg.simple.clinic.summary.DataForDoneClickLoaded→org.simple.clinic.drugs.PrescribedDrugorg.simple.clinic.summary.PatientSummaryEffectHandler→org.simple.clinic.drugs.DiagnosisWarningPrescriptionsorg.simple.clinic.summary.PatientSummaryEffectHandler→org.simple.clinic.drugs.PrescriptionRepositoryorg.simple.clinic.summary.PatientSummaryModule→org.simple.clinic.drugs.DiagnosisWarningPrescriptionsorg.simple.clinic.summary.PatientSummaryUpdate→org.simple.clinic.drugs.DiagnosisWarningPrescriptionsorg.simple.clinic.summary.PatientSummaryUpdate→org.simple.clinic.drugs.PrescribedDrugorg.simple.clinic.summary.PatientTeleconsultationInfo→org.simple.clinic.drugs.PrescribedDrugorg.simple.clinic.summary.StatinPrescriptionCheckInfoLoaded→org.simple.clinic.drugs.PrescribedDrug
- Direction
- summary uses drugs, so a change to drugs can break summary, while a change to summary can't break drugs.
- Position
- Below the diagonal: summary uses a module listed above it, which is the healthy direction.
38→12 summary uses user✕
- Connections
- 2 pairs of types, where a type in summary uses a type in user.
- The types involved
org.simple.clinic.summary.CurrentUserAndFacilityLoaded→org.simple.clinic.user.Userorg.simple.clinic.summary.PatientSummaryEffectHandler→org.simple.clinic.user.User
- Direction
- summary uses user, so a change to user can break summary, while a change to summary can't break user.
- Position
- Below the diagonal: summary uses a module listed above it, which is the healthy direction.
38→14 summary uses sync✕
- Connections
- 1 pair of types, where a type in summary uses a type in sync.
- The types involved
org.simple.clinic.summary.PatientSummaryEffectHandler→org.simple.clinic.sync.DataSync
- Direction
- summary uses sync, so a change to sync can break summary, while a change to summary can't break sync.
- Position
- Below the diagonal: summary uses a module listed above it, which is the healthy direction.
38→16 summary uses overdue✕
- Connections
- 3 pairs of types, where a type in summary uses a type in overdue.
- The types involved
org.simple.clinic.summary.LatestScheduledAppointmentLoaded→org.simple.clinic.overdue.Appointmentorg.simple.clinic.summary.PatientSummaryEffectHandler→org.simple.clinic.overdue.AppointmentRepositoryorg.simple.clinic.summary.PatientSummaryModel→org.simple.clinic.overdue.Appointment
- Direction
- summary uses overdue, so a change to overdue can break summary, while a change to summary can't break overdue.
- Position
- Below the diagonal: summary uses a module listed above it, which is the healthy direction.
38→18 summary uses bloodsugar✕
- Connections
- 2 pairs of types, where a type in summary uses a type in bloodsugar.
- The types involved
org.simple.clinic.summary.PatientSummaryEffectHandler→org.simple.clinic.bloodsugar.BloodSugarRepositoryorg.simple.clinic.summary.PatientTeleconsultationInfo→org.simple.clinic.bloodsugar.BloodSugarMeasurement
- Direction
- summary uses bloodsugar, so a change to bloodsugar can break summary, while a change to summary can't break bloodsugar.
- Position
- Below the diagonal: summary uses a module listed above it, which is the healthy direction.
38→20 summary uses patient✕
- Connections
- 11 pairs of types, where a type in summary uses a type in patient.
- The types involved
org.simple.clinic.summary.CalculateLabBasedCVDRisk→org.simple.clinic.patient.Patientorg.simple.clinic.summary.CalculateNonLabBasedCVDRisk→org.simple.clinic.patient.Patientorg.simple.clinic.summary.LoadStatinInfo→org.simple.clinic.patient.Patientorg.simple.clinic.summary.LoadStatinPrescriptionCheckInfo→org.simple.clinic.patient.Patientorg.simple.clinic.summary.PatientSummaryEffectHandler→org.simple.clinic.patient.Answerorg.simple.clinic.summary.PatientSummaryEffectHandler→org.simple.clinic.patient.PatientProfileorg.simple.clinic.summary.PatientSummaryEffectHandler→org.simple.clinic.patient.PatientRepositoryorg.simple.clinic.summary.PatientSummaryProfile→org.simple.clinic.patient.Patientorg.simple.clinic.summary.PatientSummaryProfile→org.simple.clinic.patient.PatientAddressorg.simple.clinic.summary.PatientSummaryProfile→org.simple.clinic.patient.PatientPhoneNumberorg.simple.clinic.summary.UpdatePatientReassignmentStatus→org.simple.clinic.patient.Answer
- Direction
- summary uses patient, so a change to patient can break summary, while a change to summary can't break patient.
- Position
- Below the diagonal: summary uses a module listed above it, which is the healthy direction.
38→21 summary uses facility✕
- Connections
- 13 pairs of types, where a type in summary uses a type in facility.
- The types involved
org.simple.clinic.summary.CurrentUserAndFacilityLoaded→org.simple.clinic.facility.Facilityorg.simple.clinic.summary.DispatchNewAssignedFacility→org.simple.clinic.facility.Facilityorg.simple.clinic.summary.HandleEditClick→org.simple.clinic.facility.Facilityorg.simple.clinic.summary.NewAssignedFacilitySelected→org.simple.clinic.facility.Facilityorg.simple.clinic.summary.PatientSummaryEffectHandler→org.simple.clinic.facility.Facilityorg.simple.clinic.summary.PatientSummaryEffectHandler→org.simple.clinic.facility.FacilityRepositoryorg.simple.clinic.summary.PatientSummaryModel→org.simple.clinic.facility.Facilityorg.simple.clinic.summary.PatientSummaryProfile→org.simple.clinic.facility.Facilityorg.simple.clinic.summary.PatientSummaryScreen→org.simple.clinic.facility.Facilityorg.simple.clinic.summary.PatientSummaryUiActions→org.simple.clinic.facility.Facilityorg.simple.clinic.summary.PatientTeleconsultationInfo→org.simple.clinic.facility.Facilityorg.simple.clinic.summary.ShowReassignPatientWarningSheet→org.simple.clinic.facility.Facilityorg.simple.clinic.summary.ShowScheduleAppointmentSheet→org.simple.clinic.facility.Facility
- Direction
- summary uses facility, so a change to facility can break summary, while a change to summary can't break facility.
- Position
- Below the diagonal: summary uses a module listed above it, which is the healthy direction.
38→22 summary uses remoteconfig✕
- Connections
- 3 pairs of types, where a type in summary uses a type in remoteconfig.
- The types involved
org.simple.clinic.summary.PatientSummaryConfig→org.simple.clinic.remoteconfig.ConfigReaderorg.simple.clinic.summary.PatientSummaryModule→org.simple.clinic.remoteconfig.ConfigReaderorg.simple.clinic.summary.PatientSummaryScreen→org.simple.clinic.remoteconfig.ConfigReader
- Direction
- summary uses remoteconfig, so a change to remoteconfig can break summary, while a change to summary can't break remoteconfig.
- Position
- Below the diagonal: summary uses a module listed above it, which is the healthy direction.
38→23 summary uses feature✕
- Connections
- 2 pairs of types, where a type in summary uses a type in feature.
- The types involved
org.simple.clinic.summary.PatientSummaryEffectHandler→org.simple.clinic.feature.Featuresorg.simple.clinic.summary.PatientSummaryScreen→org.simple.clinic.feature.Features
- Direction
- summary uses feature, so a change to feature can break summary, while a change to summary can't break feature.
- Position
- Below the diagonal: summary uses a module listed above it, which is the healthy direction.
38→25 summary uses util✕
- Connections
- 6 pairs of types, where a type in summary uses a type in util.
- The types involved
org.simple.clinic.summary.PatientSummaryEffectHandler→org.simple.clinic.util.UserClockorg.simple.clinic.summary.PatientSummaryEffectHandler→org.simple.clinic.util.UtcClockorg.simple.clinic.summary.PatientSummaryModel→org.simple.clinic.util.ParcelableOptionalorg.simple.clinic.summary.PatientSummaryScreen→org.simple.clinic.util.UserClockorg.simple.clinic.summary.PatientSummaryViewRenderer→org.simple.clinic.util.UserClockorg.simple.clinic.summary.PatientSummaryViewRenderer→org.simple.clinic.util.ValueChangedCallback
- Direction
- summary uses util, so a change to util can break summary, while a change to summary can't break util.
- Position
- Below the diagonal: summary uses a module listed above it, which is the healthy direction.
38→29 summary uses appconfig✕
- Connections
- 2 pairs of types, where a type in summary uses a type in appconfig.
- The types involved
org.simple.clinic.summary.PatientSummaryEffectHandler→org.simple.clinic.appconfig.Countryorg.simple.clinic.summary.PatientSummaryScreen→org.simple.clinic.appconfig.Country
- Direction
- summary uses appconfig, so a change to appconfig can break summary, while a change to summary can't break appconfig.
- Position
- Below the diagonal: summary uses a module listed above it, which is the healthy direction.
38→31 summary uses bp✕
- Connections
- 2 pairs of types, where a type in summary uses a type in bp.
- The types involved
org.simple.clinic.summary.PatientSummaryEffectHandler→org.simple.clinic.bp.BloodPressureRepositoryorg.simple.clinic.summary.PatientTeleconsultationInfo→org.simple.clinic.bp.BloodPressureMeasurement
- Direction
- summary uses bp, so a change to bp can break summary, while a change to summary can't break bp.
- Position
- Below the diagonal: summary uses a module listed above it, which is the healthy direction.
38→36 summary uses org.simple.clinic✕
- Connections
- 1 pair of types, where a type in summary uses a type in org.simple.clinic.
- The types involved
org.simple.clinic.summary.PatientSummaryModule→org.simple.clinic.AppDatabase
- Direction
- summary uses org.simple.clinic, so a change to org.simple.clinic can break summary, while a change to summary can't break org.simple.clinic.
- Position
- Below the diagonal: summary uses a module listed above it, which is the healthy direction.
39→1 scheduleappointment uses mobius✕
- Connections
- 3 pairs of types, where a type in scheduleappointment uses a type in mobius.
- The types involved
org.simple.clinic.scheduleappointment.ScheduleAppointmentSheet→org.simple.clinic.mobius.DeferredEventSourceorg.simple.clinic.scheduleappointment.ScheduleAppointmentUiRenderer→org.simple.clinic.mobius.ViewRendererorg.simple.clinic.scheduleappointment.ScheduleAppointmentViewEffectHandler→org.simple.clinic.mobius.ViewEffectsHandler
- Direction
- scheduleappointment uses mobius, so a change to mobius can break scheduleappointment, while a change to scheduleappointment can't break mobius.
- Position
- Below the diagonal: scheduleappointment uses a module listed above it, which is the healthy direction.
39→5 scheduleappointment uses util.scheduler✕
- Connections
- 1 pair of types, where a type in scheduleappointment uses a type in util.scheduler.
- The types involved
org.simple.clinic.scheduleappointment.ScheduleAppointmentEffectHandler→org.simple.clinic.util.scheduler.SchedulersProvider
- Direction
- scheduleappointment uses util.scheduler, so a change to util.scheduler can break scheduleappointment, while a change to scheduleappointment can't break util.scheduler.
- Position
- Below the diagonal: scheduleappointment uses a module listed above it, which is the healthy direction.
39→7 scheduleappointment uses navigation.v2✕
- Connections
- 2 pairs of types, where a type in scheduleappointment uses a type in navigation.v2.
- The types involved
org.simple.clinic.scheduleappointment.ScheduleAppointmentSheet→org.simple.clinic.navigation.v2.Routerorg.simple.clinic.scheduleappointment.ScheduleAppointmentSheet→org.simple.clinic.navigation.v2.Succeeded
- Direction
- scheduleappointment uses navigation.v2, so a change to navigation.v2 can break scheduleappointment, while a change to scheduleappointment can't break navigation.v2.
- Position
- Below the diagonal: scheduleappointment uses a module listed above it, which is the healthy direction.
39→8 scheduleappointment uses navigation.v2.fragments✕
- Connections
- 1 pair of types, where a type in scheduleappointment uses a type in navigation.v2.fragments.
- The types involved
org.simple.clinic.scheduleappointment.ScheduleAppointmentSheet→org.simple.clinic.navigation.v2.fragments.BaseBottomSheet
- Direction
- scheduleappointment uses navigation.v2.fragments, so a change to navigation.v2.fragments can break scheduleappointment, while a change to scheduleappointment can't break navigation.v2.fragments.
- Position
- Below the diagonal: scheduleappointment uses a module listed above it, which is the healthy direction.
39→9 scheduleappointment uses widgets✕
- Connections
- 1 pair of types, where a type in scheduleappointment uses a type in widgets.
- The types involved
org.simple.clinic.scheduleappointment.ScheduleAppointmentEvent→org.simple.clinic.widgets.UiEvent
- Direction
- scheduleappointment uses widgets, so a change to widgets can break scheduleappointment, while a change to scheduleappointment can't break widgets.
- Position
- Below the diagonal: scheduleappointment uses a module listed above it, which is the healthy direction.
39→16 scheduleappointment uses overdue✕
- Connections
- 11 pairs of types, where a type in scheduleappointment uses a type in overdue.
- The types involved
org.simple.clinic.scheduleappointment.DefaultAppointmentDateLoaded→org.simple.clinic.overdue.PotentialAppointmentDateorg.simple.clinic.scheduleappointment.PotentialAppointmentDateModel→org.simple.clinic.overdue.PotentialAppointmentDateorg.simple.clinic.scheduleappointment.ScheduleAppointmentEffectHandler→org.simple.clinic.overdue.AppointmentConfigorg.simple.clinic.scheduleappointment.ScheduleAppointmentEffectHandler→org.simple.clinic.overdue.AppointmentRepositoryorg.simple.clinic.scheduleappointment.ScheduleAppointmentEffectHandler→org.simple.clinic.overdue.PotentialAppointmentDateorg.simple.clinic.scheduleappointment.ScheduleAppointmentEffectHandler→org.simple.clinic.overdue.TimeToAppointmentorg.simple.clinic.scheduleappointment.ScheduleAppointmentModel→org.simple.clinic.overdue.PotentialAppointmentDateorg.simple.clinic.scheduleappointment.ScheduleAppointmentSheet→org.simple.clinic.overdue.AppointmentConfigorg.simple.clinic.scheduleappointment.ScheduleAppointmentSheet→org.simple.clinic.overdue.TimeToAppointmentorg.simple.clinic.scheduleappointment.ScheduleAppointmentUi→org.simple.clinic.overdue.TimeToAppointmentorg.simple.clinic.scheduleappointment.ScheduleAppointmentUiRenderer→org.simple.clinic.overdue.PotentialAppointmentDate
- Direction
- scheduleappointment uses overdue, so a change to overdue can break scheduleappointment, while a change to scheduleappointment can't break overdue.
- Position
- Below the diagonal: scheduleappointment uses a module listed above it, which is the healthy direction.
39→20 scheduleappointment uses patient✕
- Connections
- 2 pairs of types, where a type in scheduleappointment uses a type in patient.
- The types involved
org.simple.clinic.scheduleappointment.ScheduleAppointmentEffectHandler→org.simple.clinic.patient.Patientorg.simple.clinic.scheduleappointment.ScheduleAppointmentEffectHandler→org.simple.clinic.patient.PatientRepository
- Direction
- scheduleappointment uses patient, so a change to patient can break scheduleappointment, while a change to scheduleappointment can't break patient.
- Position
- Below the diagonal: scheduleappointment uses a module listed above it, which is the healthy direction.
39→21 scheduleappointment uses facility✕
- Connections
- 9 pairs of types, where a type in scheduleappointment uses a type in facility.
- The types involved
org.simple.clinic.scheduleappointment.AppointmentFacilitiesLoaded→org.simple.clinic.facility.Facilityorg.simple.clinic.scheduleappointment.PatientFacilityChanged→org.simple.clinic.facility.Facilityorg.simple.clinic.scheduleappointment.ScheduleAppointmentEffectHandler→org.simple.clinic.facility.Facilityorg.simple.clinic.scheduleappointment.ScheduleAppointmentEffectHandler→org.simple.clinic.facility.FacilityRepositoryorg.simple.clinic.scheduleappointment.ScheduleAppointmentForPatient→org.simple.clinic.facility.Facilityorg.simple.clinic.scheduleappointment.ScheduleAppointmentForPatientFromNext→org.simple.clinic.facility.Facilityorg.simple.clinic.scheduleappointment.ScheduleAppointmentModel→org.simple.clinic.facility.Facilityorg.simple.clinic.scheduleappointment.ScheduleAppointmentSheet→org.simple.clinic.facility.Facilityorg.simple.clinic.scheduleappointment.ScheduleAppointmentUiRenderer→org.simple.clinic.facility.Facility
- Direction
- scheduleappointment uses facility, so a change to facility can break scheduleappointment, while a change to scheduleappointment can't break facility.
- Position
- Below the diagonal: scheduleappointment uses a module listed above it, which is the healthy direction.
39→23 scheduleappointment uses feature✕
- Connections
- 1 pair of types, where a type in scheduleappointment uses a type in feature.
- The types involved
org.simple.clinic.scheduleappointment.ScheduleAppointmentSheet→org.simple.clinic.feature.Features
- Direction
- scheduleappointment uses feature, so a change to feature can break scheduleappointment, while a change to scheduleappointment can't break feature.
- Position
- Below the diagonal: scheduleappointment uses a module listed above it, which is the healthy direction.
39→25 scheduleappointment uses util✕
- Connections
- 3 pairs of types, where a type in scheduleappointment uses a type in util.
- The types involved
org.simple.clinic.scheduleappointment.ScheduleAppointmentEffectHandler→org.simple.clinic.util.UserClockorg.simple.clinic.scheduleappointment.ScheduleAppointmentSheet→org.simple.clinic.util.UserClockorg.simple.clinic.scheduleappointment.ScheduleAppointmentUiRenderer→org.simple.clinic.util.ValueChangedCallback
- Direction
- scheduleappointment uses util, so a change to util can break scheduleappointment, while a change to scheduleappointment can't break util.
- Position
- Below the diagonal: scheduleappointment uses a module listed above it, which is the healthy direction.
39→35 scheduleappointment uses newentry✕
- Connections
- 1 pair of types, where a type in scheduleappointment uses a type in newentry.
- The types involved
org.simple.clinic.scheduleappointment.ScheduleAppointmentModel→org.simple.clinic.newentry.ButtonState
- Direction
- scheduleappointment uses newentry, so a change to newentry can break scheduleappointment, while a change to scheduleappointment can't break newentry.
- Position
- Below the diagonal: scheduleappointment uses a module listed above it, which is the healthy direction.
39→38 scheduleappointment uses summary✕
- Connections
- 1 pair of types, where a type in scheduleappointment uses a type in summary.
- The types involved
org.simple.clinic.scheduleappointment.ScheduleAppointmentModel→org.simple.clinic.summary.AppointmentSheetOpenedFrom
- Direction
- scheduleappointment uses summary, so a change to summary can break scheduleappointment, while a change to scheduleappointment can't break summary.
- Position
- Below the diagonal: scheduleappointment uses a module listed above it, which is the healthy direction.
40→1 summary.teleconsultation.contactdoctor uses mobius✕
- Connections
- 1 pair of types, where a type in summary.teleconsultation.contactdoctor uses a type in mobius.
- The types involved
org.simple.clinic.summary.teleconsultation.contactdoctor.ContactDoctorUiRenderer→org.simple.clinic.mobius.ViewRenderer
- Direction
- summary.teleconsultation.contactdoctor uses mobius, so a change to mobius can break summary.teleconsultation.contactdoctor, while a change to summary.teleconsultation.contactdoctor can't break mobius.
- Position
- Below the diagonal: summary.teleconsultation.contactdoctor uses a module listed above it, which is the healthy direction.
40→5 summary.teleconsultation.contactdoctor uses util.scheduler✕
- Connections
- 1 pair of types, where a type in summary.teleconsultation.contactdoctor uses a type in util.scheduler.
- The types involved
org.simple.clinic.summary.teleconsultation.contactdoctor.ContactDoctorEffectHandler→org.simple.clinic.util.scheduler.SchedulersProvider
- Direction
- summary.teleconsultation.contactdoctor uses util.scheduler, so a change to util.scheduler can break summary.teleconsultation.contactdoctor, while a change to summary.teleconsultation.contactdoctor can't break util.scheduler.
- Position
- Below the diagonal: summary.teleconsultation.contactdoctor uses a module listed above it, which is the healthy direction.
40→6 summary.teleconsultation.contactdoctor uses medicalhistory✕
- Connections
- 1 pair of types, where a type in summary.teleconsultation.contactdoctor uses a type in medicalhistory.
- The types involved
org.simple.clinic.summary.teleconsultation.contactdoctor.ContactDoctorEffectHandler→org.simple.clinic.medicalhistory.MedicalHistoryRepository
- Direction
- summary.teleconsultation.contactdoctor uses medicalhistory, so a change to medicalhistory can break summary.teleconsultation.contactdoctor, while a change to summary.teleconsultation.contactdoctor can't break medicalhistory.
- Position
- Below the diagonal: summary.teleconsultation.contactdoctor uses a module listed above it, which is the healthy direction.
40→9 summary.teleconsultation.contactdoctor uses widgets✕
- Connections
- 3 pairs of types, where a type in summary.teleconsultation.contactdoctor uses a type in widgets.
- The types involved
org.simple.clinic.summary.teleconsultation.contactdoctor.ContactDoctorEvent→org.simple.clinic.widgets.UiEventorg.simple.clinic.summary.teleconsultation.contactdoctor.ContactDoctorSheet→org.simple.clinic.widgets.BottomSheetActivityorg.simple.clinic.summary.teleconsultation.contactdoctor.ContactDoctorSheet→org.simple.clinic.widgets.UiEvent
- Direction
- summary.teleconsultation.contactdoctor uses widgets, so a change to widgets can break summary.teleconsultation.contactdoctor, while a change to summary.teleconsultation.contactdoctor can't break widgets.
- Position
- Below the diagonal: summary.teleconsultation.contactdoctor uses a module listed above it, which is the healthy direction.
40→11 summary.teleconsultation.contactdoctor uses drugs✕
- Connections
- 1 pair of types, where a type in summary.teleconsultation.contactdoctor uses a type in drugs.
- The types involved
org.simple.clinic.summary.teleconsultation.contactdoctor.ContactDoctorEffectHandler→org.simple.clinic.drugs.PrescriptionRepository
- Direction
- summary.teleconsultation.contactdoctor uses drugs, so a change to drugs can break summary.teleconsultation.contactdoctor, while a change to summary.teleconsultation.contactdoctor can't break drugs.
- Position
- Below the diagonal: summary.teleconsultation.contactdoctor uses a module listed above it, which is the healthy direction.
40→12 summary.teleconsultation.contactdoctor uses user✕
- Connections
- 1 pair of types, where a type in summary.teleconsultation.contactdoctor uses a type in user.
- The types involved
org.simple.clinic.summary.teleconsultation.contactdoctor.ContactDoctorEffectHandler→org.simple.clinic.user.User
- Direction
- summary.teleconsultation.contactdoctor uses user, so a change to user can break summary.teleconsultation.contactdoctor, while a change to summary.teleconsultation.contactdoctor can't break user.
- Position
- Below the diagonal: summary.teleconsultation.contactdoctor uses a module listed above it, which is the healthy direction.
40→18 summary.teleconsultation.contactdoctor uses bloodsugar✕
- Connections
- 1 pair of types, where a type in summary.teleconsultation.contactdoctor uses a type in bloodsugar.
- The types involved
org.simple.clinic.summary.teleconsultation.contactdoctor.ContactDoctorEffectHandler→org.simple.clinic.bloodsugar.BloodSugarRepository
- Direction
- summary.teleconsultation.contactdoctor uses bloodsugar, so a change to bloodsugar can break summary.teleconsultation.contactdoctor, while a change to summary.teleconsultation.contactdoctor can't break bloodsugar.
- Position
- Below the diagonal: summary.teleconsultation.contactdoctor uses a module listed above it, which is the healthy direction.
40→20 summary.teleconsultation.contactdoctor uses patient✕
- Connections
- 1 pair of types, where a type in summary.teleconsultation.contactdoctor uses a type in patient.
- The types involved
org.simple.clinic.summary.teleconsultation.contactdoctor.ContactDoctorEffectHandler→org.simple.clinic.patient.PatientRepository
- Direction
- summary.teleconsultation.contactdoctor uses patient, so a change to patient can break summary.teleconsultation.contactdoctor, while a change to summary.teleconsultation.contactdoctor can't break patient.
- Position
- Below the diagonal: summary.teleconsultation.contactdoctor uses a module listed above it, which is the healthy direction.
40→21 summary.teleconsultation.contactdoctor uses facility✕
- Connections
- 1 pair of types, where a type in summary.teleconsultation.contactdoctor uses a type in facility.
- The types involved
org.simple.clinic.summary.teleconsultation.contactdoctor.ContactDoctorEffectHandler→org.simple.clinic.facility.Facility
- Direction
- summary.teleconsultation.contactdoctor uses facility, so a change to facility can break summary.teleconsultation.contactdoctor, while a change to summary.teleconsultation.contactdoctor can't break facility.
- Position
- Below the diagonal: summary.teleconsultation.contactdoctor uses a module listed above it, which is the healthy direction.
40→23 summary.teleconsultation.contactdoctor uses feature✕
- Connections
- 1 pair of types, where a type in summary.teleconsultation.contactdoctor uses a type in feature.
- The types involved
org.simple.clinic.summary.teleconsultation.contactdoctor.ContactDoctorSheet→org.simple.clinic.feature.Features
- Direction
- summary.teleconsultation.contactdoctor uses feature, so a change to feature can break summary.teleconsultation.contactdoctor, while a change to summary.teleconsultation.contactdoctor can't break feature.
- Position
- Below the diagonal: summary.teleconsultation.contactdoctor uses a module listed above it, which is the healthy direction.
40→25 summary.teleconsultation.contactdoctor uses util✕
- Connections
- 1 pair of types, where a type in summary.teleconsultation.contactdoctor uses a type in util.
- The types involved
org.simple.clinic.summary.teleconsultation.contactdoctor.ContactDoctorEffectHandler→org.simple.clinic.util.UtcClock
- Direction
- summary.teleconsultation.contactdoctor uses util, so a change to util can break summary.teleconsultation.contactdoctor, while a change to summary.teleconsultation.contactdoctor can't break util.
- Position
- Below the diagonal: summary.teleconsultation.contactdoctor uses a module listed above it, which is the healthy direction.
40→31 summary.teleconsultation.contactdoctor uses bp✕
- Connections
- 1 pair of types, where a type in summary.teleconsultation.contactdoctor uses a type in bp.
- The types involved
org.simple.clinic.summary.teleconsultation.contactdoctor.ContactDoctorEffectHandler→org.simple.clinic.bp.BloodPressureRepository
- Direction
- summary.teleconsultation.contactdoctor uses bp, so a change to bp can break summary.teleconsultation.contactdoctor, while a change to summary.teleconsultation.contactdoctor can't break bp.
- Position
- Below the diagonal: summary.teleconsultation.contactdoctor uses a module listed above it, which is the healthy direction.
40→38 summary.teleconsultation.contactdoctor uses summary✕
- Connections
- 6 pairs of types, where a type in summary.teleconsultation.contactdoctor uses a type in summary.
- The types involved
org.simple.clinic.summary.teleconsultation.contactdoctor.ContactDoctorEffectHandler→org.simple.clinic.summary.PatientSummaryConfigorg.simple.clinic.summary.teleconsultation.contactdoctor.ContactDoctorEffectHandler→org.simple.clinic.summary.PatientTeleconsultationInfoorg.simple.clinic.summary.teleconsultation.contactdoctor.ContactDoctorSheet→org.simple.clinic.summary.PatientTeleconsultationInfoorg.simple.clinic.summary.teleconsultation.contactdoctor.ContactDoctorUiActions→org.simple.clinic.summary.PatientTeleconsultationInfoorg.simple.clinic.summary.teleconsultation.contactdoctor.PatientTeleconsultInfoLoaded→org.simple.clinic.summary.PatientTeleconsultationInfoorg.simple.clinic.summary.teleconsultation.contactdoctor.SendTeleconsultMessage→org.simple.clinic.summary.PatientTeleconsultationInfo
- Direction
- summary.teleconsultation.contactdoctor uses summary, so a change to summary can break summary.teleconsultation.contactdoctor, while a change to summary.teleconsultation.contactdoctor can't break summary.
- Position
- Below the diagonal: summary.teleconsultation.contactdoctor uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Domain Modelling
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 46 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 10 | Medium |
Roadmap
Top priorities: Resolve the 6 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED (2), REDACTED (2); Resolve the 6 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED; Move business rules onto the aggregates/entities they govern so invariants are enforced at the source, not in anemic services.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 6 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED (2), REDACTED (2). | +4.0 pts | Low | Static Analysis (SAST) |
| Resolve the 6 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. | +3.9 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. | +2.3 pts | Low | Static Analysis (SAST) |
| Move business rules onto the aggregates/entities they govern so invariants are enforced at the source, not in anemic services. | +2.6 pts | Medium | Rich vs anemic model |
| Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing. | +1.8 pts | Medium | Security & performance tooling |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. | +0.9 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. | +0.9 pts | Low | Supply-chain Provenance & Signing |
| Give each aggregate one way in that can refuse — a guarded constructor, value-object parameters that validate themselves, or a private constructor behind a factory that returns a failure. | +1.6 pts | Medium | Constructible invalid state |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| app/src/main/java/org/simple/clinic/summary/PatientSummaryUpdate.kt | 5.5 | Mixed | Cyclomatic Complexity: PatientSummaryUpdate.dataForHandlingBackLoaded (cyclomatic 24) |
| app/src/main/java/org/simple/clinic/newentry/PatientEntryScreen.kt | 6.0 | Mixed | Explicit Debt: FixmeComment |
| app/src/main/java/org/simple/clinic/summary/PatientSummaryEffectHandler.kt | 6.0 | Mixed | Explicit Debt: TodoComment |
| app/src/main/java/org/simple/clinic/medicalhistory/MedicalHistoryRepository.kt | 6.0 | Mixed | Explicit Debt: TodoComment |
| app/src/main/java/org/simple/clinic/summary/bloodpressures/ui/BloodPressureSummaryView.kt | 6.3 | Mixed | Code Duplication: Edited copy of a member (32 corresponding lines) |
| app/src/main/java/org/simple/clinic/scheduleappointment/ScheduleAppointmentEffectHandler.kt | 6.3 | Mixed | Code Duplication: Edited copy of a member (19 corresponding lines) |
| app/src/main/java/org/simple/clinic/deeplink/DeepLinkActivity.kt | 6.3 | Mixed | Code Duplication: Edited copy of a member (6 corresponding lines) |
| app/src/main/java/org/simple/clinic/editpatient/EditPatientScreen.kt | 6.5 | Mixed | God Classes: TooManyMethods: EditPatientScreen |
| app/src/main/java/org/simple/clinic/consent/onboarding/OnboardingConsentScreen.kt | 6.7 | Mixed | Explicit Debt: TodoComment |
| app/src/main/java/org/simple/clinic/sync/indicator/SyncIndicatorView.kt | 6.7 | Mixed | Explicit Debt: TodoComment |
| app/src/main/java/org/simple/clinic/medicalhistory/sync/MedicalHistoryPayload.kt | 6.7 | Mixed | Explicit Debt: TodoComment |
| app/src/test/java/org/simple/clinic/newentry/PatientEntryScreenLogicTest.kt | 6.9 | Mixed | Explicit Debt: TodoComment |
| app/src/main/java/org/simple/clinic/bp/entry/BloodPressureEntrySheet.kt | 7.0 | Mixed | God Classes: TooManyMethods: BloodPressureEntrySheet |
| app/src/main/java/org/simple/clinic/AppDatabase.kt | 7.0 | Mixed | God Classes: TooManyMethods: AppDatabase |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 53 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 53 dimensions across the health lenses
- Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 762 of 773 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.kt) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.kt) and this repository declares a JVM test suite (repository root, Gradle), but it was not re-run: the analyzer environment could not run it. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — a Gradle build resolved 524 artifact(s) across its subprojects (148 behind a shipped release, reported), but the currency signal was not established over the whole graph, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: it declares a published package (simple-visuals/build.gradle.kts), but no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `app/src/main/java/org/simple/clinic/cvdrisk/CVDRiskCalculationSheet.kt`, `app/src/main/java/org/simple/clinic/drugs/selection/custom/drugfrequency/country/DrugFrequencyLabel.kt`, `app/src/main/java/org/simple/clinic/monthlyreports/form/compose/QuestionnaireInputField.kt`, `app/src/main/java/org/simple/clinic/patient/onlinelookup/api/SecondsDuration.kt`, `app/src/main/java/org/simple/clinic/scanid/IndiaNHIDDateOfBirth.kt`, … (+4 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Boot via AndroidApp (app). the Android app did not build — `./gradlew :app:assembleDebug` exited 1: com.github.requery:sqlite-android:3.49.0. > Could not get resource 'https://jitpack.io/com/github/requery/sqlite-android/3.49.0/sqlite-android-3.49.0.pom'. > Could not GET 'https…; runtime evidence skipped (launch chosen because app/build.gradle.kts applies the Android application plugin and gradlew builds it).
- C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- DM8 Value-object opportunities — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check finds primitive parameters that travel together through several signatures of the domain (a missing value object). Its deterministic rule has not yet shown 95 % precision on adjudicated rows, so the clumps it finds are counted here and not published as findings, and the card carries no score. That is a limit of the analyzer, not a finding about your code.
- DM9 Scattered domain decisions — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Arm two tells a construction that PRODUCES a measurement from one that merely passes it along, and this repository's frontend does not compute that fact. A measurement built independently in two places would not appear above.
- DM9 Scattered domain decisions — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Some of this repository's production types come from a frontend that does not bind comparison operands to the members they read, which arm one needs, and those types were not walked for this dimension. The counts above speak for the languages that declare it.
- ED5 Idempotency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check decides whether a handler's mutation is safe to re-run by recognising its persistence writes (a database save, a repository write, an event publish) and its guards. Those markers are .NET member names, so in this repository's language a write such as `repository.save(order)` is not recognised and a same-named call on an unrelated library type could be. The handlers were found; their idempotency was neither confirmed nor ruled out.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust and Java source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Java was found, and this repository's Kotlin is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby, Scala and Rust source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby, Scala or Rust was found, and this repository's Kotlin is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
- X2 Cancellation propagation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python and Rust source only, and no C# was loaded, and no named async function in this repository's JavaScript/TypeScript, nor any Go, PHP or Dart function or Kotlin suspend function, makes a request that can be cancelled (fetch, axios, ky, ofetch, got, undici, node:http; net/http, net.Dial; amphp; Dio; Ktor, OkHttp), so there is nothing to judge, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D7 Architectural Integrity: Layering is checked against detected/declared rules — an architecture whose boundaries live in convention or in code review, not in a rule a scanner can read, is not enforced here.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D21 Naming Consistency: Naming consistency compares each name with the convention its structural peers follow in this repository: it cannot tell whether a consistently used name is a good one, and languages other than C# and TypeScript are not measured.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- C4 Data Retention: This control is scored from in-repo evidence only — its real-world effectiveness, exercised only at runtime, is outside a static scan.
- DM4 Rich vs anemic model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
2 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was PatientSummaryUpdate.dataForHandlingBackLoaded at 24. A further 8 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being PatientSummaryUpdate.update at 44 — they are counted neither in the figure above nor in this dimension's score. 7 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: app/src/main/java/org/simple/clinic/summary/PatientSummaryViewEffectHandler.kt (PatientSummaryViewEffectHandler.handle at 27), app/src/main/java/org/simple/clinic/editpatient/EditPatientUpdate.kt (EditPatientUpdate.update at 22), app/src/main/java/org/simple/clinic/newentry/PatientEntryUpdate.kt (PatientEntryUpdate.update at 19), app/src/main/java/org/simple/clinic/newentry/PatientEntryViewEffectHandler.kt (PatientEntryViewEffectHandler.showValidationErrors at 19), app/src/main/java/org/simple/clinic/contactpatient/ContactPatientUpdate.kt (ContactPatientUpdate.update at 18), and 2 more not listed here. They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 2 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with PatientSummaryUpdate.dataForHandlingBackLoaded (cyclomatic 24), PatientSummaryUpdate.dataForHandlingDoneClickLoaded (cyclomatic 21). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cyclomatic Complexity from 9.4 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
0 method(s) exceeded the cognitive complexity threshold of 15.
D3 · God Classes
32 god class(es) detected.
What to do
- Resolve the 18 TooManyMethods finding(s) in God Classes — start with PatientSummaryScreen.kt, EditPatientScreen.kt, PatientRepository.kt. — One of this dimension's main actionable groups (18 warning-level).
- Resolve the 6 ClassTooLong finding(s) in God Classes — start with PatientRepository.kt, PatientSummaryUpdate.kt, PatientSummaryScreen.kt. — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 6 FileTooLong finding(s) in God Classes — start with PatientRepository.kt, PatientSummaryScreen.kt, EditPatientScreen.kt. — One of this dimension's main actionable groups (6 warning-level).
D4 · Code Duplication
68 duplicated block group(s) detected. 5.3 % of the production lines (4,620 of 87,124) are in a reported copy. A further 116 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
What to do
- Resolve the 14 Edited copy of a member (9 corresponding lines) finding(s) in Code Duplication — start with CommonDrugFrequencyProvider.kt, NewMedicalHistoryEffectHandler.kt, OverdueDownloadWorker.kt. — One of this dimension's main actionable groups (14 warning-level).
- Resolve the 12 Edited copy of a member (8 corresponding lines) finding(s) in Code Duplication — start with ForgotPinConfirmPinEffectHandler.kt, BloodSugarHistoryScreenEffectHandler.kt, BloodSugarHistoryScreenUpdate.kt. — One of this dimension's main actionable groups (12 warning-level).
- Resolve the 8 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with HistoryContainer.kt, EditPatientEffectHandler.kt, ForgotPinConfirmPinEffectHandler.kt. — One of this dimension's main actionable groups (8 warning-level).
D5 · Coupling
8 production modules (Gradle), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; edges a convention plugin adds from buildSrc or build-logic are not visible there; 3 module(s) off the main sequence, with abstractness counted on 7 of the 8 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
What to do
- Resolve the 2 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (2 warning-level).
D6 · Cohesion (LCOM4)
24 of 328 classes have LCOM4 above 3.
What to do
- Resolve the 24 Low cohesion finding(s) in Cohesion (LCOM4) — start with BloodPressureEntrySheet.kt, DeepLinkActivity.kt, TeleconsultDoctorInfoView.kt. — One of this dimension's main actionable groups (24 warning-level).
D7 · Architectural Integrity
No mechanizable ADR was identified, so enforcement is not measured. Dependency cycles not checked (no project-reference graph; where this repository's language has an import-cycle lens, cycles are reported there).
D13 · Secret Scanning
Secret scan ran and found no leaked secrets. 1 detection(s) were excluded as holding no minted credential in material that runs: a name, reference or comparison rather than a value, a readable phrase or pattern, a value that declares itself fake, or development, test, example, mock or demo material.
D14 · License Compliance
0 of 29 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 9 Maven/Gradle manifest(s) declare with a version resolvable from the manifest itself — the same declaration-site closure this analysis reads for dependency currency. The JVM has no lockfile a checkout is guaranteed to carry, so this is deliberately NOT the transitive closure. 10 further coordinate(s) are declared with no version at the declaration site — inherited from a parent POM, a BOM or an unresolved Gradle version reference — and are NOT graded: this verdict covers what the checkout pins, not the full transitive graph. 1 of them resolve to no licence at all on Central, even through their parent POMs; that is missing data, not a violation, and none of them is charged. A further 26 coordinate(s) are not published to Maven Central — another repository (Google's Maven hosts androidx), a SNAPSHOT, or a private artifact — so their licences are not readable from here and they are outside this verdict.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D16 · Bus Factor
10 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is app/src/main/java/org/simple/clinic/summary/PatientSummaryEffectHandler.kt. Counted over 335 of the 2004 production source files in this repository: 1615 are under the ~2,400-byte size floor this dimension measures over, and the remaining 54 have no attributable history left to measure.
D17 · Explicit Debt
42 deducted task-comment markers across 87124 LoC (0.0/KLoC) → score 9.9. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 37 TodoComment finding(s) in Explicit Debt — start with PatientEntryScreenLogicTest.kt (3), MedicalHistoryRepository.kt (3), ResetUserPinTest.kt (2). — One of this dimension's main actionable groups (37 warning-level).
- Resolve the 5 FixmeComment finding(s) in Explicit Debt — start with UserSession.kt (2), PatientEntryScreen.kt (2), ForgotPinConfirmPinScreenLogicTest.kt. — One of this dimension's main actionable groups (5 warning-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 20 document(s) read across 1 unit(s).
D20 · ADR Quality
2 of 13 evaluated ADRs have a defect readable from the log itself (a missing or empty section, no title, a single option, consequences with no cost, no status, a missing enforcement field, a status the log contradicts, a dangling link, an unlinked second decision on one question, a date that is no calendar day). How well each record argues its case is not measured.
What to do
- Resolve the 2 ADR has no Decision section finding(s) in ADR Quality — start with 002-bottom-sheets.md, 011-screen-navigation-v2.md. — One of this dimension's main actionable groups (2 recommendation-level).
D21 · Naming Consistency
24 naming inconsistencies among 1377 declarations measured against a convention their peers follow.
What to do
- Resolve the 6 `patientUUID` spells `UUID` where 618 names in the project spell it… finding(s) in Naming Consistency — start with CholesterolEntryModel.kt (2), Appointment.kt, PatientSummaryEffect.kt. — One of this dimension's main actionable groups (6 recommendation-level).
- Resolve the 3 `appointmentUUID` spells `UUID` where 618 names in the project spell it… finding(s) in Naming Consistency — start with Appointment.kt (2), CallResult.kt. — One of this dimension's main actionable groups (3 recommendation-level).
- Resolve the 2 `calculateCvdRisk` spells `Cvd` where 37 names in the project spell it… finding(s) in Naming Consistency — start with LabBasedCVDRiskCalculator.kt, NonLabBasedCVDRiskCalculator.kt. — One of this dimension's main actionable groups (2 recommendation-level).
D26 · Project Cohesion
1 of 8 build units (Gradle) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with build.gradle.kts. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
46 finding(s): 0 critical, 44 high, 2 medium, 0 low. 36 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 3 file(s) — `gradlew` (line 74, line 178), `newbranch.sh` (line 21), `sms-signature` (line 3, line 4) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 3 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 6 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (6 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- No action in Static Analysis (SAST) — all 36 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (36 issue-level, 0 of them charged here).
D34 · Knowledge Freshness
314 of 389 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is app/src/main/java/org/simple/clinic/editpatient/EditPatientScreen.kt. Counted over 389 of the 2004 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 311 Orphaned file finding(s) in Knowledge Freshness — start with BloodSugarEntrySheet.kt, Patient.kt, ContactPatientBottomSheet.kt. — One of this dimension's main actionable groups (311 recommendation-level).
- Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with EditPatientScreen.kt, PatientRepository.kt, PatientEntryScreen.kt. — One of this dimension's main actionable groups (3 recommendation-level).
- Resolve the 1 Concentrated knowledge decay finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
Strongest change-coupling: AppDatabase.kt↔RoomMigrationsModule.kt 98%; MedicalHistoryPayload.kt↔MedicalHistorySync.kt 75%; PatientSummaryEffectHandler.kt↔PatientSummaryUiActions.kt 74%
What to do
- Resolve the 7 Change coupling finding(s) in Change Coupling — start with PatientSummaryEffect.kt (2), AppDatabase.kt, MedicalHistoryPayload.kt. — One of this dimension's main actionable groups (7 warning-level).
- Resolve the 2 Change-coupling hub finding(s) in Change Coupling — start with LookupPatientOnline.kt, PatientSummaryUpdate.kt. — One of this dimension's main actionable groups (2 warning-level).
D36 · Supply-chain Provenance & Signing
1/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 6 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 8 platform declaration(s) and 55 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX5 · Architecture & structure
AX6 · Interface segregation
- `AppDatabase` declares 30 abstract methods: `patientDao`, `addressDao`, `phoneNumberDao`, `patientSearchDao`, `bloodPressureDao`, `prescriptionDao`, `facilityDao`, `userDao`, `appointmentDao`, `overdueAppointmentDao`, `medicalHistoryDao`, `ongoingLoginEntryDao`, `protocolDao`, `protocolDrugDao`, `recentPatientDao`, `businessIdDao`, `missingPhoneReminderDao`, `bloodSugarDao`, `textRecordDao`, `teleconsultFacilityInfoDao`, `teleconsultMedicalOfficersDao`, `teleconsultFacilityWithMedicalOfficersDao`, `teleconsultRecordDao`, `drugDao`, `callResultDao`, `questionnaireDao`, `questionnaireResponseDao`, `patientAttributeDao`, `cvdRiskDao`, `returnScoreDao`. Counted over its public functions with no body, once per name; default-bodied functions and properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — app/src/main/java/org/simple/clinic/AppDatabase.kt:156
- `RoomDao` declares 22 abstract methods: `save`, `latestMeasurements`, `latestMeasurementsImmediate`, `allBloodSugars`, `allBloodSugarsImmediate`, `allBloodSugarsPagingSource`, `withSyncStatus`, `recordsWithSyncStatusBatched`, `updateSyncStatus`, `updateSyncStatusForIdsRaw`, `getOne`, `recordIdsWithSyncStatus`, `count`, `countWithStatus`, `recordedBloodSugarsCountForPatient`, `recordedBloodSugarsCountForPatientImmediate`, `haveBloodSugarsForPatientChangedSince`, `clear`, `purgeDeleted`, `getAllBloodSugarMeasurements`, `deleteWithoutLinkedPatient`, `purgeBloodSugarMeasurementWhenPatientIsNull`. Counted over its public functions with no body, once per name; default-bodied functions and properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — app/src/main/java/org/simple/clinic/bloodsugar/BloodSugarMeasurement.kt:77
- `BloodSugarEntryUi` declares 16 abstract methods: `showRemoveButton`, `hideRemoveButton`, `showEntryTitle`, `showEditTitle`, `showProgress`, `hideProgress`, `setBloodSugarUnitPreferenceLabelToMmol`, `setBloodSugarUnitPreferenceLabelToMg`, `showBloodSugarUnitPreferenceButton`, `hideBloodSugarUnitPreferenceButton`, `showBloodSugarUnitPreferenceLabel`, `hideBloodSugarUnitPreferenceLabel`, `decimalOrNumericBloodSugarInputType`, `numericBloodSugarInputType`, `setLabelForHbA1c`, `setLabelForUnknown`. Counted over its public functions with no body, once per name; default-bodied functions and properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — app/src/main/java/org/simple/clinic/bloodsugar/entry/BloodSugarEntryUi.kt:8
- `BloodSugarEntryUiActions` declares 16 abstract methods: `setBloodSugarReading`, `hideBloodSugarErrorMessage`, `hideDateErrorMessage`, `dismiss`, `showDateEntryScreen`, `setBloodSugarSavedResultAndFinish`, `showConfirmRemoveBloodSugarDialog`, `showBloodSugarUnitSelectionDialog`, `showBloodSugarEmptyError`, `showBloodSugarHighError`, `showBloodSugarLowError`, `showInvalidDateError`, `showDateIsInFutureError`, `showBloodSugarEntryScreen`, `showBloodSugarDate`, `setDateOnInputFields`. Counted over its public functions with no body, once per name; default-bodied functions and properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — app/src/main/java/org/simple/clinic/bloodsugar/entry/BloodSugarEntryUiActions.kt:8
- `RoomDao` declares 27 abstract methods: `withSyncStatus`, `withSyncStatusBatched`, `updateSyncStatus`, `updateSyncStatusForIdsRaw`, `save`, `getOne`, `recordIdsWithStatus`, `bloodPressure`, `bloodPressureImmediate`, `count`, `countWithStatus`, `recordedBloodPressureCountForPatientImmediate`, `recordedBloodPressureCountForPatient`, `newestMeasurementsForPatient`, `newestMeasurementsForPatientImmediate`, `clearData`, `patientToFacilityIds`, `haveBpsForPatientChangedSince`, `allBloodPressures`, `hasBPRecordedToday`, `allBloodPressuresRecordedSinceImmediate`, `allBloodPressuresPagingSource`, `purgeDeleted`, `getAllBloodPressureMeasurements`, `deleteWithoutLinkedPatient`, `purgeBloodPressureMeasurementWhenPatientIsNull`, `isNewestBpEntryHigh`. Counted over its public functions with no body, once per name; default-bodied functions and properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — app/src/main/java/org/simple/clinic/bp/BloodPressureMeasurement.kt:85
- `BloodPressureEntryUi` declares 28 abstract methods: `changeFocusToDiastolic`, `changeFocusToSystolic`, `setBpSavedResultAndFinish`, `hideBpErrorMessage`, `showSystolicLessThanDiastolicError`, `showSystolicLowError`, `showSystolicHighError`, `showDiastolicLowError`, `showDiastolicHighError`, `showSystolicEmptyError`, `showDiastolicEmptyError`, `setSystolic`, `setDiastolic`, `showRemoveBpButton`, `hideRemoveBpButton`, `showEnterNewBloodPressureTitle`, `showEditBloodPressureTitle`, `showConfirmRemoveBloodPressureDialog`, `showBpEntryScreen`, `showDateEntryScreen`, `showInvalidDateError`, `showDateIsInFutureError`, `hideDateErrorMessage`, `setDateOnInputFields`, `showBpDate`, `dismiss`, `showProgress`, `hideProgress`. Counted over its public functions with no body, once per name; default-bodied functions and properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — app/src/main/java/org/simple/clinic/bp/entry/BloodPressureEntryUi.kt:7
- `ContactPatientUi` declares 33 abstract methods: `showProgress`, `hideProgress`, `switchToCallPatientView`, `switchToSetAppointmentReminderView`, `renderPatientDetails`, `showSecureCallUi`, `hideSecureCallUi`, `showNormalCallButtonText`, `showCallButtonText`, `showPatientWithNoPhoneNumberUi`, `hidePatientWithNoPhoneNumberUi`, `showPatientWithPhoneNumberUi`, `hidePatientWithPhoneNumberUi`, `setResultOfCallLabelText`, `setResultLabelText`, `setRegisterAtLabelText`, `setTransferredFromLabelText`, `showPatientWithPhoneNumberCallResults`, `hidePatientWithPhoneNumberCallResults`, `showPatientWithNoPhoneNumberResults`, `showDeadPatientStatus`, `hideDeadPatientStatus`, `renderSelectedAppointmentDate`, `disablePreviousReminderDateStepper`, `enablePreviousReminderDateStepper`, `disableNextReminderDateStepper`, `enableNextReminderDateStepper`, `showCallResult`, `hideCallResult`, `setupAgreedToVisitCallResultOutcome`, `setupRemindToCallLaterCallResultOutcome`, `setupRemovedFromListCallResultOutcome`, `setCallResultUpdatedAtDate`. Counted over its public functions with no body, once per name; default-bodied functions and properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — app/src/main/java/org/simple/clinic/contactpatient/ContactPatientUi.kt:6
- `RoomDao` declares 26 abstract methods: `withSyncStatus`, `withSyncStatusBatched`, `updateSyncStatus`, `updateSyncStatusForIdsRaw`, `save`, `softDelete`, `getOne`, `recordIdsWithSyncStatus`, `count`, `countWithStatus`, `forPatient`, `forPatientImmediate`, `clearData`, `prescription`, `prescriptionImmediate`, `hasPrescriptionForPatientChangedSince`, `hasPrescriptionForPatientChangedToday`, `purgeDeleted`, `updateDrugDuration`, `updateDrugFrequenecy`, `addTeleconsultationIdToDrugsRaw`, `softDeleteIdsRaw`, `getAllPrescribedDrugs`, `deleteWithoutLinkedPatient`, `purgePrescribedDrugWhenPatientIsNull`, `prescriptionCountImmediate`. Counted over its public functions with no body, once per name; default-bodied functions and properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — app/src/main/java/org/simple/clinic/drugs/PrescribedDrug.kt:133
- `EditPatientUi` declares 29 abstract methods: `displayBpPassports`, `setPatientName`, `setPatientPhoneNumber`, `setColonyOrVillage`, `setDistrict`, `setStreetAddress`, `setZone`, `setState`, `setGender`, `setPatientAge`, `setPatientDateOfBirth`, `setAlternateIdTextField`, `setAlternateIdContainer`, `showValidationErrors`, `hideValidationErrors`, `scrollToFirstFieldWithError`, `goBack`, `showDatePatternInDateOfBirthLabel`, `hideDatePatternInDateOfBirthLabel`, `setDateOfBirthAndAgeVisibility`, `showDiscardChangesAlert`, `showProgress`, `hideProgress`, `setupUi`, `setColonyOrVillagesAutoComplete`, `openSimpleScanIdScreen`, `showAddNHIDButton`, `hideAddNHIDButton`, `showIndiaNHIDLabel`. Counted over its public functions with no body, once per name; default-bodied functions and properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — app/src/main/java/org/simple/clinic/editpatient/EditPatientUi.kt:9
- `RoomDao` declares 18 abstract methods: `recordsWithSyncStatus`, `recordsWithSyncStatusBatched`, `updateSyncStatus`, `updateSyncStatusForIdsRaw`, `getOne`, `recordIdsWithSyncStatus`, `save`, `saveHistories`, `count`, `countWithStatus`, `clear`, `historyForPatient`, `historyForPatientImmediate`, `hasMedicalHistoryForPatientChangedSinceImmediate`, `purgeDeleted`, `getAllMedicalHistories`, `deleteWithoutLinkedPatient`, `purgeMedicalHistoryWhenPatientIsNull`. Counted over its public functions with no body, once per name; default-bodied functions and properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — app/src/main/java/org/simple/clinic/medicalhistory/MedicalHistory.kt:141
- `PatientEntryUiActions` declares 18 abstract methods: `prefillFields`, `scrollToFirstFieldWithError`, `scrollFormOnGenderSelection`, `setShowDatePatternInDateOfBirthLabel`, `openMedicalHistoryEntryScreen`, `showEmptyFullNameError`, `showLengthTooShortPhoneNumberError`, `showMissingGenderError`, `showEmptyColonyOrVillageError`, `showEmptyDistrictError`, `showEmptyStateError`, `showEmptyDateOfBirthAndAgeError`, `showInvalidDateOfBirthError`, `showDateOfBirthIsInFutureError`, `showAgeExceedsMaxLimitError`, `showDOBExceedsMaxLimitError`, `showAgeExceedsMinLimitError`, `showDOBExceedsMinLimitError`. Counted over its public functions with no body, once per name; default-bodied functions and properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — app/src/main/java/org/simple/clinic/newentry/PatientEntryUiActions.kt:6
- `RoomDao` declares 28 abstract methods: `recordsWithSyncStatus`, `recordsWithSyncStatusBatched`, `updateSyncStatus`, `updateSyncStatusForIdsRaw`, `getOne`, `recordIdsWithSyncStatus`, `save`, `lastCreatedAppointmentForPatient`, `count`, `countWithStatus`, `markOlderAppointmentsAsVisited`, `saveRemindDate`, `markAsAgreedToVisit`, `markAsVisited`, `cancelWithReason`, `clear`, `markAsVisitedForPatient`, `purgeDeleted`, `purgeUnusedAppointments`, `getAllAppointments`, `getAllAppointmentsForPatient`, `deleteWithoutLinkedPatient`, `purgeAppointmentsWhenPatientIsNull`, `latestOverdueAppointmentForPatient`, `nextAppointmentPatientProfile`, `hasAppointmentForPatientChangedSince`, `latestScheduledAppointmentForPatient`, `appointmentAndPatientInformationForIds`. Counted over its public functions with no body, once per name; default-bodied functions and properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — app/src/main/java/org/simple/clinic/overdue/Appointment.kt:164
- `RoomDao` declares 34 abstract methods: `allPatients`, `getOne`, `recordIdsWithSyncStatus`, `patient`, `patientImmediate`, `updateSyncStatus`, `updateSyncStatusForIdsRaw`, `patientCount`, `patientCountWithStatus`, `clear`, `findPatientsWithBusinessId`, `findPatientsWithBusinessIdImmediate`, `updatePatientStatus`, `compareAndUpdateRecordedAt`, `updateRecordedAt`, `deletePatient`, `updateAssignedFacilityId`, `recordsWithSyncStatus`, `patientProfile`, `patientProfileImmediate`, `allPatientProfiles`, `profilesWithSyncStatusBatched`, `isPatientDefaulter`, `hasPatientChangedSince`, `purgeDeleted`, `purgeDeletedPhoneNumbers`, `purgeDeletedBusinessIds`, `deletePatientsNotInFacilitiesRaw`, `purgePatientAfterRetentionTime`, `contactPatientProfileImmediate`, `villageAndPatientNamesInFacility`, `patientLineListRows`, `patientLineListCount`, `updatePatientReassignmentEligibilityStatus`. Counted over its public functions with no body, once per name; default-bodied functions and properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — app/src/main/java/org/simple/clinic/patient/Patient.kt:85
- `PatientSummaryScreenUi` declares 21 abstract methods: `renderPatientSummaryToolbar`, `populatePatientProfile`, `showDiabetesView`, `hideDiabetesView`, `showTeleconsultButton`, `hideTeleconsultButton`, `showAssignedFacilityView`, `hideAssignedFacilityView`, `hideDoneButton`, `showTeleconsultLogButton`, `hidePatientDiedStatus`, `showPatientDiedStatus`, `showNextAppointmentCard`, `hideNextAppointmentCard`, `showClinicalDecisionSupportAlert`, `hideClinicalDecisionSupportAlert`, `hideClinicalDecisionSupportAlertWithoutAnimation`, `updateStatinNudge`, `showBMIView`, `hideBMIView`, `updateCVDRiskView`. Counted over its public functions with no body, once per name; default-bodied functions and properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — app/src/main/java/org/simple/clinic/summary/PatientSummaryScreenUi.kt:7
- `PatientSummaryUiActions` declares 26 abstract methods: `showScheduleAppointmentSheet`, `showEditPatientScreen`, `goToPreviousScreen`, `goToHomeScreen`, `showUpdatePhoneDialog`, `showAddPhoneDialog`, `showLinkIdWithPatientView`, `showDiagnosisRequiredError`, `showDiagnosisOrReferralRequiredError`, `showHypertensionDiagnosisRequiredError`, `showHypertensionDiagnosisOrReferralRequiredError`, `openPatientContactSheet`, `navigateToTeleconsultRecordScreen`, `openContactDoctorSheet`, `showAddMeasurementsWarningDialog`, `showAddBloodPressureWarningDialog`, `showAddBloodSugarWarningDialog`, `openSelectFacilitySheet`, `dispatchNewAssignedFacility`, `refreshNextAppointment`, `showReassignPatientWarningSheet`, `showDiabetesDiagnosisWarning`, `showHypertensionDiagnosisWarning`, `showTobaccoStatusDialog`, `openBMIEntrySheet`, `openCholesterolEntrySheet`. Counted over its public functions with no body, once per name; default-bodied functions and properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — app/src/main/java/org/simple/clinic/summary/PatientSummaryUiActions.kt:9
What to do
- Split fat interfaces into focused role-interfaces so clients depend only on what they use.
C1 · Data Protection
What to do
- Strengthen data-at-rest protection: vault your keys (AWS KMS / Secrets Manager, GCP KMS / Secret Manager, Azure Key Vault, HashiCorp Vault — not a key compiled into the app) and encrypt the store that holds the personal data (SQLCipher, a Realm encryptionKey, field-level AEAD) — partial coverage still leaves gaps.
- Enforce HTTPS on the server that receives this data: terminate TLS in it (Ktor's sslConnector, Spring's server.ssl and requiresSecure, Netty's SslContextBuilder.forServer) and send Strict-Transport-Security (Ktor's HttpsRedirect), or run it behind a TLS-terminating proxy, so data in transit is always encrypted.
C4 · Data Retention
- A retention mechanism is present, but the data-lifecycle is not yet complete — missing: a scheduled purge / cleanup job (a periodic worker or scheduled task that deletes rows past their retention — @Query("DELETE … WHERE createdAt < :cutoff"), deleteWhere { createdAt less cutoff }, purgeExpired… / deleteOld…).
What to do
- Complete the data-lifecycle story: an expiry limit (a declared maximum age for the stored data — a retention-age setting, or a store-level TTL where your storage offers one), a scheduled purge/cleanup job that enforces it, and a documented retention period covering the personal data.
DM10 · One transaction, one aggregate
- `FakeDataGenerationReceiver.generateFakeData` saves `PatientRepository`, `BloodPressureRepository`, `AppointmentRepository` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated — into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event. — app/src/debug/java/org/simple/clinic/FakeDataGenerationReceiver.kt:86
- `NewMedicalHistoryEffectHandler.registerPatient` saves ``, `UUID` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated — into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event. — app/src/main/java/org/simple/clinic/medicalhistory/newentry/NewMedicalHistoryEffectHandler.kt:56
What to do
- Mutate one aggregate per operation and let the others follow from a domain event — the second aggregate reaching consistency a moment later is the design, not a compromise.
DM11 · Constructible invalid state
- `PrescribedDrug`'s public constructor takes `name`, `dosage`, `rxNormCode` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `PrescribedDrug` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — app/src/main/java/org/simple/clinic/drugs/PrescribedDrug.kt:37
- `Drug`'s public constructor takes `name`, `composition`, `dosage`, `rxNormCode` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `Drug` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — app/src/main/java/org/simple/clinic/drugs/search/Drug.kt:16
- `Facility`'s public constructor takes `name`, `facilityType`, `streetAddress`, `villageOrColony`, … as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `Facility` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — app/src/main/java/org/simple/clinic/facility/Facility.kt:22
- `Patient`'s public constructor takes `fullName` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `Patient` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — app/src/main/java/org/simple/clinic/patient/Patient.kt:39
- `PatientFts`'s public constructor takes `fullName` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `PatientFts` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — app/src/main/java/org/simple/clinic/patient/Patient.kt:507
- `PatientAddress`'s public constructor takes `streetAddress`, `colonyOrVillage`, `zone`, `district`, … as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `PatientAddress` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — app/src/main/java/org/simple/clinic/patient/PatientAddress.kt:18
- `PatientAddressFts`'s public constructor takes `colonyOrVillage` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `PatientAddressFts` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — app/src/main/java/org/simple/clinic/patient/PatientAddress.kt:110
- `PatientPhoneNumber`'s public constructor takes `number` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `PatientPhoneNumber` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — app/src/main/java/org/simple/clinic/patient/PatientPhoneNumber.kt:32
- `PatientPhoneNumberFts`'s public constructor takes `number` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `PatientPhoneNumberFts` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — app/src/main/java/org/simple/clinic/patient/PatientPhoneNumber.kt:92
- `BusinessId`'s public constructor takes `metaData`, `searchHelp` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `BusinessId` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — app/src/main/java/org/simple/clinic/patient/businessid/BusinessId.kt:53
- `BusinessIdFts`'s public constructor takes `searchHelp` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `BusinessIdFts` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — app/src/main/java/org/simple/clinic/patient/businessid/BusinessId.kt:217
- `Protocol`'s public constructor takes `name` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `Protocol` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — app/src/main/java/org/simple/clinic/protocol/Protocol.kt:21
- `ProtocolDrug`'s public constructor takes `name`, `rxNormCode`, `dosage` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `ProtocolDrug` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — app/src/main/java/org/simple/clinic/protocol/ProtocolDrug.kt:31
- `TextRecord`'s public constructor takes `id`, `text` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `TextRecord` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — app/src/main/java/org/simple/clinic/storage/text/TextRecord.kt:12
- `MedicalOfficer`'s public constructor takes `fullName`, `phoneNumber` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `MedicalOfficer` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — app/src/main/java/org/simple/clinic/summary/teleconsultation/sync/MedicalOfficer.kt:16
- `OngoingLoginEntry`'s public constructor takes `phoneNumber`, `pin`, `fullName`, `pinDigest`, … as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `OngoingLoginEntry` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — app/src/main/java/org/simple/clinic/user/OngoingLoginEntry.kt:18
- `User`'s public constructor takes `fullName`, `phoneNumber`, `pinDigest`, `teleconsultPhoneNumber` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `User` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — app/src/main/java/org/simple/clinic/user/User.kt:35
What to do
- Give each aggregate one way in that can refuse — a guarded constructor, value-object parameters that validate themselves, or a private constructor behind a factory that returns a failure.
DM4 · Rich vs anemic model
- `BloodSugarMeasurement` is an aggregate/entity with 8 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/src/main/java/org/simple/clinic/bloodsugar/BloodSugarMeasurement.kt:34
- `BloodPressureMeasurement` is an aggregate/entity with 11 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/src/main/java/org/simple/clinic/bp/BloodPressureMeasurement.kt:34
- `CVDRisk` is an aggregate/entity with 5 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/src/main/java/org/simple/clinic/cvdrisk/CVDRisk.kt:27
- `PrescribedDrug` is an aggregate/entity with 16 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/src/main/java/org/simple/clinic/drugs/PrescribedDrug.kt:37
- `Drug` is an aggregate/entity with 10 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/src/main/java/org/simple/clinic/drugs/search/Drug.kt:16
- `Facility` is an aggregate/entity with 18 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/src/main/java/org/simple/clinic/facility/Facility.kt:22
- `MedicalHistory` is an aggregate/entity with 22 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/src/main/java/org/simple/clinic/medicalhistory/MedicalHistory.kt:40
- `Appointment` is an aggregate/entity with 14 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/src/main/java/org/simple/clinic/overdue/Appointment.kt:37
- `CallResult` is an aggregate/entity with 9 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/src/main/java/org/simple/clinic/overdue/callresult/CallResult.kt:32
- `Patient` is an aggregate/entity with 17 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/src/main/java/org/simple/clinic/patient/Patient.kt:39
- `PatientFts` is an aggregate/entity with 2 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/src/main/java/org/simple/clinic/patient/Patient.kt:507
- `PatientAddress` is an aggregate/entity with 11 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/src/main/java/org/simple/clinic/patient/PatientAddress.kt:18
- `PatientAddressFts` is an aggregate/entity with 2 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/src/main/java/org/simple/clinic/patient/PatientAddress.kt:110
- `PatientPhoneNumber` is an aggregate/entity with 8 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/src/main/java/org/simple/clinic/patient/PatientPhoneNumber.kt:32
- `PatientPhoneNumberFts` is an aggregate/entity with 2 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/src/main/java/org/simple/clinic/patient/PatientPhoneNumber.kt:92
- `BusinessIdFts` is an aggregate/entity with 2 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/src/main/java/org/simple/clinic/patient/businessid/BusinessId.kt:217
- `PatientAttribute` is an aggregate/entity with 6 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/src/main/java/org/simple/clinic/patientattribute/PatientAttribute.kt:27
- `Protocol` is an aggregate/entity with 7 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/src/main/java/org/simple/clinic/protocol/Protocol.kt:21
- `ProtocolDrug` is an aggregate/entity with 9 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/src/main/java/org/simple/clinic/protocol/ProtocolDrug.kt:31
- `Questionnaire` is an aggregate/entity with 4 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/src/main/java/org/simple/clinic/questionnaire/Questionnaire.kt:19
- `QuestionnaireResponse` is an aggregate/entity with 8 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/src/main/java/org/simple/clinic/questionnaireresponse/QuestionnaireResponse.kt:25
- `ReturnScore` is an aggregate/entity with 5 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/src/main/java/org/simple/clinic/returnscore/ReturnScore.kt:23
- `TextRecord` is an aggregate/entity with 2 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/src/main/java/org/simple/clinic/storage/text/TextRecord.kt:12
- `MissingPhoneReminder` is an aggregate/entity with 2 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/src/main/java/org/simple/clinic/summary/addphone/MissingPhoneReminder.kt:14
- `MedicalOfficer` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/src/main/java/org/simple/clinic/summary/teleconsultation/sync/MedicalOfficer.kt:16
- `TeleconsultationFacilityInfo` is an aggregate/entity with 6 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/src/main/java/org/simple/clinic/summary/teleconsultation/sync/TeleconsultationFacilityInfo.kt:16
- `TeleconsultationFacilityMedicalOfficersCrossRef` is an aggregate/entity with 2 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/src/main/java/org/simple/clinic/summary/teleconsultation/sync/TeleconsultationFacilityWithMedicalOfficers.kt:17
- `TeleconsultRecord` is an aggregate/entity with 7 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/src/main/java/org/simple/clinic/teleconsultlog/teleconsultrecord/TeleconsultRecord.kt:22
- `User` is an aggregate/entity with 20 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/src/main/java/org/simple/clinic/user/User.kt:35
What to do
- Move business rules onto the aggregates/entities they govern so invariants are enforced at the source, not in anemic services.
DM5 · Encapsulated state
DM7 · Repository granularity
DM9 · Scattered domain decisions
M1 · Documentation (README)
M2 · Architecture documentation
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add spotbugs with find-sec-bugs (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 6 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:4
What to do
- Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
P6 · Release Hygiene
PF1 · Benchmark discipline
- A JMH/Jetpack Benchmark suite exists but nothing turns on its allocation measurement — allocations (the main way hot code pressures a garbage collector or allocator) aren't being measured.
What to do
- Run JMH with the GC profiler (`-prof gc`, or addProfiler(GCProfiler.class)) so allocation rate regressions are visible, not just time.
PF3 · Async & latency hygiene
X1 · Async correctness
X12 · Unreachable branch
X16 · Unfloored truncation loop
X21 · Side-effecting pattern guard
X25 · Inert configuration knob
X27 · Collection changed while being enumerated
X3 · Exception handling
- `catch (ex: Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×5) — app/src/main/java/org/simple/clinic/util/moshi/MapWithAnyValueTypeMoshiAdapter.kt:20, app/src/main/java/org/simple/clinic/monthlyreports/util/StringFormatter.kt:13, app/src/main/java/org/simple/clinic/monthlyreports/util/StringFormatter.kt:21, …
- `catch (e: Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — app/src/main/java/org/simple/clinic/storage/DatabaseEncryptor.kt:129
- `catch (_: Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — app/src/main/java/org/simple/clinic/patient/PatientRepository.kt:767
- An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. — app/src/main/java/org/simple/clinic/monthlyreports/form/compose/QuestionnaireInputField.kt:111
- `catch (_: Throwable)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — app/src/main/java/org/simple/clinic/monthlyreports/form/compose/QuestionnaireUnorderedListItem.kt:62
What to do
- Swallowed exception (caught, then discarded)
X30 · Support guard that admits what it rejects
X5 · Nullable reference types
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 79.9 | Strong | Solid. |
| Architecture | 91.3 | Exemplary | Strongest area. |
| Maturity | 80.6 | Adequate — gated by D34 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 69.7 | Adequate — gated by P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 59.9 | Adequate — gated by D29, D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Domain Modelling | 66.2 | Adequate — gated by DM4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 88.6 | Strong | Solid. |
Unscored — 2 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X7 Silent fallback defaults — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 3 control(s) we could not find positive evidence for
- C3 Audit Trail — Repo shows no audit-logging mechanism (an audit-log table or model — an Exposed table, a data class, a Room entity or a SQL migration's table named for it — Hibernate Envers' @Audited, a JPA entity listener, Hibernate event listener or jOOQ RecordListener that records each change) for sensitive changes — absence of evidence is not evidence of a working control. Record an audit trail in code (or document where it lives) so this dimension can be scored.
- C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. Implement erasure, data export/portability and consent tracking over the subject's records.
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 69 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: Dagger rejects, at compile time, a component that holds a binding with a narrower scope than its own.
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Kotlin code is a Spring, JSR-330 or CDI singleton bean. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads.
- AX4 Dependency direction — not applicable to a CQRS architecture (the inward-dependency rule is for layered/clean styles)
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — the Android app did not build — `./gradlew :app:assembleDebug` exited 1: com.github.requery:sqlite-android:3.49.0. > Could not get resource 'https://jitpack.io/com/github/requery/sqlite-android/3.49.0/sqlite-android-3.49.0.pom'. > Could not GET 'https…; runtime evidence skipped (launch chosen because app/build.gradle.kts applies the Android application plugin and gradlew builds it) This is a statement about this run, not a statement about your application: nothing here says the app is inaccessible, only that it was never run.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- D10 Test Quality — ~75113 lines of test source are present (.kt) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D11 Test Reliability — Test reliability not included — the .kt suite was found but not re-run
- D12 Dependency Hygiene — Not scored — a Gradle build resolved 524 artifact(s) across its subprojects (148 behind a shipped release, reported), but the currency signal was not established over the whole graph, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .kt, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — None of 8 binding record(s) states a rule in checkable form (a backticked element with a prohibition, or an `adr-rules` block), so conformance cannot be read from the code. Write the rule as an `adr-rules` block (`forbid:` a symbol, a package or a dependency) to make it checkable.
- D27 Navigability — symbol resolution incomplete — navigability not assessed
- D30 Dependency Vulnerabilities — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) and a Gradle version catalogue — not scanned yet).
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — 9 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) and a Gradle version catalogue — not scanned yet).
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM1 Aggregate boundaries — no aggregates detected — aggregate-boundary check not applicable
- DM12 Ambient inputs in the domain — no domain-layer types detected — ambient-input check not applicable
- DM2 Strongly-typed ids — no id-bearing domain types detected — strongly-typed-id adoption not assessable
- DM3 Integration-event coupling — no integration events detected — coupling check not applicable
- DM6 Domain ↔ infrastructure boundary — no domain-layer types detected — domain↔infrastructure boundary check not applicable
- DM8 Value-object opportunities — not scored — the deterministic rule found 0 candidate clump(s); its rows are withheld until it has a measured precision of 95 % (a sample of fewer than 10 rows cannot show one)
- ED1 Event-Driven — not scored — this repository shows only 1 of the 3 signals this lens looks for (52 CQRS handler(s))
- ED5 Idempotency — Not assessed, and this one is on us: 52 command handler(s) or message consumer(s) were found here, but this check does not yet recognise persistence writes in this repository's language. Idempotency was neither confirmed nor ruled out — this is a limit of the analyzer, not a finding about your code.
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust and Java, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P2 Observability — This repository's JVM source (7 module(s), 2002 file(s) read) declares no entry point and bootstraps no server, and nothing here deploys a service — it is a library, run inside whatever hosts it, so production observability (structured logging, tracing/metrics, health checks) is N/A. If it grows a binary or a service, the dimension reactivates.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Kotlin was read, and it logs through none that an assembled message defeats: Android's `Log` and Timber, java.util.logging and log4j-api-kotlin take one finished message (as log4net does in C#), or it makes no call through a named logger at all. Calls made through SLF4J, log4j 2 or kotlin-logging (`LoggerFactory.getLogger`, `KotlinLogging.logger {}`) would be judged.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 44 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 362 finding(s)
- TodoComment app/src/test/java/org/simple/clinic/user/resetpin/ResetUserPinTest.kt:169
- TodoComment app/src/test/java/org/simple/clinic/user/resetpin/ResetUserPinTest.kt:186
- TodoComment app/src/test/java/org/simple/clinic/newentry/PatientEntryScreenLogicTest.kt:253
- TodoComment app/src/test/java/org/simple/clinic/newentry/PatientEntryScreenLogicTest.kt:410
- TodoComment app/src/test/java/org/simple/clinic/newentry/PatientEntryScreenLogicTest.kt:478
- TodoComment app/src/test/java/org/simple/clinic/login/LoginUserWithOtpTest.kt:142
- TodoComment app/src/test/java/org/simple/clinic/editpatient/EditPatientEffectHandlerTest.kt:219
- TodoComment app/src/test/java/org/simple/clinic/bp/entry/BloodPressureValidationMockDateValidatorTest.kt:78
- TodoComment app/src/test/java/org/simple/clinic/bp/entry/BloodPressureValidationMockDateValidatorTest.kt:79
- TodoComment app/src/main/java/org/simple/clinic/util/UserInputDatePaddingCharacter.kt:3
- TodoComment app/src/main/java/org/simple/clinic/user/resetpin/ResetUserPin.kt:28
- TodoComment app/src/main/java/org/simple/clinic/user/refreshuser/RefreshCurrentUser.kt:52
- TodoComment app/src/main/java/org/simple/clinic/sync/indicator/SyncIndicatorView.kt:143
- TodoComment app/src/main/java/org/simple/clinic/summary/PatientSummaryEffectHandler.kt:550
- TodoComment app/src/main/java/org/simple/clinic/summary/PatientSummaryEvent.kt:25
- TodoComment app/src/main/java/org/simple/clinic/summary/PatientSummaryEvent.kt:33
- TodoComment app/src/main/java/org/simple/clinic/summary/PatientSummaryScreenKey.kt:16
- TodoComment app/src/main/java/org/simple/clinic/summary/teleconsultation/messagebuilder/ShortTeleconsultMessageBuilder.kt:8
- TodoComment app/src/main/java/org/simple/clinic/registration/phone/RegistrationPhoneEvent.kt:21
- TodoComment app/src/main/java/org/simple/clinic/recentpatientsview/LatestRecentPatientsInit.kt:20
- TodoComment app/src/main/java/org/simple/clinic/protocol/sync/ProtocolPayload.kt:32
- TodoComment app/src/main/java/org/simple/clinic/patient/Answer.kt:34
- TodoComment app/src/main/java/org/simple/clinic/medicalhistory/Answer.kt:42
- TodoComment app/src/main/java/org/simple/clinic/patient/PhoneNumberDetails.kt:3
- TodoComment app/src/main/java/org/simple/clinic/patient/businessid/Identifier.kt:66
- Anemic entity: BloodSugarMeasurement app/src/main/java/org/simple/clinic/bloodsugar/BloodSugarMeasurement.kt:34
- Anemic entity: BloodPressureMeasurement app/src/main/java/org/simple/clinic/bp/BloodPressureMeasurement.kt:34
- Anemic entity: CVDRisk app/src/main/java/org/simple/clinic/cvdrisk/CVDRisk.kt:27
- Anemic entity: PrescribedDrug app/src/main/java/org/simple/clinic/drugs/PrescribedDrug.kt:37
- Anemic entity: Drug app/src/main/java/org/simple/clinic/drugs/search/Drug.kt:16
- Anemic entity: Facility app/src/main/java/org/simple/clinic/facility/Facility.kt:22
- Anemic entity: MedicalHistory app/src/main/java/org/simple/clinic/medicalhistory/MedicalHistory.kt:40
- Anemic entity: Appointment app/src/main/java/org/simple/clinic/overdue/Appointment.kt:37
- Anemic entity: CallResult app/src/main/java/org/simple/clinic/overdue/callresult/CallResult.kt:32
- Anemic entity: Patient app/src/main/java/org/simple/clinic/patient/Patient.kt:39
- Anemic entity: PatientFts app/src/main/java/org/simple/clinic/patient/Patient.kt:507
- Anemic entity: PatientAddress app/src/main/java/org/simple/clinic/patient/PatientAddress.kt:18
- Anemic entity: PatientAddressFts app/src/main/java/org/simple/clinic/patient/PatientAddress.kt:110
- Anemic entity: PatientPhoneNumber app/src/main/java/org/simple/clinic/patient/PatientPhoneNumber.kt:32
- Anemic entity: PatientPhoneNumberFts app/src/main/java/org/simple/clinic/patient/PatientPhoneNumber.kt:92
- Anemic entity: BusinessIdFts app/src/main/java/org/simple/clinic/patient/businessid/BusinessId.kt:217
- Anemic entity: PatientAttribute app/src/main/java/org/simple/clinic/patientattribute/PatientAttribute.kt:27
- Anemic entity: Protocol app/src/main/java/org/simple/clinic/protocol/Protocol.kt:21
- Anemic entity: ProtocolDrug app/src/main/java/org/simple/clinic/protocol/ProtocolDrug.kt:31
- Anemic entity: Questionnaire app/src/main/java/org/simple/clinic/questionnaire/Questionnaire.kt:19
- Anemic entity: QuestionnaireResponse app/src/main/java/org/simple/clinic/questionnaireresponse/QuestionnaireResponse.kt:25
- Anemic entity: ReturnScore app/src/main/java/org/simple/clinic/returnscore/ReturnScore.kt:23
- Anemic entity: TextRecord app/src/main/java/org/simple/clinic/storage/text/TextRecord.kt:12
- Anemic entity: MissingPhoneReminder app/src/main/java/org/simple/clinic/summary/addphone/MissingPhoneReminder.kt:14
- Anemic entity: MedicalOfficer app/src/main/java/org/simple/clinic/summary/teleconsultation/sync/MedicalOfficer.kt:16
- Low cohesion: BloodPressureEntrySheet (LCOM4 9) app/src/main/java/org/simple/clinic/bp/entry/BloodPressureEntrySheet.kt:59
- Low cohesion: DeepLinkActivity (LCOM4 9) app/src/main/java/org/simple/clinic/deeplink/DeepLinkActivity.kt:25
- Low cohesion: TeleconsultDoctorInfoView (LCOM4 8) app/src/main/java/org/simple/clinic/teleconsultlog/prescription/doctorinfo/TeleconsultDoctorInfoView.kt:27
- Low cohesion: PatientsTabLinkView (LCOM4 6) app/src/main/java/org/simple/clinic/home/patients/links/PatientsTabLinkView.kt:30
- Low cohesion: BloodPressureHistoryScreen (LCOM4 5) app/src/main/java/org/simple/clinic/bp/history/BloodPressureHistoryScreen.kt:46
- Low cohesion: DrugsSearchScreen (LCOM4 5) app/src/main/java/org/simple/clinic/drugs/search/DrugsSearchScreen.kt:41
- Low cohesion: AlertFacilityChangeSheet (LCOM4 5) app/src/main/java/org/simple/clinic/facility/alertchange/AlertFacilityChangeSheet.kt:36
- Low cohesion: InstantSearchScreen (LCOM4 5) app/src/main/java/org/simple/clinic/instantsearch/InstantSearchScreen.kt:73
- Low cohesion: RegistrationFacilitySelectionScreen (LCOM4 5) app/src/main/java/org/simple/clinic/registration/facility/RegistrationFacilitySelectionScreen.kt:33
- Low cohesion: SetupActivity (LCOM4 5) app/src/main/java/org/simple/clinic/setup/SetupActivity.kt:42
- Low cohesion: TeleconsultStatusSheet (LCOM4 5) app/src/main/java/org/simple/clinic/summary/teleconsultation/status/TeleconsultStatusSheet.kt:33
- Low cohesion: MedicineFrequencySheet (LCOM4 5) app/src/main/java/org/simple/clinic/teleconsultlog/medicinefrequency/MedicineFrequencySheet.kt:35
- Low cohesion: TeleconsultSharePrescriptionScreen (LCOM4 5) app/src/main/java/org/simple/clinic/teleconsultlog/shareprescription/TeleconsultSharePrescriptionScreen.kt:52
- Low cohesion: DeletePatientScreen (LCOM4 4) app/src/main/java/org/simple/clinic/editpatient/deletepatient/DeletePatientScreen.kt:34
- Low cohesion: RegistrationLoadingScreen (LCOM4 4) app/src/main/java/org/simple/clinic/registration/register/RegistrationLoadingScreen.kt:26
- Low cohesion: ScanSimpleIdScreen (LCOM4 4) app/src/main/java/org/simple/clinic/scanid/ScanSimpleIdScreen.kt:61
- Low cohesion: ScheduleAppointmentEffectHandler (LCOM4 4) app/src/main/java/org/simple/clinic/scheduleappointment/ScheduleAppointmentEffectHandler.kt:31
- Low cohesion: SignatureActivity (LCOM4 4) app/src/main/java/org/simple/clinic/signature/SignatureActivity.kt:18
- Low cohesion: BloodPressureSummaryView (LCOM4 4) app/src/main/java/org/simple/clinic/summary/bloodpressures/ui/BloodPressureSummaryView.kt:69
- Low cohesion: DataSync (LCOM4 4) app/src/main/java/org/simple/clinic/sync/DataSync.kt:39
- Low cohesion: SyncIndicatorView (LCOM4 4) app/src/main/java/org/simple/clinic/sync/indicator/SyncIndicatorView.kt:36
- Low cohesion: DrugDurationSheet (LCOM4 4) app/src/main/java/org/simple/clinic/teleconsultlog/drugduration/DrugDurationSheet.kt:33
- Low cohesion: TeleconsultMedicinesView (LCOM4 4) app/src/main/java/org/simple/clinic/teleconsultlog/prescription/medicines/TeleconsultMedicinesView.kt:41
- Low cohesion: MobiusTestFixture (LCOM4 4) mobius-migration/src/main/java/org/simple/mobius/migration/MobiusTestFixture.kt:21
- TooManyMethods: PatientSummaryScreen app/src/main/java/org/simple/clinic/summary/PatientSummaryScreen.kt:95
- TooManyMethods: EditPatientScreen app/src/main/java/org/simple/clinic/editpatient/EditPatientScreen.kt:111
- TooManyMethods: PatientRepository app/src/main/java/org/simple/clinic/patient/PatientRepository.kt:47
- TooManyMethods: ContactPatientBottomSheet app/src/main/java/org/simple/clinic/contactpatient/ContactPatientBottomSheet.kt:55
- TooManyMethods: BloodSugarEntrySheet app/src/main/java/org/simple/clinic/bloodsugar/entry/BloodSugarEntrySheet.kt:64
- TooManyMethods: BloodPressureEntrySheet app/src/main/java/org/simple/clinic/bp/entry/BloodPressureEntrySheet.kt:59
- TooManyMethods: PatientEntryScreen app/src/main/java/org/simple/clinic/newentry/PatientEntryScreen.kt:88
- TooManyMethods: AppDatabase app/src/main/java/org/simple/clinic/AppDatabase.kt:156
- TooManyMethods: PatientsTabScreen app/src/main/java/org/simple/clinic/home/patients/PatientsTabScreen.kt:68
- TooManyMethods: InstantSearchScreen app/src/main/java/org/simple/clinic/instantsearch/InstantSearchScreen.kt:73
- TooManyMethods: ScheduleAppointmentSheet app/src/main/java/org/simple/clinic/scheduleappointment/ScheduleAppointmentSheet.kt:51
- TooManyMethods: Router app/src/main/java/org/simple/clinic/navigation/v2/Router.kt:21
- TooManyMethods: RoomDao app/src/main/java/org/simple/clinic/patient/Patient.kt:85
- TooManyMethods: CustomDrugEntrySheet app/src/main/java/org/simple/clinic/drugs/selection/custom/CustomDrugEntrySheet.kt:44
- TooManyMethods: OverdueSearchScreen app/src/main/java/org/simple/clinic/home/overdue/search/OverdueSearchScreen.kt:69
- TooManyMethods: PatientSummaryEffectHandler app/src/main/java/org/simple/clinic/summary/PatientSummaryEffectHandler.kt:55
- TooManyMethods: RoomDao app/src/main/java/org/simple/clinic/drugs/PrescribedDrug.kt:133
- TooManyMethods: ScanSimpleIdScreen app/src/main/java/org/simple/clinic/scanid/ScanSimpleIdScreen.kt:61
- Constructible in an invalid state: PrescribedDrug app/src/main/java/org/simple/clinic/drugs/PrescribedDrug.kt:37
- Constructible in an invalid state: Drug app/src/main/java/org/simple/clinic/drugs/search/Drug.kt:16
- Constructible in an invalid state: Facility app/src/main/java/org/simple/clinic/facility/Facility.kt:22
- Constructible in an invalid state: Patient app/src/main/java/org/simple/clinic/patient/Patient.kt:39
- Constructible in an invalid state: PatientFts app/src/main/java/org/simple/clinic/patient/Patient.kt:507
- Constructible in an invalid state: PatientAddress app/src/main/java/org/simple/clinic/patient/PatientAddress.kt:18
- Constructible in an invalid state: PatientAddressFts app/src/main/java/org/simple/clinic/patient/PatientAddress.kt:110
- Constructible in an invalid state: PatientPhoneNumber app/src/main/java/org/simple/clinic/patient/PatientPhoneNumber.kt:32
- Constructible in an invalid state: PatientPhoneNumberFts app/src/main/java/org/simple/clinic/patient/PatientPhoneNumber.kt:92
- Constructible in an invalid state: BusinessId app/src/main/java/org/simple/clinic/patient/businessid/BusinessId.kt:53
- Constructible in an invalid state: BusinessIdFts app/src/main/java/org/simple/clinic/patient/businessid/BusinessId.kt:217
- Constructible in an invalid state: Protocol app/src/main/java/org/simple/clinic/protocol/Protocol.kt:21
- Constructible in an invalid state: ProtocolDrug app/src/main/java/org/simple/clinic/protocol/ProtocolDrug.kt:31
- Constructible in an invalid state: TextRecord app/src/main/java/org/simple/clinic/storage/text/TextRecord.kt:12
- Constructible in an invalid state: MedicalOfficer app/src/main/java/org/simple/clinic/summary/teleconsultation/sync/MedicalOfficer.kt:16
- Constructible in an invalid state: OngoingLoginEntry app/src/main/java/org/simple/clinic/user/OngoingLoginEntry.kt:18
- Constructible in an invalid state: User app/src/main/java/org/simple/clinic/user/User.kt:35
- Edited copy of a member (9 corresponding lines) app/src/main/java/org/simple/clinic/drugs/selection/custom/drugfrequency/country/CommonDrugFrequencyProvider.kt:12
- Edited copy of a member (9 corresponding lines) app/src/main/java/org/simple/clinic/medicalhistory/newentry/NewMedicalHistoryEffectHandler.kt:45
- Edited copy of a member (9 corresponding lines) app/src/main/java/org/simple/clinic/overdue/download/OverdueDownloadWorker.kt:157
- Edited copy of a member (9 corresponding lines) app/src/main/java/org/simple/clinic/bloodsugar/entry/BloodSugarEntryUpdate.kt:124
- Edited copy of a member (9 corresponding lines) app/src/main/java/org/simple/clinic/drugs/EditMedicinesEffectHandler.kt:57
- Edited copy of a member (9 corresponding lines) app/src/main/java/org/simple/clinic/cvdrisk/calculator/LabBasedCVDRiskCalculator.kt:31
- Edited copy of a member (9 corresponding lines) app/src/main/java/org/simple/clinic/overdue/download/formatdialog/DownloadFailedErrorDialog.kt:13
- Edited copy of a member (9 corresponding lines) app/src/main/java/org/simple/clinic/overdue/download/OverdueListDownloader.kt:136
- Edited copy of a member (9 corresponding lines) app/src/main/java/org/simple/clinic/bp/BloodPressureRepository.kt:86
- Edited copy of a member (9 corresponding lines) app/src/main/java/org/simple/clinic/medicalhistory/MedicalHistoryRepository.kt:178
- Edited copy of a member (9 corresponding lines) app/src/main/java/org/simple/clinic/patient/PatientRepository.kt:117
- Edited copy of a member (9 corresponding lines) app/src/main/java/org/simple/clinic/appconfig/StatesFetcher.kt:31
- Edited copy of a member (9 corresponding lines) app/src/main/java/org/simple/clinic/editpatient/EditPatientInit.kt:11
- Edited copy of a member (9 corresponding lines) app/src/main/java/org/simple/clinic/facility/change/FacilityChangeInit.kt:9
- Edited copy of a member (8 corresponding lines) app/src/main/java/org/simple/clinic/forgotpin/confirmpin/ForgotPinConfirmPinEffectHandler.kt:35
- Edited copy of a member (8 corresponding lines) app/src/main/java/org/simple/clinic/bloodsugar/history/BloodSugarHistoryScreenEffectHandler.kt:41
- Edited copy of a member (8 corresponding lines) app/src/main/java/org/simple/clinic/bloodsugar/history/BloodSugarHistoryScreenUpdate.kt:12
- Edited copy of a member (8 corresponding lines) app/src/main/java/org/simple/clinic/login/LoginUserWithOtp.kt:39
- Edited copy of a member (8 corresponding lines) app/src/main/java/org/simple/clinic/selectcountry/SelectCountryUpdate.kt:33
- Edited copy of a member (8 corresponding lines) app/src/main/java/org/simple/clinic/security/pin/verification/LocalUserPinVerificationMethod.kt:17
- Edited copy of a member (8 corresponding lines) app/src/main/java/org/simple/clinic/summary/prescribeddrugs/DrugSummaryEffectHandler.kt:41
- Edited copy of a member (8 corresponding lines) app/src/main/java/org/simple/clinic/drugs/selection/custom/CustomDrugEntryEffectHandler.kt:80
- Edited copy of a member (8 corresponding lines) app/src/main/java/org/simple/clinic/home/overdue/search/OverdueSearchEffectHandler.kt:79
- Edited copy of a member (8 corresponding lines) app/src/main/java/org/simple/clinic/removeoverdueappointment/RemoveOverdueEffectHandler.kt:77
- Edited copy of a member (8 corresponding lines) app/src/main/java/org/simple/clinic/drugs/selection/dosage/DosagePickerEffectHandler.kt:42
- Edited copy of a member (8 corresponding lines) app/src/main/java/org/simple/clinic/home/help/HelpScreenEffectHandler.kt:34
- Duplicated block (8 lines × 2) app/src/main/java/org/simple/clinic/medicalhistory/ui/HistoryContainer.kt:30
- Duplicated block (8 lines × 2) app/src/main/java/org/simple/clinic/editpatient/EditPatientEffectHandler.kt:351
- Duplicated block (8 lines × 2) app/src/main/java/org/simple/clinic/forgotpin/confirmpin/ForgotPinConfirmPinEffectHandler.kt:81
- Duplicated block (8 lines × 2) app/src/main/java/org/simple/clinic/home/overdue/search/OverdueSearchEffectHandler.kt:131
- Duplicated block (8 lines × 2) app/src/main/java/org/simple/clinic/summary/PatientSummaryEffectHandler.kt:479
- Duplicated block (8 lines × 2) app/src/main/java/org/simple/clinic/teleconsultlog/prescription/TeleconsultPrescriptionEffectHandler.kt:91
- Duplicated block (8 lines × 2) app/src/main/java/org/simple/clinic/facility/change/confirm/ConfirmFacilityChangeEffectHandler.kt:72
- Duplicated block (8 lines × 2) app/src/main/java/org/simple/clinic/home/help/HelpScreenInit.kt:8
- Swallowed exception (caught, then discarded) app/src/main/java/org/simple/clinic/util/moshi/MapWithAnyValueTypeMoshiAdapter.kt:20
- Swallowed exception (caught, then discarded) app/src/main/java/org/simple/clinic/storage/DatabaseEncryptor.kt:129
- Swallowed exception (caught, then discarded) app/src/main/java/org/simple/clinic/patient/PatientRepository.kt:767
- Swallowed exception (caught, then discarded) app/src/main/java/org/simple/clinic/monthlyreports/util/StringFormatter.kt:13
- Swallowed exception (caught, then discarded) app/src/main/java/org/simple/clinic/monthlyreports/util/StringFormatter.kt:21
- Swallowed exception (caught, then discarded) app/src/main/java/org/simple/clinic/monthlyreports/util/StringFormatter.kt:30
- Swallowed exception (caught, then discarded) app/src/main/java/org/simple/clinic/monthlyreports/form/compose/QuestionnaireInputField.kt:77
- Swallowed exception (caught, then discarded) app/src/main/java/org/simple/clinic/monthlyreports/form/compose/QuestionnaireUnorderedListItem.kt:62
- Change coupling: AppDatabase.kt ↔ RoomMigrationsModule.kt app/src/main/java/org/simple/clinic/AppDatabase.kt:1
- Change coupling: MedicalHistoryPayload.kt ↔ MedicalHistorySync.kt app/src/main/java/org/simple/clinic/medicalhistory/sync/MedicalHistoryPayload.kt:1
- Change coupling: PatientSummaryEffectHandler.kt ↔ PatientSummaryUiActions.kt app/src/main/java/org/simple/clinic/summary/PatientSummaryEffectHandler.kt:1
- Change coupling: PatientSummaryEffect.kt ↔ PatientSummaryEvent.kt app/src/main/java/org/simple/clinic/summary/PatientSummaryEffect.kt:1
- Change coupling: MedicalHistoryQuestion.kt ↔ NewMedicalHistoryScreen.kt app/src/main/java/org/simple/clinic/medicalhistory/MedicalHistoryQuestion.kt:1
- Change coupling: PatientSummaryEffect.kt ↔ PatientSummaryUiActions.kt app/src/main/java/org/simple/clinic/summary/PatientSummaryEffect.kt:1
- Change coupling: OngoingMedicalHistoryEntry.kt ↔ NewMedicalHistoryScreen.kt app/src/main/java/org/simple/clinic/medicalhistory/OngoingMedicalHistoryEntry.kt:1
- Edited copy of a member (10 corresponding lines) app/src/main/java/org/simple/clinic/editpatient/EditPatientEffectHandler.kt:61
- Edited copy of a member (10 corresponding lines) app/src/main/java/org/simple/clinic/teleconsultlog/shareprescription/TeleconsultSharePrescriptionScreen.kt:258
- Edited copy of a member (10 corresponding lines) app/src/main/java/org/simple/clinic/reassignpatient/ReassignPatientEffectHandler.kt:53
- Edited copy of a member (10 corresponding lines) app/src/main/java/org/simple/clinic/bp/BloodPressureRepository.kt:120
- Edited copy of a member (10 corresponding lines) app/src/main/java/org/simple/clinic/bloodsugar/BloodSugarRepository.kt:118
- Edited copy of a member (10 corresponding lines) app/src/main/java/org/simple/clinic/cvdrisk/CVDRiskRepository.kt:24
- Edited copy of a member (10 corresponding lines) app/src/main/java/org/simple/clinic/summary/PatientSummaryEffectHandler.kt:399
- ClassTooLong: PatientRepository app/src/main/java/org/simple/clinic/patient/PatientRepository.kt:47
- ClassTooLong: PatientSummaryUpdate app/src/main/java/org/simple/clinic/summary/PatientSummaryUpdate.kt:31
- ClassTooLong: PatientSummaryScreen app/src/main/java/org/simple/clinic/summary/PatientSummaryScreen.kt:95
- ClassTooLong: EditPatientScreen app/src/main/java/org/simple/clinic/editpatient/EditPatientScreen.kt:111
- ClassTooLong: PatientSummaryEffectHandler app/src/main/java/org/simple/clinic/summary/PatientSummaryEffectHandler.kt:55
- ClassTooLong: PatientEntryScreen app/src/main/java/org/simple/clinic/newentry/PatientEntryScreen.kt:88
- FileTooLong: patient/PatientRepository.kt app/src/main/java/org/simple/clinic/patient/PatientRepository.kt
- FileTooLong: summary/PatientSummaryScreen.kt app/src/main/java/org/simple/clinic/summary/PatientSummaryScreen.kt
- FileTooLong: editpatient/EditPatientScreen.kt app/src/main/java/org/simple/clinic/editpatient/EditPatientScreen.kt
- FileTooLong: summary/PatientSummaryUpdate.kt app/src/main/java/org/simple/clinic/summary/PatientSummaryUpdate.kt
- FileTooLong: summary/PatientSummaryEffectHandler.kt app/src/main/java/org/simple/clinic/summary/PatientSummaryEffectHandler.kt
- FileTooLong: newentry/PatientEntryScreen.kt app/src/main/java/org/simple/clinic/newentry/PatientEntryScreen.kt
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Edited copy of a member (13 corresponding lines) app/src/main/java/org/simple/clinic/medicalhistory/MedicalHistory.kt:100
- Edited copy of a member (13 corresponding lines) app/src/main/java/org/simple/clinic/bp/BloodPressureLevel.kt:46
- Edited copy of a member (13 corresponding lines) app/src/main/java/org/simple/clinic/home/overdue/search/OverdueSearchScreen.kt:187
- Edited copy of a member (13 corresponding lines) app/src/main/java/org/simple/clinic/registration/confirmpin/RegistrationConfirmPinScreen.kt:118
- Edited copy of a member (13 corresponding lines) app/src/main/java/org/simple/clinic/selectcountry/adapter/SelectableCountryItem.kt:25
- Edited copy of a member (13 corresponding lines) app/src/main/java/org/simple/clinic/summary/bloodpressures/BloodPressureSummaryViewEffectHandler.kt:82
- Duplicated block (9 lines × 2) app/src/main/java/org/simple/clinic/editpatient/EditPatientScreen.kt:816
- Duplicated block (9 lines × 2) app/src/main/java/org/simple/clinic/drugs/PrescriptionRepository.kt:110
- Duplicated block (9 lines × 2) app/src/main/java/org/simple/clinic/overdue/download/OverdueListDownloader.kt:176
- Duplicated block (9 lines × 2) app/src/main/java/org/simple/clinic/teleconsultlog/prescription/patientinfo/TeleconsultPatientInfoEffectHandler.kt:22
- Duplicated block (9 lines × 2) app/src/main/java/org/simple/clinic/bloodsugar/entry/BloodSugarEntryUpdate.kt:146
- Duplicated block (9 lines × 2) app/src/main/java/org/simple/clinic/teleconsultlog/prescription/doctorinfo/TeleconsultDoctorInfoEffectHandler.kt:64
- Duplicated block (7 lines × 2) app/src/main/java/org/simple/clinic/bloodsugar/BloodSugarHistoryListItemPagingSource.kt:80
- Duplicated block (7 lines × 2) app/src/main/java/org/simple/clinic/home/overdue/OverdueScreen.kt:209
- Duplicated block (7 lines × 2) app/src/main/java/org/simple/clinic/widgets/ItemAdapter.kt:25
- Duplicated block (7 lines × 2) app/src/main/java/org/simple/clinic/bloodsugar/history/BloodSugarHistoryScreen.kt:217
- Duplicated block (7 lines × 2) app/src/main/java/org/simple/clinic/bloodsugar/history/adapter/BloodSugarHistoryListItem.kt:119
- Duplicated block (7 lines × 2) app/src/main/java/org/simple/clinic/teleconsultlog/prescription/TeleconsultPrescriptionInit.kt:9
- FixmeComment app/src/test/java/org/simple/clinic/forgotpin/confirmpin/ForgotPinConfirmPinScreenLogicTest.kt:61
- FixmeComment app/src/main/java/org/simple/clinic/user/UserSession.kt:167
- FixmeComment app/src/main/java/org/simple/clinic/user/UserSession.kt:168
- FixmeComment app/src/main/java/org/simple/clinic/newentry/PatientEntryScreen.kt:245
- FixmeComment app/src/main/java/org/simple/clinic/newentry/PatientEntryScreen.kt:680
- Edited copy of a member (12 corresponding lines) app/src/main/java/org/simple/clinic/home/patients/links/PatientsTabLinkEffectHandler.kt:34
- Edited copy of a member (12 corresponding lines) app/src/main/java/org/simple/clinic/drugs/selection/custom/CustomDrugEntryUpdate.kt:47
- Edited copy of a member (12 corresponding lines) app/src/main/java/org/simple/clinic/bloodsugar/entry/BloodSugarEntrySheet.kt:367
- Edited copy of a member (12 corresponding lines) app/src/release/java/org/simple/clinic/remoteconfig/firebase/FirebaseRemoteConfigModule.kt:17
- Edited copy of a member (12 corresponding lines) app/src/main/java/org/simple/clinic/bloodsugar/entry/BloodSugarEntryUpdate.kt:107
- Edited copy of a member (19 corresponding lines) app/src/main/java/org/simple/clinic/editpatient/EditPatientScreen.kt:460
- Edited copy of a member (19 corresponding lines) app/src/main/java/org/simple/clinic/drugs/selection/custom/CustomDrugEntryEffectHandler.kt:59
- Edited copy of a member (19 corresponding lines) app/src/main/java/org/simple/clinic/scheduleappointment/ScheduleAppointmentEffectHandler.kt:65
- Edited copy of a member (19 corresponding lines) app/src/main/java/org/simple/clinic/drugs/selection/dosage/DosagePickerEffectHandler.kt:64
- Edited copy of a member (19 corresponding lines) app/src/main/java/org/simple/clinic/patient/PatientRepository.kt:358
- Edited copy of a member (14 corresponding lines) app/src/main/java/org/simple/clinic/newentry/country/BangladeshInputFieldsProvider.kt:20
- Edited copy of a member (14 corresponding lines) app/src/main/java/org/simple/clinic/newentry/country/EthiopiaInputFieldsProvider.kt:19
- Edited copy of a member (14 corresponding lines) app/src/main/java/org/simple/clinic/bloodsugar/entry/BloodSugarEntryEffectHandler.kt:101
- Edited copy of a member (14 corresponding lines) app/src/main/java/org/simple/clinic/home/overdue/search/OverdueSearchUpdate.kt:71
- Edited copy of a member (14 corresponding lines) app/src/main/java/org/simple/clinic/instantsearch/InstantSearchEffectHandler.kt:82
- Edited copy of a member (16 corresponding lines) app/src/main/java/org/simple/clinic/drugs/selection/DrugListItem.kt:41
- Edited copy of a member (16 corresponding lines) app/src/main/java/org/simple/clinic/bloodsugar/entry/BloodSugarEntryUpdate.kt:77
- Edited copy of a member (16 corresponding lines) app/src/main/java/org/simple/clinic/editpatient/EditPatientScreen.kt:576
- Edited copy of a member (16 corresponding lines) app/src/main/java/org/simple/clinic/drugs/PrescriptionRepository.kt:209
- Edited copy of a member (16 corresponding lines) app/src/main/java/org/simple/clinic/patientattribute/sync/PatientAttributeSync.kt:38
- Edited copy of a member (15 corresponding lines) app/src/main/java/org/simple/clinic/summary/teleconsultation/messagebuilder/LongTeleconsultMessageBuilder.kt:150
- Edited copy of a member (15 corresponding lines) app/src/main/java/org/simple/clinic/login/pin/LoginPinScreen.kt:106
- Edited copy of a member (15 corresponding lines) app/src/main/java/org/simple/clinic/drugs/search/DrugSearchEffectHandler.kt:43
- Edited copy of a member (15 corresponding lines) app/src/main/java/org/simple/clinic/summary/nextappointment/ui/NextAppointment.kt:189
- Edited copy of a member (15 corresponding lines) app/src/main/java/org/simple/clinic/consent/onboarding/OnboardingConsentScreen.kt:65
- Edited copy of a member (17 corresponding lines) app/src/main/java/org/simple/clinic/summary/compose/StatinNudgeDescription.kt:58
- Edited copy of a member (17 corresponding lines) app/src/main/java/org/simple/clinic/editpatient/EditPatientEffectHandler.kt:291
- Edited copy of a member (17 corresponding lines) app/src/main/java/org/simple/clinic/summary/updatephone/UpdatePhoneNumberEffectHandler.kt:47
- Edited copy of a member (17 corresponding lines) app/src/main/java/org/simple/clinic/drugs/PrescribedDrug.kt:76
- Edited copy of a member (11 corresponding lines) app/src/main/java/org/simple/clinic/bloodsugar/entry/BloodSugarEntrySheet.kt:355
- Edited copy of a member (11 corresponding lines) app/src/main/java/org/simple/clinic/textInputdatepicker/TextInputDatePickerValidator.kt:25
- Edited copy of a member (11 corresponding lines) app/src/main/java/org/simple/clinic/overdue/download/OverdueListDownloader.kt:212
- Edited copy of a member (11 corresponding lines) app/src/main/java/org/simple/clinic/recentpatient/RecentPatientItem.kt:35
- Edited copy of a member (7 corresponding lines) app/src/main/java/org/simple/clinic/medicalhistory/SelectOngoingDiabetesTreatmentErrorDialog.kt:23
- Edited copy of a member (7 corresponding lines) app/src/main/java/org/simple/clinic/summary/addphone/AddPhoneNumberEffectHandler.kt:35
- Edited copy of a member (7 corresponding lines) app/src/main/java/org/simple/clinic/summary/bloodpressures/ui/BloodPressureSummaryView.kt:227
- Edited copy of a member (7 corresponding lines) app/src/main/java/org/simple/clinic/home/help/HelpScreen.kt:67
- Duplicated block (15 lines × 2) app/src/main/java/org/simple/clinic/editpatient/EditPatientScreen.kt:505
- Duplicated block (15 lines × 2) app/src/main/java/org/simple/clinic/home/overdue/compose/OverdueScreenView.kt:99
- Duplicated block (15 lines × 2) app/src/main/java/org/simple/clinic/overdue/download/OverdueListDownloader.kt:192
- Duplicated block (15 lines × 2) app/src/main/java/org/simple/clinic/scheduleappointment/ScheduleAppointmentEffectHandler.kt:66
- Edited copy of a member (32 corresponding lines) app/src/main/java/org/simple/clinic/overdue/download/OverdueDownloadWorker.kt:167
- Edited copy of a member (32 corresponding lines) app/src/main/java/org/simple/clinic/navigation/v2/fragments/BaseBottomSheet.kt:110
- Edited copy of a member (32 corresponding lines) app/src/main/java/org/simple/clinic/summary/bloodpressures/ui/BloodPressureSummaryView.kt:146
- Edited copy of a member (26 corresponding lines) app/src/main/java/org/simple/clinic/bloodsugar/BloodSugarHistoryListItemPagingSource.kt:52
- Edited copy of a member (26 corresponding lines) app/src/main/java/org/simple/clinic/enterotp/EnterOtpScreen.kt:267
- Edited copy of a member (26 corresponding lines) common-ui/src/main/java/org/simple/clinic/common/ui/components/Button.kt:72
- Edited copies of one member (3 members, 8+ corresponding lines) app/src/main/java/org/simple/clinic/bloodsugar/entry/confirmremovebloodsugar/ConfirmRemoveBloodSugarDialog.kt:62
- Edited copies of one member (3 members, 8+ corresponding lines) app/src/main/java/org/simple/clinic/medicalhistory/newentry/NewMedicalHistoryScreen.kt:82
- Edited copies of one member (3 members, 8+ corresponding lines) app/src/main/java/org/simple/clinic/home/help/HelpScreenEffectHandler.kt:43
- Duplicated block (16 lines × 2) app/src/main/java/org/simple/clinic/enterotp/EnterOtpScreen.kt:270
- Duplicated block (16 lines × 2) app/src/main/java/org/simple/clinic/main/TheActivity.kt:191
- Duplicated block (16 lines × 2) app/src/main/java/org/simple/clinic/overdue/download/OverdueListDownloader.kt:234
- Duplicated block (13 lines × 2) app/src/main/java/org/simple/clinic/editpatient/EditPatientScreen.kt:465
- Duplicated block (13 lines × 2) app/src/main/java/org/simple/clinic/forgotpin/confirmpin/ForgotPinConfirmPinUiRenderer.kt:13
- Duplicated block (13 lines × 2) app/src/main/java/org/simple/clinic/bloodsugar/history/BloodSugarHistoryScreenEffectHandler.kt:74
- Duplicated block (9 lines × 3) app/src/main/java/org/simple/clinic/navigation/v2/fragments/BaseBottomSheet.kt:132
- Duplicated block (9 lines × 3) app/src/main/java/org/simple/clinic/bloodsugar/entry/BloodSugarEntrySheet.kt:245
- Duplicated block (9 lines × 3) app/src/main/java/org/simple/clinic/bloodsugar/BloodSugarRepository.kt:90
- Duplicated block (8 lines × 3) app/src/main/java/org/simple/clinic/summary/PatientSummaryUpdate.kt:149
- Duplicated block (8 lines × 3) app/src/main/java/org/simple/clinic/contactpatient/ContactPatientEffectHandler.kt:60
- Duplicated block (8 lines × 3) app/src/main/java/org/simple/clinic/medicalhistory/newentry/NewMedicalHistoryEffectHandler.kt:115
- Duplicated block (10 lines × 2) app/src/main/java/org/simple/clinic/util/moshi/LocalDateMoshiAdapter.kt:15
- Duplicated block (10 lines × 2) app/src/main/java/org/simple/clinic/overdue/download/OverdueListDownloader.kt:251
- Duplicated block (10 lines × 2) app/src/main/java/org/simple/clinic/signature/SignatureEffectHandler.kt:30
- REDACTED
- REDACTED
- MethodTooLong: SimpleThemeKt.parseSimpleTypography common-ui/src/main/java/org/simple/clinic/common/ui/theme/SimpleTheme.kt:133
- MethodTooLong: SettingsUIKt.SettingsList app/src/main/java/org/simple/clinic/settings/SettingsUI.kt:106
- Change-coupling hub: LookupPatientOnline.kt → AppDatabase.kt, MedicalHistoryRepository.kt, RoomMigrationsModule.kt app/src/main/java/org/simple/clinic/patient/onlinelookup/api/LookupPatientOnline.kt
- Change-coupling hub: PatientSummaryUpdate.kt → PatientSummaryEffectHandler.kt, PatientSummaryInit.kt, StatinNudge.kt app/src/main/java/org/simple/clinic/summary/PatientSummaryUpdate.kt
- Edited copies of one member (3 members, 13+ corresponding lines) app/src/main/java/org/simple/clinic/appupdate/AppUpdateNotificationWorker.kt:165
- Edited copies of one member (3 members, 13+ corresponding lines) app/src/main/java/org/simple/clinic/summary/PatientSummaryScreen.kt:691
- Edited copy of a member (18 corresponding lines) app/src/main/java/org/simple/clinic/overdue/download/OverdueDownloadWorker.kt:83
- Edited copy of a member (18 corresponding lines) app/src/main/java/org/simple/clinic/util/WindowInsetsExt.kt:50
- Edited copies of one member (3 members, 10+ corresponding lines) app/src/main/java/org/simple/clinic/appupdate/criticalupdatedialog/CriticalAppUpdateDialog.kt:160
- Edited copies of one member (3 members, 10+ corresponding lines) app/src/main/java/org/simple/clinic/contactpatient/CreateReminderForAppointment.kt:31
- Edited copy of a member (5 corresponding lines) app/src/main/java/org/simple/clinic/summary/addphone/AddPhoneNumberEffectHandler.kt:28
- Edited copy of a member (5 corresponding lines) app/src/main/java/org/simple/clinic/overdue/download/OverdueListDownloader.kt:166
- Edited copy of a member (4 corresponding lines) app/src/main/java/org/simple/clinic/bloodsugar/history/BloodSugarHistoryScreen.kt:186
- Edited copy of a member (4 corresponding lines) app/src/main/java/org/simple/clinic/bloodsugar/entry/BloodSugarEntryEffectHandler.kt:96
- Duplicated block (34 lines × 2) app/src/main/java/org/simple/clinic/summary/bloodpressures/ui/BloodPressureSummary.kt:58
- Duplicated block (34 lines × 2) app/src/main/java/org/simple/clinic/drugstockreminders/enterdrugstock/EnterDrugStockWebViewClient.kt:12
- Duplicated block (17 lines × 2) app/src/main/java/org/simple/clinic/summary/PatientSummaryUpdate.kt:448
- Duplicated block (17 lines × 2) app/src/main/java/org/simple/clinic/summary/bloodpressures/ui/BloodPressureSummaryItem.kt:84
- Duplicated block (8 lines × 4) app/src/main/java/org/simple/clinic/drugs/search/sync/DrugSync.kt:28
- Duplicated block (8 lines × 4) app/src/main/java/org/simple/clinic/forgotpin/confirmpin/ForgotPinConfirmPinEffectHandler.kt:72
- Duplicated block (6 lines × 2) app/src/main/java/org/simple/clinic/bloodsugar/entry/BloodSugarEntryUpdate.kt:186
- Duplicated block (6 lines × 2) app/src/main/java/org/simple/clinic/bloodsugar/history/adapter/BloodSugarHistoryListItem.kt:132
- Duplicated block (12 lines × 2) app/src/main/java/org/simple/clinic/editpatient/EditPatientScreen.kt:521
- Duplicated block (12 lines × 2) app/src/main/java/org/simple/clinic/enterotp/EnterOtpEffectHandler.kt:87
- Duplicated block (11 lines × 2) app/src/main/java/org/simple/clinic/bloodsugar/history/BloodSugarHistoryScreen.kt:197
- Duplicated block (11 lines × 2) app/src/main/java/org/simple/clinic/summary/bloodpressures/BloodPressureSummaryViewEffectHandler.kt:59
- Off the main sequence: :simple-visuals
- Off the main sequence: :simple-platform
- PatientSummaryUpdate.dataForHandlingBackLoaded (cyclomatic 24) app/src/main/java/org/simple/clinic/summary/PatientSummaryUpdate.kt:620
- PatientSummaryUpdate.dataForHandlingDoneClickLoaded (cyclomatic 21) app/src/main/java/org/simple/clinic/summary/PatientSummaryUpdate.kt:570
- REDACTED
- REDACTED
- Near-duplicate member pair (78 shared lines) app/src/main/java/org/simple/clinic/summary/bloodpressures/ui/BloodPressureSummary.kt:36
- Members sharing a duplicated core (4 members, 50+ identical tokens) app/src/main/java/org/simple/clinic/summary/PatientSummaryUpdate.kt:147
- Edited copy of a member (38 corresponding lines) app/src/main/java/org/simple/clinic/summary/PatientSummaryUpdate.kt:581
- Edited copy of a member (50 corresponding lines) app/src/main/java/org/simple/clinic/summary/assignedfacility/ui/AssignedFacility.kt:27
- Edited copy of a member (36 corresponding lines) app/src/main/java/org/simple/clinic/summary/PatientSummaryEffectHandler.kt:567
- Edited copy of a member (34 corresponding lines) app/src/main/java/org/simple/clinic/summary/PatientSummaryEffectHandler.kt:204
- Edited copy of a member (23 corresponding lines) app/src/main/java/org/simple/clinic/overdue/download/OverdueDownloadWorker.kt:133
- Edited copies of one member (3 members, 25+ corresponding lines) app/src/main/java/org/simple/clinic/bp/BloodPressureHistoryListItemPagingSource.kt:84
- Edited copy of a member (24 corresponding lines) app/src/main/java/org/simple/clinic/editpatient/EditPatientScreen.kt:815
- Edited copy of a member (22 corresponding lines) app/src/main/java/org/simple/clinic/home/overdue/compose/OverdueScreenView.kt:92
- Edited copy of a member (21 corresponding lines) app/src/main/java/org/simple/clinic/medicalhistory/MedicalHistory.kt:118
- Edited copies of one member (3 members, 14+ corresponding lines) app/src/main/java/org/simple/clinic/monthlyreports/form/compose/QuestionnaireHeader.kt:18
- Edited copies of one member (4 members, 21+ corresponding lines) app/src/main/java/org/simple/clinic/summary/medicalhistory/ui/MedicalHistorySummary.kt:74
- Edited copies of one member (4 members, 14+ corresponding lines) common-ui/src/main/java/org/simple/clinic/common/ui/theme/SimpleTheme.kt:32
- Edited copies of one member (3 members, 9+ corresponding lines) app/src/main/java/org/simple/clinic/appupdate/AppUpdateModule.kt:57
- Edited copies of one member (4 members, 18+ corresponding lines) app/src/main/java/org/simple/clinic/login/LoginUserWithOtp.kt:50
- Edited copies of one member (3 members, 22+ corresponding lines) app/src/main/java/org/simple/clinic/summary/assignedfacility/AssignedFacilityView.kt:73
- Edited copies of one member (4 members, 7+ corresponding lines) app/src/main/java/org/simple/clinic/medicalhistory/SelectDiagnosisOrReferralRequiredErrorDialog.kt:23
- Edited copies of one member (3 members, 7+ corresponding lines) app/src/main/java/org/simple/clinic/bloodsugar/entry/BloodSugarEntrySheet.kt:225
- Edited copies of one member (8 members, 3+ corresponding lines) app/src/main/java/org/simple/clinic/bloodsugar/sync/BloodSugarSync.kt:28
- Edited copy of a member (6 corresponding lines) app/src/main/java/org/simple/clinic/deeplink/DeepLinkActivity.kt:128
- Duplicated block (24 lines × 3) app/src/main/java/org/simple/clinic/summary/bloodpressures/ui/BloodPressureSummary.kt:103
- Duplicated block (23 lines × 2) app/src/main/java/org/simple/clinic/overdue/download/OverdueDownloadWorker.kt:168
- Duplicated block (19–20 lines × 2) app/src/main/java/org/simple/clinic/medicalhistory/MedicalHistoryRepository.kt:26
- Duplicated block (20 lines × 2) app/src/main/java/org/simple/clinic/summary/bloodpressures/ui/BloodPressureSummary.kt:37
- Duplicated block (17–19 lines × 3) app/src/main/java/org/simple/clinic/medicalhistory/ui/BMIContainer.kt:36
- Duplicated block (17–19 lines × 2) app/src/main/java/org/simple/clinic/summary/PatientSummaryUpdate.kt:592
- Duplicated block (16–17 lines × 2) app/src/main/java/org/simple/clinic/summary/bloodpressures/ui/BloodPressureSummaryItem.kt:35
- Duplicated block (13 lines × 3) app/src/main/java/org/simple/clinic/navigation/v2/fragments/BaseBottomSheet.kt:116
- Duplicated block (11 lines × 3) app/src/main/java/org/simple/clinic/medicalhistory/ui/BMIContainer.kt:94
- Duplicated block (8–10 lines × 2) app/src/main/java/org/simple/clinic/drugs/selection/custom/CustomDrugEntryEffectHandler.kt:67
- Duplicated block (7–8 lines × 2) app/src/main/java/org/simple/clinic/home/overdue/compose/OverdueUiModelMapper.kt:354
- Duplicated block (6 lines × 4) app/src/main/java/org/simple/clinic/summary/PatientSummaryUpdate.kt:148
- Duplicated block (17 lines × 7) app/src/main/java/org/simple/clinic/bloodsugar/BloodSugarMeasurementType.kt:27
- Duplicated block (5 lines × 2) app/src/main/java/org/simple/clinic/bloodsugar/entry/BloodSugarEntrySheet.kt:392
- Duplicated block (10 lines × 7) app/src/main/java/org/simple/clinic/bloodsugar/selection/type/BloodSugarTypePickerSheet.kt:66
- Duplicated block (10 lines × 3) app/src/main/java/org/simple/clinic/deeplink/DeepLinkActivity.kt:85
- Duplicated block (12 lines × 3) app/src/main/java/org/simple/clinic/forgotpin/confirmpin/ForgotPinConfirmPinInit.kt:8
- One operation mutates 3 aggregates: FakeDataGenerationReceiver.generateFakeData app/src/debug/java/org/simple/clinic/FakeDataGenerationReceiver.kt:86
- One operation mutates 2 aggregates: NewMedicalHistoryEffectHandler.registerPatient app/src/main/java/org/simple/clinic/medicalhistory/newentry/NewMedicalHistoryEffectHandler.kt:56
- Swallowed exception (empty catch) app/src/main/java/org/simple/clinic/monthlyreports/form/compose/QuestionnaireInputField.kt:111
Minor — 366 finding(s)
- Orphaned file app/src/main/java/org/simple/clinic/bloodsugar/entry/BloodSugarEntrySheet.kt:1
- Orphaned file app/src/main/java/org/simple/clinic/patient/Patient.kt:1
- Orphaned file app/src/main/java/org/simple/clinic/contactpatient/ContactPatientBottomSheet.kt:1
- Orphaned file app/src/main/java/org/simple/clinic/bp/entry/BloodPressureEntrySheet.kt:1
- Orphaned file app/src/main/java/org/simple/clinic/navigation/v2/Router.kt:1
- Orphaned file app/src/main/java/org/simple/clinic/editpatient/EditPatientEffectHandler.kt:1
- Orphaned file app/src/main/java/org/simple/clinic/home/patients/PatientsTabScreen.kt:1
- Orphaned file app/src/main/java/org/simple/clinic/instantsearch/InstantSearchScreen.kt:1
- Orphaned file app/src/main/java/org/simple/clinic/AppDatabase.kt:1
- Orphaned file app/src/main/java/org/simple/clinic/scanid/ScanSimpleIdScreen.kt:1
- Orphaned file app/src/main/java/org/simple/clinic/home/overdue/search/OverdueSearchScreen.kt:1
- Orphaned file app/src/main/java/org/simple/clinic/widgets/Views.kt:1
- Orphaned file app/src/main/java/org/simple/clinic/settings/SettingsUI.kt:1
- Orphaned file app/src/main/java/org/simple/clinic/overdue/Appointment.kt:1
- Orphaned file app/src/main/java/org/simple/clinic/patient/OngoingNewPatientEntry.kt:1
- Orphaned file app/src/main/java/org/simple/clinic/scheduleappointment/ScheduleAppointmentSheet.kt:1
- Orphaned file app/src/main/java/org/simple/clinic/home/HomeScreen.kt:1
- Orphaned file common-ui/src/main/java/org/simple/clinic/common/ui/theme/SimpleTheme.kt:1
- Orphaned file app/src/main/java/org/simple/clinic/bp/entry/BloodPressureEntryEffectHandler.kt:1
- Orphaned file app/src/main/java/org/simple/clinic/summary/bloodsugar/ui/BloodSugarSummaryView.kt:1
- Orphaned file app/src/main/java/org/simple/clinic/teleconsultlog/shareprescription/TeleconsultSharePrescriptionScreen.kt:1
- Orphaned file app/src/main/java/org/simple/clinic/contactpatient/views/CallPatientView.kt:1
- Orphaned file app/src/main/java/org/simple/clinic/main/TheActivity.kt:1
- Orphaned file app/src/main/java/org/simple/clinic/widgets/PatientSearchResultItemView.kt:1
- Orphaned file app/src/main/java/org/simple/clinic/drugs/PrescribedDrug.kt:1
- Fat interface: AppDatabase (30 abstract methods) app/src/main/java/org/simple/clinic/AppDatabase.kt:156
- Fat interface: RoomDao (22 abstract methods) app/src/main/java/org/simple/clinic/bloodsugar/BloodSugarMeasurement.kt:77
- Fat interface: BloodSugarEntryUi (16 abstract methods) app/src/main/java/org/simple/clinic/bloodsugar/entry/BloodSugarEntryUi.kt:8
- Fat interface: BloodSugarEntryUiActions (16 abstract methods) app/src/main/java/org/simple/clinic/bloodsugar/entry/BloodSugarEntryUiActions.kt:8
- Fat interface: RoomDao (27 abstract methods) app/src/main/java/org/simple/clinic/bp/BloodPressureMeasurement.kt:85
- Fat interface: BloodPressureEntryUi (28 abstract methods) app/src/main/java/org/simple/clinic/bp/entry/BloodPressureEntryUi.kt:7
- Fat interface: ContactPatientUi (33 abstract methods) app/src/main/java/org/simple/clinic/contactpatient/ContactPatientUi.kt:6
- Fat interface: RoomDao (26 abstract methods) app/src/main/java/org/simple/clinic/drugs/PrescribedDrug.kt:133
- Fat interface: EditPatientUi (29 abstract methods) app/src/main/java/org/simple/clinic/editpatient/EditPatientUi.kt:9
- Fat interface: RoomDao (18 abstract methods) app/src/main/java/org/simple/clinic/medicalhistory/MedicalHistory.kt:141
- Fat interface: PatientEntryUiActions (18 abstract methods) app/src/main/java/org/simple/clinic/newentry/PatientEntryUiActions.kt:6
- Fat interface: RoomDao (28 abstract methods) app/src/main/java/org/simple/clinic/overdue/Appointment.kt:164
- Fat interface: RoomDao (34 abstract methods) app/src/main/java/org/simple/clinic/patient/Patient.kt:85
- Fat interface: PatientSummaryScreenUi (21 abstract methods) app/src/main/java/org/simple/clinic/summary/PatientSummaryScreenUi.kt:7
- Fat interface: PatientSummaryUiActions (26 abstract methods) app/src/main/java/org/simple/clinic/summary/PatientSummaryUiActions.kt:9
- `patientUUID` spells `UUID` where 618 names in the project spell it `Uuid` app/src/main/java/org/simple/clinic/overdue/Appointment.kt:348
- `patientUUID` spells `UUID` where 618 names in the project spell it `Uuid` app/src/main/java/org/simple/clinic/summary/PatientSummaryEffect.kt:68
- `patientUUID` spells `UUID` where 618 names in the project spell it `Uuid` app/src/main/java/org/simple/clinic/summary/addcholesterol/CholesterolEntryModel.kt:11
- `patientUUID` spells `UUID` where 618 names in the project spell it `Uuid` app/src/main/java/org/simple/clinic/summary/addcholesterol/CholesterolEntryModel.kt:17
- `patientUUID` spells `UUID` where 618 names in the project spell it `Uuid` app/src/main/java/org/simple/clinic/summary/medicalhistory/MedicalHistorySummaryEffect.kt:8
- `patientUUID` spells `UUID` where 618 names in the project spell it `Uuid` app/src/main/java/org/simple/clinic/summary/nextappointment/NextAppointmentUiActions.kt:6
- `appointmentUUID` spells `UUID` where 618 names in the project spell it `Uuid` app/src/main/java/org/simple/clinic/overdue/Appointment.kt:233
- `appointmentUUID` spells `UUID` where 618 names in the project spell it `Uuid` app/src/main/java/org/simple/clinic/overdue/Appointment.kt:245
- `appointmentUUID` spells `UUID` where 618 names in the project spell it `Uuid` app/src/main/java/org/simple/clinic/overdue/callresult/CallResult.kt:156
- Most significant orphaned file app/src/main/java/org/simple/clinic/editpatient/EditPatientScreen.kt:1
- Most significant orphaned file app/src/main/java/org/simple/clinic/patient/PatientRepository.kt:1
- Most significant orphaned file app/src/main/java/org/simple/clinic/newentry/PatientEntryScreen.kt:1
- ADR has no Decision section doc/arch/002-bottom-sheets.md:1
- ADR has no Decision section doc/arch/011-screen-navigation-v2.md:1
- `calculateCvdRisk` spells `Cvd` where 37 names in the project spell it `CVD` app/src/main/java/org/simple/clinic/cvdrisk/calculator/LabBasedCVDRiskCalculator.kt:18
- `calculateCvdRisk` spells `Cvd` where 37 names in the project spell it `CVD` app/src/main/java/org/simple/clinic/cvdrisk/calculator/NonLabBasedCVDRiskCalculator.kt:16
- Duplicated predicate app/src/main/java/org/simple/clinic/drugstockreminders/enterdrugstock/EnterDrugStockWebViewClient.kt:42
- Duplicated predicate app/src/main/java/org/simple/clinic/medicalhistory/newentry/NewMedicalHistoryViewModel.kt:23
- Partial data-retention evidence
- Off-boarding risk: anonymized user #1
- `setupCallResultOutcomeUI` spells `UI` where 260 names in the project spell it `Ui` app/src/main/java/org/simple/clinic/contactpatient/ContactPatientUiRenderer.kt:53
- `setUpUIForCreatingDrugEntry` spells `UI` where 260 names in the project spell it `Ui` app/src/main/java/org/simple/clinic/drugs/selection/custom/CustomDrugEntryUiRenderer.kt:59
- `setUpUIForUpdatingDrugEntry` spells `UI` where 260 names in the project spell it `Ui` app/src/main/java/org/simple/clinic/drugs/selection/custom/CustomDrugEntryUiRenderer.kt:64
- `drugStockFormURL` spells `URL` where 22 names in the project spell it `Url` app/src/main/java/org/simple/clinic/drugstockreminders/DrugStockReminderApiModule.kt:42
- `ScanIndiaNationalHealthID` spells `ID` where 481 names in the project spell it `Id` app/src/main/java/org/simple/clinic/editpatient/EditPatientScreen.kt:920
- `DrugStockFormURL` spells `URL` where 22 names in the project spell it `Url` app/src/main/java/org/simple/clinic/main/TypedPreference.kt:20
- `appointmentID` spells `ID` where 481 names in the project spell it `Id` app/src/main/java/org/simple/clinic/overdue/callresult/CallResultRepository.kt:53
- `hasNationalHealthID` spells `ID` where 481 names in the project spell it `Id` app/src/main/java/org/simple/clinic/patient/PatientProfile.kt:38
- `isOpenedFromEditPatientScreenToAddNhid` spells `Nhid` where 30 names in the project spell it `NHID` app/src/main/java/org/simple/clinic/scanid/ScanSimpleIdModel.kt:35
- `NationalHealthIDErrorDialog` spells `ID` where 481 names in the project spell it `Id` app/src/main/java/org/simple/clinic/scanid/scannedqrcode/NationalHealthIDErrorDialog.kt:10
- `SettingsUIKt` spells `UI` where 260 names in the project spell it `Ui` app/src/main/java/org/simple/clinic/settings/SettingsUI.kt:1
- `loadBmiReading` spells `Bmi` where 33 names in the project spell it `BMI` app/src/main/java/org/simple/clinic/summary/PatientSummaryEffectHandler.kt:680
- `loadMedicalRegistrationID` spells `ID` where 481 names in the project spell it `Id` app/src/main/java/org/simple/clinic/teleconsultlog/shareprescription/TeleconsultSharePrescriptionEffectHandler.kt:100
- Projects may be oversized for their cohesion app/build.gradle.kts:1
- Concentrated knowledge decay
- REDACTED
- REDACTED
- No SAST REDACTED:4
- Benchmarks don't track allocations
- Silent fallback default in catch app/src/main/java/org/simple/clinic/monthlyreports/util/StringFormatter.kt:13
Minor — 1 finding(s)
- Off the main sequence: :common-ui
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=0 --max-count=200" --report-format json --report-path /tmp/watchdog-gitleaks-1b375fd6e59e4dd1b703f37ad6a2f005/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=200 --max-count=800" --report-format json --report-path /tmp/watchdog-gitleaks-1b375fd6e59e4dd1b703f37ad6a2f005/history-1.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history-1.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=1000 --max-count=3200" --report-format json --report-path /tmp/watchdog-gitleaks-1b375fd6e59e4dd1b703f37ad6a2f005/history-2.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history-2.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=4200 --max-count=7222" --report-format json --report-path /tmp/watchdog-gitleaks-1b375fd6e59e4dd1b703f37ad6a2f005/history-3.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history-3.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-1b375fd6e59e4dd1b703f37ad6a2f005/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 46 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) and a Gradle version catalogue — not scanned yet). | 0 | — |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 9 file(s) — `app/src/main/java/org/simple/clinic/cvdrisk/CVDRiskCalculationSheet.kt`, `app/src/main/java/org/simple/clinic/drugs/selection/custom/drugfrequency/country/DrugFrequencyLabel.kt`, `app/src/main/java/org/simple/clinic/monthlyreports/form/compose/QuestionnaireInputField.kt`, `app/src/main/java/org/simple/clinic/patient/onlinelookup/api/SecondsDuration.kt`, `app/src/main/java/org/simple/clinic/scanid/IndiaNHIDDateOfBirth.kt`, … (+4 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) and a Gradle version catalogue — not scanned yet). | 0 | — |