Page tree
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

This page list all the queries that Child Health Project team wants to discuss with CWG and decide a path forward. 

Generic Query

Serial Number


Date and Decision

Members Present


At this moment NCDHC uses only a handful of elements from the default FHIR profiles. This gives an option to the implementer to supply more data than originally supported by NCDHC. We want to decide whether we should restrict the data set or leave as it is with some control.

I think we have two options on this:

Option 1: Remove all non-supported elements from the profile. This may introduce strict boundary on the profile and loose re-usability.

Option 2: Use must support flag to indicate what is supported by NCDHC. If the source system supplies more data, then NCDHC will not remove them but will not process them or take any ownership of that additional data. They will remain as-is in the supplied resources. 







Resource: Observation

Serial Number


Resource Path

NCDHC Approach

Date and Decision

Members Present


Shall we make effective[x] as mandatory in the profile when there any value[X] provided?

in what situation effective[x] can not be provided (other than historical observations which we are not dealing with in NCDHC)?


Add Invariant to check the existence of effective[x] if the absentReason is not provided




Use of component or hasMember along with dataAbsentReason


Do not allow dataAbsentReason along with component and/or hasMember in the same Observation instance.




Use closed slice vs open slice in coding


NCDHC recommends to use closed slice to avoid ambiguous codes in the instance




What is recommended to use for Observation.category


NCDHC to use ‘procedure’ or ‘exam’ as category (as applicable)




There are some Observation profiles under NCDHC which points to just to record if the Procedure was performed or not.

The main objective of these types of Observations are to capture the Observation.interpretation and comments (if any)

The ValueSet includes the following values:

443938003 - Procedure carried out on subject

416237000 - Procedure not done

439495000 - Counselling declined



Proposal: Remove this valueset and implement the following changes

Observation.value[x] make it valueBoolean to allow true/false

move “Procedure not done” and “Counselling declined” as part of Observation.dataAbsentReason




Use of au-practitionerrole to record “Examiner” in Observation instead of current implementation where we are usingau-practitioner


Use of au-practitionerrole to record “Examiner” in Observation. This provide the option to record the Examiner and associated Organisation along with practitioner's role.




  • No labels