Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add RelatedPersons resources - generate from existing Patient resources #8

Closed
dt-r opened this issue Mar 25, 2024 · 2 comments · Fixed by #49
Closed

Add RelatedPersons resources - generate from existing Patient resources #8

dt-r opened this issue Mar 25, 2024 · 2 comments · Fixed by #49
Assignees

Comments

@dt-r
Copy link
Contributor

dt-r commented Mar 25, 2024

Add RelatedPerson sample data.

  1. Confirm suitability of, and amend as needed RelatedPersons from au core 0.2.2-preview
  2. Assess and select the personas from Services Australia to be RelatedPersons (some were generated as 'families')
  3. Assess initial gaps, add any additional RelatedPersons for 'minimum' set
  4. Design and develop those RelatedPersons instances (assume csv file)
StephThaoOng added a commit that referenced this issue Aug 7, 2024
Added Coverage.
Added RelatedPerson (partial fix for #8).
Added Specimen.
Removed redundant AU Core Inferno Tests Postman collection.
Updated Readme.
StephThaoOng added a commit that referenced this issue Aug 8, 2024
Added Coverage.
Added RelatedPerson (partial fix for #8).
Added Specimen.
Removed redundant AU Core Inferno Tests Postman collection.
Updated Readme.
@heathfrankel
Copy link
Collaborator

@dt-r what is needed for this?
For starters, RelatedPerson is currently part of AU Core. Where do you want feedback on suitability?

We currently have one scenario for RelatedPerson as a performer of an observation (weight), which is not MS. This has been manually created located in direct-fhir-test-resources.

Services Australia data has almost no information to help with deriving RelatedPerson resources. It may be possible to use medicare number to derive children, but there will be no explicit relationship so significant effort will be required to synthesise this data. Suggest more efficient to just manually fix this data if necessary.

Profiles that have MS elements that reference RelatedPerson are Diagnostic and Pathology Result Observation, Encounter and MedicationRequest.
Personally, I would suggest that a RelatedPerson is not an applicable performer of a Diagnostic or Pathology Result observation.
An example of an RelatedPerson in Encounter and MedicationRequest can be produced to support these scenarios.

Is this sufficient?

@heathfrankel
Copy link
Collaborator

heathfrankel commented Sep 24, 2024

Added PR #49

This contains a new RelatedPerson.csv and associated mapping.
CSV contains synthesised data from Services Australia data based on Medicare Card Number. The first IRN is the RelatedPerson. Subsequent IRNs are the patient.
Based on the gender and the aged difference of the first IRN the relationship is derived as either FTH, MTH, WIFE or HUSB.

heathfrankel added a commit that referenced this issue Sep 25, 2024
StephThaoOng added a commit that referenced this issue Sep 30, 2024
#8 Added RelatedPerson.csv, CSV2RelatedPerson.map and generated instances
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants