Ewout Kramer
Ewout Kramer
These properties list the properties of an instance, and are replaced by GetElementPairs() and IReadOnlyDictionary. We should remove them or rewrite these as (obsolete) extension methods, so they can be...
Both our FHIR and CQL SDK have a set of CQL datatypes, that are covering exactly the same ground. They were created for the same purpose, but, back then, by...
Although it sounds like we do, there might actually be a better way to get at the value. Consider: not every node has a value, since not every node is...
`ToXml(Base)` and `ToJson(Base)` still work via PocoElementNode, but should work via the more native route. This is in principle independent of the new direct implementation of ITypedElement, but in line...
As part of our effort to support "custom resources" through Pocos (and more specifically through the new DynamicResource/DynamicDataType), we will need a way to provide metadata about these resources so...
At this moment, POCOs only have properties for the elements defined in the FHIR specification. In many POCO serialization/deserialization frameworks, there is support for [overflow](https://learn.microsoft.com/en-us/dotnet/standard/serialization/system-text-json/handle-overflow), where "unknown" data can still...
Although we have our new stack of parsers available since SDK 4.0, we've been very careful to not cause incompatibilities by using them ourselves in the SDK. E.g. the `DirectorySource`...
I switched the parser in our validator demo to "Ostrich", so that we would get more errors reported from the validator (e.g. cardinality) instead from the parser. However, when I...