Logging symptoms associated with a medication

At a glance

Project structure

Source bundle/
└── MedsSymptomsLoggingApp/
    ├── MedsSymptomsLoggingApp.swift
    ├── Views/
    │   ├── Charts/
    │   │   ├── MedicationChartsView+ChartsView.swift
    │   │   ├── MedicationChartsView.swift
    │   │   └── MedicationChartsView+MedicationSelectorView.swift
    │   ├── TabsView.swift
    │   └── HealthKitAuthorizationGatedView.swift
    ├── Models/
    │   ├── AnnotatedMedicationConceptModel.swift
    │   ├── DoseEventModel.swift
    │   ├── Stores/
    │   │   └── HealthStore.swift
    │   └── SymptomModel.swift
    └── Data Sources/
        ├── DoseEventProvider.swift
        └── MedicationProvider.swift

Structure observations

• Architecturally prominent files are ranked from entry points and role-named declarations; resource-only paths are omitted.
• Primary languages: Swift.
• The verified tree contains 4 project/configuration file(s) and 27 source declaration(s).

Overall architecture

flowchart LR
    N1["MedsSymptomsLoggingApp"]
    N2["TabsView"]
    N3["HealthStore"]
    N4["DoseEventProvider"]
    N5["HealthKit / HealthKitUI APIs"]
    N1 --> N2
    N2 --> N3
    N3 --> N4
    N4 --> N5

Reference code

MedsSymptomsLoggingApp/MedsSymptomsLoggingApp.swift:11 — architecture anchor

@main
struct MedsSymptomsLoggingApp: App {
    private let healthStore = HealthStore.shared.healthStore

    @State var triggerMedicationsAuthorization: Bool = false
    @State var healthDataAuthorized: Bool?

    var body: some Scene {
        WindowGroup {
            TabsView(toggleHealthDataAuthorization: $triggerMedicationsAuthorization,
                     healthDataAuthorized: $healthDataAuthorized)
            .onAppear {
                triggerMedicationsAuthorization.toggle()
            }
            .healthDataAccessRequest(store: healthStore,
                                     objectType: .userAnnotatedMedicationType(),
                                     trigger: triggerMedicationsAuthorization,
                                     completion: { @Sendable result in
                Task { @MainActor in
                    switch result {
                    case .success:
                        healthDataAuthorized = true
                    case .failure(let error):
                        print("Error when requesting HealthKit read authorizations: \(error)")
                    }
                }
            })
        }
    }
}

Interpretation

The arrows summarize the source-visible entry, role-named types or folders, and framework direction; when nodes come from structural folders, the sequence is a high-level interpretation rather than proof that every adjacent node calls the next. Ownership is claimed only where the next section cites a stored property or assignment. The diagram is intentionally limited to the dominant path into HealthKit.

Ownership and state

classDiagram
    MedsSymptomsLoggingApp *-- Bool : triggerMedicationsAuthorization
    MedsSymptomsLoggingApp *-- Bool : healthDataAuthorized
    ChartsView o-- DateConfiguration : dateConfiguration
    ChartsView *-- Array : chartSeries

Ownership evidence

MedsSymptomsLoggingApp/MedsSymptomsLoggingApp.swift:15 — stored dependency or nearest verified ownership anchor

@main
struct MedsSymptomsLoggingApp: App {
    // ...
    @State var triggerMedicationsAuthorization: Bool = false
    // ...
}

Composition arrows indicate a source-visible construction expression or locally owned value state; aggregation means the owner stores or receives a dependency without proving exclusive lifetime ownership.

Concurrency, scheduling, and thread safety

Evidence limit: actor isolation, async/await, or Task creation does not by itself prove background-thread execution; Sendable conformance alone does not prove thread-safe mutation.

@MainActor/MainActor.run, DispatchQueue.main, and RunLoop.main are reported as distinct isolation, queue, and event-loop mechanisms. A plain Task is kept separate from Task.detached; neither is labeled as a background thread.

Reference code

MedsSymptomsLoggingApp/Data Sources/DoseEventProvider.swift:11 — representative execution boundary

@Observable @MainActor class DoseEventProvider: Sendable {
    let healthStore: HKHealthStore
    // ...
}

State propagation, frameworks, and dependencies

Evidence limit: an import proves a source-level compilation dependency at the cited line; it does not prove runtime use, architectural adoption, or whether a Swift package is a direct application dependency.

receive(on:) describes downstream delivery scheduling, while subscribe(on:) describes upstream subscription/request/cancel scheduling. An import Combine alone establishes neither behavior nor a Store, reducer, Redux, or other application architecture.

Class and protocol design

MedsSymptomsLoggingApp/MedsSymptomsLoggingApp.swift:12 — representative type boundary

@main
struct MedsSymptomsLoggingApp: App {
    private let healthStore = HealthStore.shared.healthStore
    // ...
}

No local protocol conformance is claimed as protocol-oriented design; external framework conformances are listed only as dependencies.

Access control

Reference code

MedsSymptomsLoggingApp/Data Sources/DoseEventProvider.swift:19 — representative boundary

@Observable @MainActor class DoseEventProvider: Sendable {
    // ...
    private(set) var doseEvents: [DoseEventModel] = []
    // ...
}

Swift declarations without a modifier are internal; explicit private, fileprivate, private(set), public, or open entries above are interpreted by language semantics. Objective-C/C samples instead rely on header and implementation boundaries, which are not equivalent to Swift lexical privacy.

Logic ownership and placement

Design patterns

Naming conventions

• Types: App: MedsSymptomsLoggingApp; Model: DoseEventModel, SymptomModel; Provider: DoseEventProvider, MedicationProvider; Store: HealthStore; View: ArchivedMedicationView, ChartsView, DateIntervalPaginationView, DoseEventView, HealthKitAuthorizationGatedView.
• Protocols: no local protocol declaration in the scanned source.
• Methods: chartPoints, chartPoint, decrement, increment, todayView, calendarChartsView.
• Files: MedsSymptomsLoggingApp/MedsSymptomsLoggingApp.swift, MedsSymptomsLoggingApp/Models/DoseEventModel.swift, MedsSymptomsLoggingApp/Models/Stores/HealthStore.swift, MedsSymptomsLoggingApp/Models/SymptomModel.swift, MedsSymptomsLoggingApp/Views/Charts/MedicationChartsView.swift, MedsSymptomsLoggingApp/Views/TabsView.swift.

Architecture takeaways

• MedsSymptomsLoggingApp is the main source-visible entry or composition anchor for this sample.
• Framework work reaches SwiftUI, HealthKit, Charts, HealthKitUI through a deliberately small high-level chain; the detailed API graph remains inside the cited implementation files.
• Stored-property evidence identifies lifecycle collaboration; it does not by itself prove exclusive object ownership.
• Access-control conclusions separate verified language visibility from the likely design rationale.
• The source does not justify labeling the design protocol-oriented.

Source map

• Official Apple documentation