Skip to content

Releases: skylight-hq/FHIR-Converter

v7.0-skylight-16

12 Dec 17:21
ce1d320
Compare
Choose a tag to compare

add period to address

v7.0-skylight-15

09 Dec 18:03
4455ff7
Compare
Choose a tag to compare

Add eCR encounterParticipants to the fhir Encounter resource's participant field.

Reduced the number of templates by combining the individual participant and reponsible participant into one with type and time variables.

Now take the @value attribute of an object passed to Period and map that to the start output.

v7.0-skylight-14

04 Dec 18:08
2e2b667
Compare
Choose a tag to compare

Convert marital status and religious affiliation when available on the eCR

v7.0-skylight-13

25 Nov 18:33
8f3f618
Compare
Choose a tag to compare

Get all procedure codes

v7.0-skylight-12

21 Nov 18:54
0c16b80
Compare
Choose a tag to compare

Add mapping of pager as use code to system for eCR

v7.0-skylight-11

20 Nov 19:23
37b6d27
Compare
Choose a tag to compare

More work to get dotnet publish to work

v7.0-skylight-10

20 Nov 13:20
66f0bbd
Compare
Choose a tag to compare

Enable standalone binary publishing

v7.0-skylight-9

15 Nov 19:12
b6e0055
Compare
Choose a tag to compare

Return all emergency contacts in the eCR conversion

v7.0-skylight-8

15 Nov 16:23
e9d4146
Compare
Choose a tag to compare

Always use inner text for conversion of note/comment type fields

v7.0-skylight-7

14 Nov 17:54
15f380d
Compare
Choose a tag to compare
  • Allow social history entries that have a value which is coded with nullFlavor = UNK to still be converted as long as they have original text in their value field
  • Make sure that all converted social history observations are referenced in the social history section (and not more than did get converted)
  • Abstract out the logic of whether to convert a social history observation to the Util/IsSocialHistoryObservation template.
  • This template contains boolean logic to figure out if we should convert it or not then renders the result at the end. We can then capture this result when including the template in another template and use its value to simplify/dry out the code there
  • Use case/when to dry out a lot of repeated template ID-ing (and also add the check to look at the first as sometimes this had more than one thing and then the old logic just wasn't hitting 😬 )
  • Remove the extra special casing for SOCIALOBS in the social history _entry.liquid and just make it a normal special case as it wasn't needed and was causing weird merged objects because we were also converting it in the regular way.
  • Create a utility template for handling value[x] fhir mappings and use it in a lot of places