Bring HealthKit's FHIR Output in Line With the Published Profiles

[PSchmiedmayer]

♻️ Current situation & Problem

HealthKit samples converted to FHIR did not match the profiles grove-fhir publishes: metadata and provenance used spellings the guides do not define, and a release once shipped observations that declared a profile they violated.

⚙️ Release Notes

• HealthKit FHIR output is aligned with the vocabulary the guides publish, across metadata, provenance, time zones, state of mind, ECG, category values, quantities, and workouts.
• Platform metadata moves to grove-platform-metadata, with the metadata key carried in a key sub-extension rather than nested in the URL, and source records to grove-source-record-id.
• Contained devices gain a form factor and a gateway operating system name, both derived from manufacturer and model and marked as inferred where written.
• The platform vocabulary the framework writes is dumped for the guide to publish, so the code systems in grove-fhir are generated from the values Grove actually emits instead of being re-derived.

📚 Documentation

The conversion helpers document which spellings are written versus only read, and Migrating to Grove.md reflects the new metadata shape.

✅ Testing

• GroveHealthKitFHIR on macOS: 16 suites covering category, quantity, correlation, workout, ECG, state-of-mind, metadata, time zone, and superseded-spelling behaviour, plus the macro expansions.
• A conformance fixture target emits one resource per shape, which Scripts/validate-fhir-conformance.sh puts through the HL7 validator against both published guide packages.

Code of Conduct & Contributing Guidelines

By creating and submitting this pull request, you agree to follow our Code of Conduct and Contributing Guidelines:

• I agree to follow the Code of Conduct and Contributing Guidelines.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[coderabbitai]

Important

• 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 7d66d051-dcb1-4a1d-8d47-41b49d061e54

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[PSchmiedmayer]

Contract target for the next revision: preserve this PR as the Grove Swift/HealthKit reference implementation for grove-fhir #6, but move the shared subject/source-identity/sensor/gateway/recording/study/provenance rules into a platform-neutral layer before the final package switch.

Health Connect is not being discarded because it is absent from Swift. Its Android implementation destination is MyHeartCounts-Android #31, which will target the same Mobile profiles and provide independent fixtures. Likewise, My Heart Counts clinical passthrough, study attribution, and metadata/privacy needs require explicit destinations rather than blanket deletion from the prototype inventory.

When #6 settles the package, rebase this PR on those accepted profiles and retain its deterministic HealthKit mappings/tests as evidence for grove-fhir #8. This note does not authorize merging the PR or changing its runners.

[PSchmiedmayer]

Superseded by #67, which rewrites this work on the catalog-driven converter and the published v0.2 profiles. Sensor coverage, stable output identity, metadata-key handling and device provenance all carry over; the vocabulary is now sourced from the grove-fhir catalogs with a CI drift check rather than a golden dump in this repo.