Bugfix nl core dependency 4.0.x

[bramwesselo]

minor changes

added dependencies on nl-core and eu-base

[stevenvegt]

Good busy!

[bramwesselo]

On-hold: Momenteel nog in geprek met Pieter Edelman (NictiZ) om nl-core package te kunnen gebruiken.

[bramwesselo]

Kan w.m.b. nu gemerged worden

[stevenvegt]

Kun de urn urn:oid:2.16.840.1.113883.2.4.6.7 nog als een alias worden opgenomen?

Je verwijst op diverse plekken naar de NLCore profielen, maar die worden nergens gebruikt?

[rolandgroen]

I see that nictiz has released 0.12.0-beta.4, i'll check if that version also has the issue.

[rolandgroen]

From the changelog:

This beta release introduces the following changes:

ZIBFHIR-380: The dependency on FHIR in the package manifests is written as “4.0.1” instead of “4.0.x” as a workaround for a bug in the IG Publisher.
ZIBFHIR-366: Extra documentation has been added regarding the TreatmentDirective2 zib2020 R4 implementation. In addition, extra guidance has been added on the use if .provision.type`.

[bramwesselo]

From the changelog:

This beta release introduces the following changes:
ZIBFHIR-380: The dependency on FHIR in the package manifests is written as “4.0.1” instead of “4.0.x” as a workaround for a bug in the IG Publisher.
ZIBFHIR-366: Extra documentation has been added regarding the TreatmentDirective2 zib2020 R4 implementation. In addition, extra guidance has been added on the use if .provision.type`.

@rolandgroen Ik heb hiervoor een ticket bij Nictiz aangemaakt (waar ik zelf niet bij kan, maar ZIBFHIR-365 werd genoemd door Pieter Edelman)

[bramwesselo]

@rolandgroen: not only the ZIB-packages had issues, but also the FHIR IG Publisher (first it would be solved in version 2.0.17, but now it is finally solved in 2.0.19....)

[rolandgroen]

I see some (probably harmless) renaming of aliases that I not fully understand, but that seems fine.
The dependency bump is the most important part.