hl7au / au-fhir-base Goto Github PK

The HL7 AU Organization profile has 2 slices for the element Organization.type to cater for:

• ANZSIC class only codes (slice: anzsicClassType)
• ANZSIC activities only (slice: anzsicActivityType)

The source for both when looking at their respective terminologies is the ABS ANZSIC page. The class only representation is discoverable, via the deeper level page here: http://www.abs.gov.au/ausstats/[email protected]/Latestproducts/F6650BC55BC31757CA257B9500133C17?opendocument

However, I cannot seem to find a representation of the activities codes as they are listed on the valueset and codesystem pages in the base-ig.

Therefore, I am just wondering about the source of the activities only ANZCIC codes.

Extension for ingredient strength as text

I suggest that profiles that include LOINC or SNOMED CT codes should have copyright notices?

Currently au-prescription profile allows 0..* grounds-for-concurrent-supply extension. Should this be 0..1 - only one ground per prescription? Please update.

The Agency has a draft RelatedPerson that can be offered up to the HL7 AU base IG, following some revisions for alignment to other HL7 AU content.
This can be the subject of a PR, as required.

Hi Brett,

• Can you please check if the invariant at the following link
  

  au-fhir-base/resources/au-patient.xml

  Line 317 in 54c1700

  <expression value="type.coding.exists() and type.text != 'DVA Number'" />

type.coding.exists() and type.text != 'DVA Number'
is doing what the statement states:
"DVA Number identifier type text must be 'DVA Number' when colour is not specified"

As it seems to be working differently to me.

• Similarly about inv-dva-number-gold, inv-dva-number-lilac, inv-dva-number-orange, inv-dva-number-white

Thanks.
Vikas

Hi Brett,
The extension Receiving Application does not have an example.
Suggest there be an example present for ballot.

Hi Brett (@oridashi),

In the following file (Line 16) https://github.com/hl7au/au-fhir-base/blob/master/resources/structuredefinition-grounds-for-concurrent-supply.xml#L16
the context is set to MedicationRequest.

While this extension is also used in the MedicationDispense context (Line 43) https://github.com/hl7au/au-fhir-base/blob/master/resources/au-dispenserecord.xml#L43

So I have the following queries:

1. Shall this "grounds-for-concurrent-supply" Extension file additionally include the context of MedicationDispense?
2. If yes then does this type of change applies to other extension files like Medication Brand Name or Medication Generic Files?
3. The IGPublisher is not giving any error in the qa.html, so does this merit a Zulip query or a GForge ticket?

Just to mention that Firely Forge tool also does not seem to be consistent in handling this and in raising the flag. Although this is just a comment to log the observation about that particular profiling tool.

If this is an issue and based on your feedback how it needs to be fixed, I can create a pull request.
Please let me know your suggestions.

Thanks heaps.
Vikas

Different values for publisher for profiles
In au-device - Health Level Seven Australia (Patient Administration)
In au-pbs-pharma-manufacturer - Health Level Seven Australia (Medications WG)
In au-observation-age - Health Level Seven Australia (Patient Administration)
In au-bodysite - Health Level Seven Australia
In au-condition - Health Level Seven Australia

What is wanted for observations, such as au-bodyheight and au-bodyweight?

• Health Level Seven Australia
• Health Level Seven Australia (Orders and Observations WG)
• something else

Hi Brett,
The extension Receiving Application does not have an example.
Suggest there be an example present for ballot.

private, pbs, rpbs, crg - entitlement

The current Address profile caters for Australian as well as non-Australian residences. To cater for these 2 address categories, the profile has a number of invariants doing the job of differentiating the 2 categories. As such, there are a number of elements represented as text that could be better represented using terminology particularly given that NCTS support is imminent.

This ticket is aimed at proposing some improvements (yet to be determined) that will eventually be offered up in the form of a pull request.

There are a handful of identifier namespaces in the organization profile that are hosted in the hl7.org.au domain, but do not resolve.

It is understood that technically namespaces do not have to resolve, but this query is more for whenever the HL7 Au base IG is being readied for its v1.0 milestone, would it be preferable that they do resolve for v1.0?

The namespaces are:

• http://hl7.org.au/id/abn
• http://hl7.org.au/id/acn
• http://hl7.org.au/id/arbn

https://en.wikipedia.org/wiki/Standard_for_the_Uniform_Scheduling_of_Medicines_and_Poisons TGA schedule needs to be added

Hi Brett,
The extension Metadata Source URI does not have an example.
Suggest there be an example present for ballot.

The examples for the newly added profile au-observation-age have a couple of errors that need to be corrected. For example:

• ObservationAge1 - has a value with the unit of litres ("4.12 10^12/L")
• ObservationAge2 - has a value without units ("12-18")

These will be fixed in a forthcoming pull request.

Also the intent is to provide in total 5 age examples each demonstrating a specific variation; such as:

• Example for "12-18 months"
• Example for "12 months"
• Example for "6 months to <5 years"
• Example for "6 months and over"
• Example for "4 years"

AHPRA registration number should exist in in Practitioner.qualification; repeating and related to specialty

look at timezone extension for HealthcareService.availabilityTime

Hi Brett,
The extension Assigning Authority does not have an example.
Suggest there be an example present for ballot.

Advice

1. A single corporate NATA/RCPA accreditation number (2639) and then each Laboratory also has their individual NATA accreditation site number, e.g.,

NATA/RCPA Accreditation No. 2639
Corporate Site No. 12542

NATA/RCPA Accreditation No. 2639
Corporate Site No. 12544

2. The Corporate number is four digits, the Laboratory number may be either four or five digits.  There are no leading zeros on the reports provided.
   

approval number recorded for prescription (RPBS, PBS)

Hi Brett,
The extension Medication Generic Name does not have an example.
Suggest there be an example present for ballot.

Hi Brett,
The extension Medication Brand Name does not have an example.
Suggest there be an example present for ballot.

A request to add Care Agency Employee Identifier (CAE-I) to au-practitioner profile.

The potential fixed values and constraints will be -
fixed value for system = http://ns.electronichealth.net.au/id/pcehr/caei/1.0
constraints -
The value shall be a 16 digit number
The identifier SHALL contain a prefix of 9
The identifier shall pass the Luhn algorithm check

If this identifier is added the Fixed value for System, Code and Display for type.coding element shall be requested from HL7 AU.

add 3.0 FHIR version to cannonical url for IG; these profiles are FHIR version specific

identifier.system has fixed value of "http://pbs.gov.au/identifier/manufacturer"
Is this the correct value? The actual page cannot be found.
Description & Constraints column says this is a placeholder URL: "PBS manufacturer (placeholder URL)"

these have been identified as incorrect by agency and will be changed to another as advised

The standard STU3 extension of birthPlace allows recording of a patient's registered place of birth. In Australia, recording of a patient's country of birth and the Australian state / territory of birth is commonplace.

Propose:

• add this extension into the AU Patient profile with cardinality 0..1
• modify the extension to point to the HL7 AU base address profile, thereby providing support for the Australian states and territories.

Plan: Candidate pull request

create a base Composition profile -
add extension http://hl7.org.au/fhir/StructureDefinition/composition-author-practitionerrole as resource Reference in context of composition

The base patient profile has a number of extensions that have cardinality of 0..* in the patient differential data hierarchy but when viewed directly in Forge the cardinality shows up as 0..1 (as expected). I gather that the cardinality within each extension definition is not getting propagated into the patient profile itself.

For example, the extension for Australian Indigenous status has its root Extension element cardinality set to 0..1. However, the rendered view of the patient profile shows its cardinality as 0..*.

This is seen for these extensions:

• Australian Indigenous status
• Birth Place
• Close the Gap Registration
• IHI status
• IHI Record Status
• Patient birthTime

I also gather that this does require some manual intervention outside of Forge to add the correct cardinality of 0..1.

WHO ATC code definition for Medication

It may be worthwhile adding the STU3 extension for mother's maiden name into the HL7 AU base patient profile as an optional element.

@oridashi has requested an AHPRA identifier slice to added to the AustralianPractitionerRole.
Query whether to use MD - Medical License Number in http://hl7.org/fhir/v2/0203/index.htm, but as AHPRA is used for nurses, so query whether creating an "AHPRA" code in http://hl7.org.au/fhir/v2/0203/index.htm.
Awaiting details from AHRPA on the format on the number ie length, content and check digits etc.

Hi Brett,
The extension Receiving Facility does not have an example.
Suggest there be an example present for ballot.

The early iteration of structure for AHPRA registration number content was based on a discrete identifer slice. More recently, the AHPRA number has moved to being represented in the qualification node instead.

The sole example for practitioner has an AHPRA number but it is within the outdated identifer structures - see these lines. The AHPRA number needs to be updated to reflect this new qualification structure.

The valueset v2 Identifier Type - AU Extended is used for the various identifier slices, specifically as the terminology binding for the element .identifier.type.coding. The terminology binding is set to 'required' in all cases except for the HealthcareService profile identifier slice for HPI-O, where the binding strength is instead 'extensible'.

Not sure if that is a deliberate variation or not and therefore raising to be reviewed.

A PR can be logged if this should change to 'required'.

Hi Brett,
This applies to both identifier slices - please include examples in Description & Constraints column for identifier.value in both slices

Add into the Device profile slice for the PAI-D identifier a fixed value for the identifier.type.coding as has been done with the Organisation HPI-O slice.
The fixed value details (as found in the HL7 V2 Table 0203 - Identifier Type (AU Extended) code system) are:

• System: http://hl7.org.au/fhir/v2/0203
• Code: NDI
• Display: National Device Identifier

(Note that the example device instance already uses the above values.)

Plan: candidate pull request

Discussion https://confluence.hl7australia.com/display/MED/MED20180725+Meeting

• add extension
• confirm two letter PBS code url with PBS

This is in relation to the invariant(s)/constraint(s) for the Luhn algorithm check in the applicable identifiers like IHI, HPI-I, HPI-O, PAI-D, PAI-R, PAI-O etc.

Attached are a few files related to the Luhn Check FHIRpath constraint.
Device.identifier.value.txt
value_1.txt
value_2.txt
value_3.txt

So my main queries here are::

1. Is it safe to add the constraint that -- the identifier.value SHALL be an exactly 16 digit number?
   The current constraint is that -- it shall be a 16 character string; which can be replaced by the above constraint in case there are no issues in doing so.

2. The FHIRpath for the Luhn check has been tested with the “FhirPathTester” as given in the “Device.identifier.value.txt” file. It was tested against the Device resource.
   The modified version as given in the “value_1.txt, value_2.txt, value_3.txt” files could not be tested but is not giving any error when added in the profile using Forge.

Please suggest if it is a good idea to include this constraint and if yes then can the expression be tested by you or someone else for veracity.

A device profile added with PAI-D identifier

Authority and streamlined authority number for prescription

Hi Brett,
The extension Encryption Certificate PEM X509 does not have an example.
Suggest there be an example present for ballot.

@oridashi has requested an employee number identifier slice to added to the AustralianPractitionerRole.
Use the code "EI" Employee number in http://hl7.org/fhir/v2/0203/index.htm.

Hi Brett,
The extension Receiving Facility does not have an example.
Suggest there be an example present for ballot.

Extension NoFixedAddress has the ContextType set to 'resource'.
Should the contextType be 'datatype' as the context for this extension is the Address datatype?

Extension - au-communication
To provide support for outstanding aspects noted in Tracker: https://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=15722

Definition as implemented at this time: https://build.fhir.demo.nhsd.com.au/StructureDefinition-au-communication.html
Profile Usage Reference: https://build.fhir.demo.nhsd.com.au/StructureDefinition-nhsd-healthcareservice.html

NCTS advising on CodeSystem URL changes - these are pending change and will not be as currently provided

Core birthTime extension is now referenced; and included