You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It is likely that the FHIR specification for Value Sets will not be able to capture sufficient detail to cover the whole create-and-maintain life cycle.
An artefact will be produced that documents at a suitable level for team discussion (ie higher level than the detailed UML/API level) the capabilities of the ontoserver (ie according to the specification for a FHIR terminology) for holding
Value Set intensional definitions
Value Set expansions
Versioning information
Descriptive metadata
Metadata associated with a creation/maintenance cycle
The document will comment in broad terms where the main gaps appear to be that will probably require a second form of database
D.o.D.
A document has been created and is available to the team
The text was updated successfully, but these errors were encountered:
PaulChapmanPM
changed the title
Research and document for the team the capabilities (and limitations) of a FHIR terminology server (concretely Ontoserver) for storing valuesets
Research and document for the team the capabilities (and limitations) of a FHIR terminology server for storing valuesets
Dec 8, 2022
PaulChapmanPM
changed the title
Research and document for the team the capabilities (and limitations) of a FHIR terminology server for storing valuesets
Research and document for the team the capabilities (and limitations) of a FHIR terminology server for storing value sets
Dec 8, 2022
It is likely that the FHIR specification for Value Sets will not be able to capture sufficient detail to cover the whole create-and-maintain life cycle.
An artefact will be produced that documents at a suitable level for team discussion (ie higher level than the detailed UML/API level) the capabilities of the ontoserver (ie according to the specification for a FHIR terminology) for holding
The document will comment in broad terms where the main gaps appear to be that will probably require a second form of database
D.o.D.
The text was updated successfully, but these errors were encountered: