profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/jkiddo/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.
Jens Kristian Villadsen jkiddo @trifork

FelixGail/gplaymusic 59

A Google Play Music API in Java

botunge/hapi-fhir-forge-profile-converter 4

A Converter which converts Forge Fhir (http://fhir.furore.com/forge) profiles to Hapi Fhir Resources

jkiddo/ccow 3

A Java HL7 HTTP Binding Compliant CCOW implementation with web socket extensions

jkiddo/cda-gen 3

Automated generation of CDA classes for Java

ehn-dcc-development/hcert-java 1

Java version of the protocol

jkiddo/AirPlayAuth 0

Since tvOS 10.2 AppleTV is enforcing the "Device verification" for AirPlay, which could be manually enabled/disabled before. This library allows to pair with an AppleTV and can be used in any app supporting streaming/casting to an AppleTV.

issue commenthl7dk/KL-dk

Issues with whitespace using SUSHI 2.0

@Kirstinerosenbeck -- in the case of this IG, the issue is actually that you have some of the keywords indented. This sets the baseline indent level for the rules that follow, but the rules are indented less than the keywords (resulting in a "negative" indent level on the rules).

For example, these keywords are indented but probably shouldn't be: https://github.com/hl7dk/KL-dk/blob/master/input/fsh/KLCommonCareSocialServiceRequest.fsh#L51-L55

These keywords should also be fully left-aligned: https://github.com/hl7dk/KL-dk/blob/master/input/fsh/KLCommonValuesets.fsh#L859-L861

cmoesel

comment created time in 12 hours

push eventhl7dk/kl-ffb-messaging

Torben M. Hagensen

commit sha d4a10fab8412919b72aaad956e7506ef5b37cdc3

Added conditions, intervention and goals

view details

push time in 16 hours

push eventhl7dk/KL-dk-tools

Kirstine Rosenbeck Gøeg

commit sha 83f659a7366a02ae7cdaeade17e757c6db04a13c

patient identifiers added to ensure conformance with dk-core

view details

push time in 18 hours

issue closedhl7dk/KL-dk

Issues with whitespace using SUSHI 2.0

Background: SUSHI 2.0 implements several major features that will be balloted as part of FHIR Shorthand (FSH) STU2. One such feature, indented rules, interprets whitespace before rule markers (*) as an indicator of path context. Prior to SUSHI 2.0 and FSH STU2, whitespace before rule markers was insignificant.

Problem: This project contains FSH rules that have whitespace before the rule marker (*) and/or FSH keywords (e.g., Profile:, Parent:, etc.) that have whitespace before the first character. When SUSHI 2.0 processes these definitions, it attempts to determine path context from the whitespace, which then causes errors in the project output. If your project uses the HL7 IG Autobuild, auto builds will fail after SUSHI 2.0.0 comes out of beta.

Preferred Solution: The preferred way to fix this problem is to update your FSH definitions so that the keywords and rules all start on the first column of each line. This means removing all whitespace before keywords and * rule markers. This does not require any changes to the actual rule text; only the whitespace before the *. You can test your fixes by installing the latest SUSHI 2.0 beta via the following command: npm install -g fsh-sushi@beta.

Alternate Solution: If it is not feasible to make these changes in a timely manner, you can "lock in" the version of SUSHI that the IG Publisher uses by creating or updating a fsh.ini file at the root of your project. For example, the following fsh.ini file would tell the IG Publisher to always use SUSHI 1.3.2, even after SUSHI 2.0.0 is released:

[FSH]
sushi-version=1.3.2

Timeline: In order to avoid being affected by the official SUSHI 2.0.0 release, we recommend you implement one of the above solutions by July 6, 2021.

More Information / Questions: For more information about SUSHI 2.0, you can read the SUSHI 2.0.0 Beta 1 Release Notes. If you have questions, you can reach out to the SUSHI team via the #shorthand stream on Zulip or by logging an issue on SUSHI.

closed time in 19 hours

cmoesel

issue commenthl7dk/KL-dk

Issues with whitespace using SUSHI 2.0

I have checked that the SUSHI 2.0.0 update will not create problems in this project. The indents before * only occurs in comments.

cmoesel

comment created time in 19 hours

startedardera/flutter-pi

started time in a day

release Konloch/bytecode-viewer

v2.10.10

released time in a day

push eventhl7dk/KL-dk

Kirstine Rosenbeck Gøeg

commit sha 24da807c93a52aa52432c52558ba787407dd673b

corrected errors to package-list.json

view details

push time in 2 days

push eventhl7dk/kl-gateway

Torben M. Hagensen

commit sha a2fc367a4513672f737c5c39b750be8cf7953fca

Added missing inline usage

view details

push time in 2 days

release home-assistant/core

2021.6.6

released time in 2 days

startedkrystophv/mudletMAR

started time in 2 days

issue openedhapifhir/hapi-fhir-jpaserver-starter

"Cannot execute UPDATE in a read-only transaction" using Postgres with :latest (c24012514b4f)

Attempting to view data in the JPA server's web frontend using a Postgres backend with the :latest docker image returns an error. This issue does not occur in v5.4.1. Server error log appears in screenshot.

screenshot_from_2021-06-18_14-20-35

created time in 4 days

push eventhl7dk/KL-dk

Kirstine Rosenbeck Gøeg

commit sha 8912fccf511f63663fbb5274e178ff34f08ea7c4

package-list.json corrections

view details

push time in 5 days

push eventhl7dk/KL-dk

Kirstine Rosenbeck Gøeg

commit sha 322f14444e03fe73067c73eb6bcce6c75eb21c1e

Added descriptions to the condition change examples

view details

push time in 5 days

startedlukaslueg/macro_railroad

started time in 5 days

push eventejurgensen/pair_ap

ejurgensen

commit sha d955c447dac0545803dee9c90312c9d42310e9b1

Silence compiler warning with -O3

view details

push time in 5 days

issue openedhl7dk/KL-dk

Issues with whitespace using SUSHI 2.0

Background: SUSHI 2.0 implements several major features that will be balloted as part of FHIR Shorthand (FSH) STU2. One such feature, indented rules, interprets whitespace before rule markers (*) as an indicator of path context. Prior to SUSHI 2.0 and FSH STU2, whitespace before rule markers was insignificant.

Problem: This project contains FSH rules that have whitespace before the rule marker (*) and/or FSH keywords (e.g., Profile:, Parent:, etc.) that have whitespace before the first character. When SUSHI 2.0 processes these definitions, it attempts to determine path context from the whitespace, which then causes errors in the project output. If your project uses the HL7 IG Autobuild, auto builds will fail after SUSHI 2.0.0 comes out of beta.

Preferred Solution: The preferred way to fix this problem is to update your FSH definitions so that the keywords and rules all start on the first column of each line. This means removing all whitespace before keywords and * rule markers. This does not require any changes to the actual rule text; only the whitespace before the *. You can test your fixes by installing the latest SUSHI 2.0 beta via the following command: npm install -g fsh-sushi@beta.

Alternate Solution: If it is not feasible to make these changes in a timely manner, you can "lock in" the version of SUSHI that the IG Publisher uses by creating or updating a fsh.ini file at the root of your project. For example, the following fsh.ini file would tell the IG Publisher to always use SUSHI 1.3.2, even after SUSHI 2.0.0 is released:

[FSH]
sushi-version=1.3.2

Timeline: In order to avoid being affected by the official SUSHI 2.0.0 release, we recommend you implement one of the above solutions by July 6, 2021.

More Information / Questions: For more information about SUSHI 2.0, you can read the SUSHI 2.0.0 Beta 1 Release Notes. If you have questions, you can reach out to the SUSHI team via the #shorthand stream on Zulip or by logging an issue on SUSHI.

created time in 5 days

push eventhl7dk/KL-dk

Kirstine Rosenbeck Gøeg

commit sha 70562cdc6d89cca45e4a12c21517949aec02194a

Supressed warnings file added

view details

Kirstine Rosenbeck Gøeg

commit sha 5920115b4088262ccddb2b1f3dae4be4c3f05e14

Supressed warnings file added

view details

push time in 6 days

push eventhl7dk/KL-dk

Kirstine Rosenbeck Gøeg

commit sha c055c221285b74aa601772d8d86bb0854855c0f3

New versions of FSIII and FFB documents added

view details

push time in 6 days

issue commenthapifhir/hapi-fhir-jpaserver-starter

JPA server does not start with MDM enabled

Hello I have been facing the same issue while enabling the MDM configurations in application.yaml file. Can someone please guide me how to resolve this issue? Am i missing out some dependencies.

ERROR DETAILS:

Result :

Invalid bean definition with name 'mdmRuleValidator' defined in ca.uhn.fhir.jpa.mdm.config.MdmSubmitterConfig: Cannot register bean definition [Root bean: class [null]; scope=; abstract=false; lazyInit=null; autowireMode=3; dependencyCheck=0; autowireCandidate=true; primary=false; factoryBeanName=ca.uhn.fhir.jpa.mdm.config.MdmSubmitterConfig; factoryMethodName=mdmRuleValidator; initMethodName=null; destroyMethodName=(inferred); defined in ca.uhn.fhir.jpa.mdm.config.MdmSubmitterConfig] for bean 'mdmRuleValidator': There is already [Root bean: class [null]; scope=; abstract=false; lazyInit=null; autowireMode=3; dependencyCheck=0; autowireCandidate=true; primary=false; factoryBeanName=ca.uhn.fhir.jpa.mdm.config.MdmConsumerConfig; factoryMethodName=mdmRuleValidator; initMethodName=null; destroyMethodName=(inferred); defined in ca.uhn.fhir.jpa.mdm.config.MdmConsumerConfig] bound.

_

tgorton617

comment created time in 6 days

release home-assistant/core

2021.6.5

released time in 7 days

release hapifhir/hapi-fhir

v5.4.1

released time in 7 days

push eventhl7dk/KL-dk

Kirstine Rosenbeck Gøeg

commit sha 39f35990fb02b70312bb3af74b2e30b6161b1981

isModifierReason added to Condition

view details

push time in 8 days

push eventhl7dk/KL-dk

Kirstine Rosenbeck Gøeg

commit sha 3dc94efb94d0ab01a4c6eef4f7722c9de8e306df

updated all pdf-documents, small change i Condition summary

view details

push time in 8 days

push eventhl7dk/KL-dk

Kirstine Rosenbeck Gøeg

commit sha aa4db9a838d3cef2a53f62762ff55f93e0215e13

updated all pdf-documents, small change i Condition summary

view details

push time in 8 days

push eventhapifhir/hapi-fhir-jpaserver-starter

Octavian Ianculescu

commit sha f52041b8c64e3fba3963c79f86dcf95da2a4cf4c

Mysql docker setup - forcing mysql identifiers (database, table, triggers) naming to lowercase and name comparison to caseinsensitive, so hibernate queries can work even when referencing upper cased table names

view details

James Agnew

commit sha 131cb12111d28b0d39b540cc4e7fab1c7c38b983

Merge pull request #243 from mail4taz/patch-mysql-persistent-storage mysql docker setup patch

view details

push time in 8 days

PR merged hapifhir/hapi-fhir-jpaserver-starter

mysql docker setup patch

Mysql docker setup - forcing mysql identifiers (database, table, triggers) naming to lowercase and name comparison to caseinsensitive, so hibernate queries can work even when referencing upper cased table names

+6 -1

0 comment

2 changed files

mail4taz

pr closed time in 8 days

startedchriskiehl/Gooey

started time in 8 days

created repositorytmh-mjolner/history-issue

created time in 8 days