Stream: implementers
Topic: Concept Resource
nicola (RIO/SS) (Nov 12 2016 at 09:31):
How about abstract Concept from CodeSystem into separate resource - this will be helpful to implement CodeSystem management using FHIR API. $lookup just turns into Concept/_search & /CodeSystem/<id>/Concept/_search (Search). Also with inline resources syntax - we could save backward compatibility with current version of FHIR API.
Grahame Grieve (Nov 13 2016 at 10:52):
we've talked about making Concept a separate resource to Code System. It would change $lookup, but it would complicate lots of other things, and it's outside our scope (managing code systems). So we've kept away from it
Grahame Grieve (Nov 13 2016 at 10:52):
don't follow the comment about inline resource syntax
nicola (RIO/SS) (Nov 13 2016 at 15:59):
@Grahame Grieve What kind of things will be complicated with separating Concept resource?
nicola (RIO/SS) (Nov 13 2016 at 16:02):
About inline - i mean you could describe code system as in current version { resourceType: 'CodeSystem', concept: [ collection of concepts] }, but collection of concept will be treated as inline resources and saved separately.
Last updated: Apr 12 2022 at 19:14 UTC
