Stream: fmg
Topic: FMG e-vote
Anne Wizauer (Mar 03 2022 at 22:34):
Hi all! We are trying to handle a publication request via e-vote this week that I missed putting on the agenda. If we can get quorum by Tuesday morning, I can send to TSC e-vote next week.
https://confluence.hl7.org/display/FMG/FMG+e-Vote+2022-03-03
Lloyd McKenzie (Mar 03 2022 at 23:09):
The four information messages are due to a code system in UTG being marked as 'example' when they shouldn't be. A request to fix this has been submitted and at some point the information messages will go away. (Which is why they're not suppressed.)
The two errors about links not resolving will go away once this specification is published. They're absolute links to the base URL of the spec.
The remaining error is inherited from the core spec.
I've abstained, given that I wrote the guide - and if it'd been taken up on the call, I'd have been chairing and couldn't have voted :)
Lloyd McKenzie (Mar 05 2022 at 21:39):
Friendly poke soliciting votes... :)
David Hay (Mar 07 2022 at 07:16):
So the pub request is for hRex and QA report shows 4 information messages that are not indicative of issues with the IG - right?
John Moehrke (Mar 07 2022 at 13:57):
The info about IHE formatcode can be resolved by using the codesystem that IHE has chosen.
John Moehrke (Mar 07 2022 at 13:58):
The error if identifier.system is ''urn:ietf:rfc:3986'', then the identifier.value must be a full URI (e.g. start with a scheme) can also be cleared up by using a legitimate URL. Seems the value is holding narrative.
John Moehrke (Mar 07 2022 at 14:01):
The errors in parameters-member-match-in.json can be avoided by using example.com (example domain).
John Moehrke (Mar 07 2022 at 14:08):
indeed there is no #regular anchor on the page URL value 'http://hl7.org/fhir/us/davinci-hrex/StructureDefinition-hrex-consent.html#regular' does not resolve
Lloyd McKenzie (Mar 07 2022 at 19:39):
The URL can't resolve yet because there is no davinci-hrex spec published at that location. Once it's pushed, it'll be correct.
There's no mechanism to correct the URL on Consent because it's inherited from the base resource.
The format code being used is the one defined in THO. What's the status of getting THO to 'correct' it?
John Moehrke (Mar 07 2022 at 20:14):
The IHE defined codeSystem is well-enough-known for IGs to use. I use it in my IGs.
John Moehrke (Mar 07 2022 at 20:16):
the URL will not be fixed when hrex is published as that StructureDefiniton page, even on the CI-Build, doesn't have a #regular -- https://build.fhir.org/ig/HL7/davinci-ehrx/StructureDefinition-hrex-consent.html
Last updated: Apr 12 2022 at 19:14 UTC
