FHIR Chat · General Development Questions · cimpl

Stream: cimpl

Topic: General Development Questions

Kurt Allen (Jul 10 2019 at 21:36):

Hello @Chris Moesel
(I created a new topic for further development queries to keep the number of topics manageable...)

Do you have a planned release date for the ability to constrain strings (and integers)?

If that is not something you plan on doing soon, can you suggest how I can fix it inthemap file? I am trying to set the Composition.Section.Title property to a fixed value. I am including several entries derived from Composition.Section, which are all included as follows:

Entry: BreastRadiologyDocument
Parent: Composition
Section
includes PatientHistory 0..1
includes FindingsLeftBreast 0..1
...

Group: PatientHistory
Description: "Patient History"
Parent: Section
...

Group: FindingsLeftBreast
Description: "Findings for Left Breast"
Parent: Section
...

How do I fix (in the map file) the PatientHistory.Title to one value and the FindingsLeftBreast.Title to another?

Chris Moesel (Jul 12 2019 at 21:06):

Hi @Kurt Allen -- I apologize for the very delayed response. Unfortunately, I think you've found a hole in our mapping language. There doesn't currently seem to be a good way to fix a value on a specific slice in a profile -- from the mapping file. Of course, if the value is fixed in the model itself, it all works out -- but what you're trying to do is different (and we don't support fixing strings in the model right now anyway). Ack. That stinks.

Chris Moesel (Jul 12 2019 at 21:07):

Sorry... but I'll log it as an enhancement to consider for future versions.

Kurt Allen (Jul 15 2019 at 17:16):

Yo @Chris Moesel Thanks for the info, I will prob. just add a post processing step to add it into the structure definition resource manually before I compile the IG.

Chris Moesel (Jul 15 2019 at 17:18):

Thanks for the update, @Kurt Allen. That seems like a very reasonable approach -- I'm just sorry that you have to do it!

Kurt Allen (Jul 15 2019 at 17:27):

Hey @Chris Moesel No worries. I bill by the hour :-) Your tool(s) have saved me a lot of time, and I understand that this is still a work in progress. That's the exciting life of a development engineer, walking the fine edge :tada: .....

Kurt Allen (Jul 16 2019 at 15:21):

hello @Mark Kramer
Small typo in obf_lab.txt, line #17

Description: "A quantity with that requires a coded unit of measure."
I think you mean:
Description: "A quantity that requires a coded unit of measure."

Kurt Allen (Jul 18 2019 at 19:49):

Yo @Chris Moesel
I am getting a lot of warnings.
WARN shr: Using profile that is currently in the middle of processing: obf-Specimen. ERROR_CODE:13054

a) is this normal
b) is there any way I can turn them off/hide them?
Thanks

Chris Moesel (Jul 18 2019 at 19:52):

a) Yes, and so far this occurrence (using a profile that is currently in the middle of processing) has never actually caused a problem. I'm thinking of turning off the warning or demoting it to a debug-level log.
b) There isn't a way to turn off just a specific warning, but you can turn off all warnings by passing in the -l error flag into the CLI.

Kurt Allen (Jul 18 2019 at 19:54):

Yo @Chris Moesel
I updated to the latest spec, and found an interesting issue. In the previous version of shr-spec, Section contains an element named DomainResource. This was renamed to Resource in the current version. I didn't change the name in my section derived class nor in the mapping file, but it compiled with no errors. In essence I was overriding a value that didn't exist. Should this generate an error or at least a warning?

The following is one of my section overrides.
// Patient History Section
Group: PatientHistory
Parent: Section
Description: "Patient History Section"
Code = LOINC#34117-2 // is this correct code for section
DomainResource 0..*
DomainResource substitute Observation // Only Observations allowed in this section
Section 0..0 // Child sections not allowed in this section
SortOrder 0..0 // No defined sort order
FocalSubject 0..0 // Subject is always Composition.FocalSubject
// Title = "Patient History"

Best

Chris Moesel (Jul 18 2019 at 20:07):

Yo @Kurt Allen -- I agree, that seems like a bug that we should be detecting and flagging. This sort of thing worked in CIMPL5 (it would just create a new property on the subclass), so I wonder if this is a holdover that slipped through. Thanks for pointing it out.

Chris Moesel (Jul 18 2019 at 20:13):

Logged it here: https://standardhealthrecord.atlassian.net/browse/CIMPL-18

Kurt Allen (Jul 18 2019 at 20:33):

Yo @Chris Moesel back!
I live to find bugs (especially other peoples ) :-)
Thanks,

Kurt Allen (Jul 18 2019 at 21:19):

Hey @Chris Moesel and @Mark Kramer

In the IG output from CIMPLE, each .html file has a yellow background banner with the text "Publish Box goes here".

How do I override this to say something more clever...
Thanks in advance, K

Chris Moesel (Jul 18 2019 at 21:27):

The FHIR IG Publisher is supposed to populate that box for you. So technically, there's not much you are supposed to do. That said, it's driven off the package-list.json -- so I wonder if there is something about your package-list.json that prevents it from working correctly.

You should try updating your ig-breastRad-plist.json file (which eventually becomes package-list.json in the IG) so that it has another entry besides the CI build one. The non-CI entry should reflect what your ballot package will be. For an example, see our mCODE one here. Perhaps if you add that, the publish box will start working.

Kurt Allen (Jul 19 2019 at 14:42):

Thanks for the suggestion. I tried changing that and it still came up. Documentation suggests that this is controlled by the people who control whether the item is published or not, i.e. hl7. It is supposed to be "Publish Box goes here" until it is marked as published. Not sure who does that marking.

Kurt Allen (Jul 27 2019 at 01:16):

Hello @Chris Moesel
How do I get a .jpg file copied to the fhir ig pages directory. I added it to the CIMPL Pages dir (where the landing page lives), can you point me to the documentation or give me a heads up on what I have to do to get this copies to the fhir ig output\fhir\guide\pages dir?
thx,
Kurt A.

Chris Moesel (Jul 29 2019 at 16:01):

Hi @Kurt Allen, your JSON config file's implementationGuide -> indexContent needs to point to the folder where the index file and images are -- and the index file has to be named index.html. Looking at your source you currently have this in the config:

"indexContent": "Pages/BreastRad.html",

So the steps would be:

• Rename the BreastRad.html file to index.html
• Change the value of "indexContent" in the config from "Pages/BreastRad.html" to just "Pages"

Chris Moesel (Jul 29 2019 at 16:02):

This is documented in the CLI's README here: https://github.com/standardhealth/shr-cli#implementation-guide-configuration

Kurt Allen (Jul 29 2019 at 17:15):

@Chris Moesel - Thanks!!!!

Last updated: Apr 12 2022 at 19:14 UTC