Canadian FHIR Baseline Profiles - Governance Stream Meeting - August 30th, 2-3pm EST

Hi folks,

For any proposed changes (cardinality, value sets, etc.) to the profiles, our process has been to submit the proposed changed to me (This email address is being protected from spambots. You need JavaScript enabled to view it.) using the excel template that's available from here on InfoCentral (look in the Documents tab). As soon as I receive those proposed changes, I post them to GitHub as 'issues' so the rest of the Community can review (and/or comment on) the proposed changes, prior to us updating (or not updating) the profiles.

-Mike

Hi Smita, I'm able to edit anything under BC Core project on Simplifier but I do not have such access rights on Canadian Core. At the same time it's not required, I'm fine with a single person consolidating all requests to change a profile.

I found Forge being too verbose for things that we are doing (e.g., defining extensions) and for that reason I'd prefer to edit directly in XML. Saying that, if core profiles are edited outside of the Canadian Core project, Simplifier applies its own constrains, for example, forcing me to create a package or failing to parse profiles. Just FYI.

Regards,
Shamil

Hi Shamil,

I am not sure whether there is any process in place who can edit the CA-Core profile or it’s open for anyone to edit.

There are two ways I know how to do it:

1. If you are fine with editing the XML /JSON definition of a profile, click on the update button on the top-right of Simplifier-profile page and select ‘update by editing the last version’. This will allow you to update the XML/JSON definition by adding the required attribute and hence your profile

2. Another way, which I personally prefer is using the ‘Forge’ Editor. You can download the editor by clicking the link here Download Forge . Step by Step instruction could be found here .

Thanks,
Smita

Question: how do we edit CA Core profiles on Simplifier?

For example, the extension definition needs to be suffixed with the data type
<element id="Patient.extension:birthsex.valueCode:valueCode">
as well as I'd like to propose some other extensions to be included.

Hi all,

For this Friday's Governance Stream meeting, the draft agenda will be to take stock of the outstanding questions that have arisen during prior discussions, as well as to start the conversation around what the approach would be down the road to feature draft core profiles in connectathon contexts (i.e. what are we 'testing'? What are the tools for gathering implementer feedback? any lessons learned in this space from the Community? etc.)

Fully recognizing that attendance may be lower due to the coming Labor Day Weekend, rest assured these conversations will be re-opened and continued at later dates as well.

Thank you!

-Mike