Add RelatedPersons resources - generate from existing Patient resources

[dt-r]

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)

[heathfrankel]

@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]

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.