Skip to content
This repository has been archived by the owner on Oct 8, 2024. It is now read-only.

Extensions as First-Class Fields #11

Open
niquola opened this issue Jan 13, 2019 · 2 comments
Open

Extensions as First-Class Fields #11

niquola opened this issue Jan 13, 2019 · 2 comments

Comments

@niquola
Copy link
Member

niquola commented Jan 13, 2019

We need clarification what is First-Class Fields

In spec:

resourceType: Patient
gender: ...
extension:
 - url: ...race
    valueCoding: 
        code: <code>
        system: <sys>

# this is in example
resourceType: Patient
gender: ...
race:
   value:
      Coding: 
         code: <code>
         system: <sys>

# this is how i see FCE
resourceType: Patient
gender: ...
race: 
   code: <code>
   system: <sys>

@niquola
Copy link
Member Author

niquola commented Jan 13, 2019

And we need example of nested extensions in spec.

We can use real one - https://www.hl7.org/fhir/us/core/StructureDefinition-us-core-race.html - to illustrate

@rbrush
Copy link
Collaborator

rbrush commented Jan 18, 2019

Yes, it should be race.code and race.system as you mentioned. I'm about to travel for a couple days but will put together a PR the spec to fix when I get back.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants