swift data and healthkit (apple) omop cmd compatible

Open
  • Is something wrong?
#720 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
15/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
swift
Domain
databases, mobile-dev

Research direction

The issue names no repository file, test, or entry point. First clarify the intended SwiftData and HealthKit integration, the required OMOP CDM scope, and the compatibility criteria before identifying implementation work and a definition of done.

Written by the indexing model from the issue text.

Description

Have you some interest on an OMOP swiftdata healthkit product ?

This appaire difficult but in fact ... this look like this:
import HealthKit

class person {
var person_id: Int64 // person_id INT64 not null,
var gender_concept_id: Int64 // gender_concept_id INT64 not null,
var year_of_birthint: Int64 // year_of_birth INT64 not null,
var month_of_birth: Int64? // month_of_birth INT64,
var day_of_birth: Int64? // day_of_birth INT64,
var birth_datetime: Date? // birth_datetime datetime null,
var race_concept_id: Int64 // race_concept_id INT64 not null,
var ethnicity_concept_id:Int64 // ethnicity_concept_id INT64 not null,
var location_id: Int64? // location_id INT64,
var provider_id: Int64? // provider_id INT64,
var care_site_id: Int64? // care_site_id INT64,
var person_source_value: String // person_source_value STRING,
var gender_source_value HKBiologicalSex? // gender_source_value STRING,
var gender_source_concept_id: Int64 // gender_source_concept_id INT64,
var race_source_value: String // race_source_value STRING,
var race_source_concept_id: Int64, // race_source_concept_id INT64,
var ethnicity_source_value: String, // ethnicity_source_value STRING,
var ethnicity_source_concept_id: Int64, //ethnicity_source_concept_id INT64
}
etc...
Thank for your response

Dominant language
HTML
Stars
1.1k
Forks
513
Avg merge
8d 3h
Merged PRs (30d)
4

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from OHDSI/CommonDataModel

All issues in OHDSI/CommonDataModel

Similar issues

More Databases issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.