Stream: IG creation
Topic: Code System rendering
Brian Postlethwaite (Oct 03 2019 at 03:41):
Wondering if the Code System rendering in an IG should display the property values associated with codes?
Grahame Grieve (Oct 03 2019 at 05:51):
have you got an example?
Brian Postlethwaite (Oct 03 2019 at 06:47):
Something like this
<CodeSystem xmlns="http://hl7.org/fhir">
<id value="blah-address-type" />
<url value="http://fhir.telstrahealth.com/th-blah/CodeSystem/blah-address-type" />
<name value="AddressType" />
<status value="active" />
<content value="complete" />
<property>
<code value="Flag 2"/>
<description value="This indicates if the address is: A (Home Address) or P (Postal Address)"/>
<type value="code"/>
</property>
<property>
<code value="Flag 7"/>
<description value="This should contain a code for which program the name belongs to as follows: M (Medicare/generic), B , C "/>
<type value="code"/>
</property>
<concept>
<code value="PADMEDSTD" />
<display value="Medicare Standardised Postal Address" />
<!-- <definition value="This name was provided during import into the B Registry. It will be read only to GP systems" /> -->
<property>
<code value="Flag 2" />
<valueCode value="P"/>
</property>
<property>
<code value="Flag 7"/>
<valueCode value="M"/>
</property>
</concept>
...
Brian Postlethwaite (Oct 03 2019 at 06:49):
Would just expect an extra 2 columns with the table of codes being displayed with the value of that property in them.
Brian Postlethwaite (Oct 03 2019 at 06:49):
If there isn't happy to do the code change and submit a PR for it.
would just want to know if this is another format, or the default rendering
Brian Postlethwaite (Oct 03 2019 at 06:50):
@Michael Lawley would this be of use to you guys?
Michael Lawley (Oct 03 2019 at 20:47):
Some codesystems have lots of properties; it might be useful to have a mechanism to indicate to the IG tooling which properties are interesting / useful to display.
You'd also need to account for multi-values properties and ones like parent and child
Brian Postlethwaite (Oct 03 2019 at 20:58):
As it currently stands the IG doesn't show any of it to you outside the code system xml/json.
Brian Postlethwaite (Oct 03 2019 at 20:59):
Sounds like a new snippit for a PR to discuss then.
Brian Postlethwaite (Oct 03 2019 at 21:00):
@Michael Lawley can you point me at one with parents/children and another with lots of props?
(so I can test for my PR)
Michael Lawley (Oct 03 2019 at 21:51):
https://stu3.ontoserver.csiro.au/fhir/CodeSystem/LOINC-2.65
Michael Lawley (Oct 03 2019 at 21:51):
Although that CodeSystem doesn't actually enumerate the codes
Michael Lawley (Oct 03 2019 at 21:52):
And the same issue with SNOMED which has many properties
Grahame Grieve (Oct 03 2019 at 22:04):
I'm not going to be writing an IG presenter for snomed ct
Brian Postlethwaite (Oct 03 2019 at 22:19):
And as the expansion doesn't include the properties without doing a lookup afterwards, hard to define what to include in the documentation there too (if we wanted to)
Grahame Grieve (Oct 03 2019 at 22:23):
that I can handle - a parameters resource with the same id as the value set
Grahame Grieve (Oct 11 2019 at 18:55):
ok done, next release. To get the property to render you have the following choices:
- just tell me you want the property URL rendered always, and we can talk about it
- put a rendered value extension on the property definition
- register the url for the property in the json file using a code.system.property.list property which is an array of strings (or, for the new approach in the ig, using the parameter name codesystem-property)
Brian Postlethwaite (Oct 12 2019 at 09:28):
I'll take a look at the commit and give it a try
Brian Postlethwaite (Oct 12 2019 at 09:28):
Thanks.
Brian Postlethwaite (Oct 12 2019 at 09:32):
I'll give the codesystem-property trick a whirl.
Last updated: Apr 12 2022 at 19:14 UTC
