Stream: committers
Topic: CG committer : RE proband patient example
Eric Haas (Jan 23 2017 at 17:54):
FYI We are moving the us-races and us-ethnicity extension out of the fhir spec so the externsions in the 'proband' patient example have been commented out since the build cannot recognize the extension url.
Lloyd McKenzie (Jan 23 2017 at 18:03):
Realistically, in the CG profile, race and ethnicity information should probably be captured as observations rather than using the demographic extensions. What codes are relevant will be different and the context is different - demographics is "how the patient sees themselves" and is often cultural. Genomics cares more about ancestry than self-identification.
Grahame Grieve (Feb 06 2017 at 02:34):
we can restore these extensions specifically, and tell the build about them. @Lloyd McKenzie comment is more interesting - my impression is that you'll get demographics fields first, so including them in the examples with a comment about the limited usefulness of the data would be good
Lloyd McKenzie (Feb 06 2017 at 02:50):
@Grahame Grieve This issue here is that a realm-independent profile shouldn't be pointing to US realm extensions. We actually don't want the US realm extensions showing up in the core build - they were moved out deliberately.
Grahame Grieve (Feb 06 2017 at 02:53):
I disagree with this. We moved the definitions out deliberately, for good reason. But that doesn't mean that the core spec shouldn't mention them. And we can speciifcally mention them in examples when we mention them. And the US core extension for demographics are a FAQ enough that we should mention them to point people to the right place
Eric Haas (Feb 06 2017 at 03:11):
So I originally had a line in the introduction text to the extensions.html saying here is where you can find the us extensions and assumed this would be superseded by the registry link whenever that is ready. I also had a an exaample and a section in the profiles that pointed to them but since the links were broken I took them out. I would prefer to keep an example but I tend to agree with Lloyd that this muddies the waters. Would like to strike a balance. When is the extension registy going to be live.
Grahame Grieve (Feb 06 2017 at 03:35):
well, the us-sore spec exists ,and has a place, and that is the place for this reference
Grahame Grieve (Feb 06 2017 at 03:35):
not sure on ETA for registry.fhir.org
Lloyd McKenzie (Feb 06 2017 at 04:45):
@Grahame Grieve This isn't about just the example, it's also about the profile. They used to be part of the profile, but they can't be anymore because the profile is universal. The example should be updated to align with the profile.
Grahame Grieve (Feb 06 2017 at 06:36):
how does it not align with the profiel?
Eric Haas (Feb 06 2017 at 06:52):
To clarify there were 2 examples in the build using US-Core extensions:
- A example specifically made to demo all the us-core extensions. That now exists in the the US-Core profile
- Proband example - a CG workgroup product. I had hoped they would have picked up this stream so I don't have to chase them down. I agree with Lloyd re administrative vs tracing ancestry. Slippery slope that I think is gong to be hard to stop.
Lloyd McKenzie (Feb 06 2017 at 14:04):
The profile uses Observation to convey relevant information. So the example should do the same.
Lloyd McKenzie (Feb 06 2017 at 14:05):
@Gil Alterovitz ?
Last updated: Apr 12 2022 at 19:14 UTC
