Lee Surprenant

This element is of type base64Binary and there is no spec-defined limit for this data type: https://hl7.org/fhir/datatypes.html#base64Binary Correspondingly, there is no enforced limit for this type in our fhir-model classes,...

This will be easier if we drop the db2 multi-tenant schema. But then, maybe we should just ditch the admin schema completely...

https://www.w3.org/TR/REC-xml/#AVNormalize has me agreeing this could be an issue. Based on my reading of that, an XML parser would parse ``` ``` to an attribute value of ``` XXX XXX...

I added a test at https://github.com/LinuxForHealth/FHIR/pull/3816/files#diff-8ec2e5b4061497aaf09998b194bb8e294ab785f38c512b5d64119ed4940e7463R23-R38 to demonstrate the root of the issue which has nothing to do with JSON and everything to do with XML.

I updated the demo env locally to use an old version of azurite (3.10.0). After this the fhir-server image was crashing during startup. I then updated the config to specify...

Potentialy a larger issue with our custom operation framework in general. We now support `beforeInvoke` and `afterInvoke` on the FHIRPersistenceInterceptor interface, but the NotificationService doesn't do anything when these are...

Keeping this scoped just to notification of $erase invocations.

Relates to (and may be fixed by) #3405

Today I am unable to reproduce this issue. Will need to keep an eye on it. I won't consider the issue addressed until we've added java 17 to our test...

I now see that #3683 does include some updates to the SchemaToolUsageGuide (number 2 in the description), its possible that this part is done (or at least started)