Reputation: 4675
Resolving codings like currency symbols (e.g. urn:iso:std:iso:4217
) requires that HAPI have access to the Internet (in order to contact tx.fhir.org
), which means that these codings cannot be validated when working completely offline, as is often necessary in the health care system. For Firely the situation is pretty much the same, as regards offline use.
Furthermore, many specifications for German health care are still incomplete and are missing some value sets.
That is why I decided to work around both problems by constructing conformance resource stubs for the value sets in question. For example, for the foreseeable future only one the code EUR
will have to be validated against urn:iso:std:iso:4217
, and the missing value sets for electronic prescriptions are similarly small.
How would one go about constructing a fake value set resource for e.g. the EUR
code? How should the fake resource be constructed in order to work well with both the HAPI and Firely validators?
Upvotes: 0
Views: 197
Reputation: 6803
You don't need a fake value set resource, you can simply put a pre-constructed expansion in your value set. If terminology services are unavailable, the validator will use the expansion already present in the value set.
Upvotes: 0