-
Notifications
You must be signed in to change notification settings - Fork 51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Inheritance of Resource, DomainResource, Element and BackboneElement #26
Comments
You are correct -- the current code in master does not reflect the properties of any of these base resources or elements (except for We don't yet have a plan, however, for support of |
Well, I make regular use of the language element, which is defined at the parent class level. I can do without the internal ID, which is the other main contribution, but language is a gotta-have for my use case. |
Support for the base DomainResource and Resource classes was added in PR #25, which has now been merged to master. So... language shouldn't be a problem anymore. Does that resolve your main concerns? |
That's great, thank you. What are the plans for implementing CodeSystem? |
I'm not entirely sure what you mean by "implementing CodeSystem" -- could you provide a few more details? CodeSystem isn't a resource, but the ValueSet resource defines a CodeSystem component for defining code systems inline. Is that what you're talking about? (If so, our model supports that already). |
CodeSystem is now a resource, actually: http://hl7-fhir.github.io/codesystem.html |
Oh. I see. This wasn't on my radar, as we've been focused on DSTU2. Right now, we remain focused on DSTU2, so I wouldn't expect to see support for CodeSystem until closer to DSTU3. That said, much of our code is generated from the FHIR tool chain, so it may be possible to rebase our code generation on a later version of the FHIR sources and generate out the latest (DSTU3) resources (assuming the tool chain itself hasn't changed a lot) -- but that would require forks of our fhir and fhir-golang-generator projects -- and maintaining those forks while we continue to work on the master branches. If this is something you're truly interested in, let me know and we can throw you a few pointers. |
I am, thank you. Might a different channel be better to chat about it? IRC? Email? Skype? |
In the XML Schema Resource, DomainResource, Element and BackboneElement are parent types of most of the data and resource types. In particular, they include fields like Language and Extension. These seem to be absent from the various classes, or am I missing something?
The text was updated successfully, but these errors were encountered: