Stream: implementers
Topic: Patient Birth Place
Brian Postlethwaite (Dec 10 2017 at 05:06):
There is a standard extension for patient for birth place that is currently defined as a general extension, and as a result does not have a prefix of patient- on it.
This is the only current standard extension on patient that doesn't have the prefix.
Tracker 12974 requests to update the extension url. Refer to this page to see how out of place it looks.
http://build.fhir.org/patient-profiles.html
Patient is FMM5, thus seeking feedback from the community on this one.
Eric Haas (Dec 10 2017 at 05:44):
Half of Observation extensions don't start with Observation.:
- 1) I do not consider the extensions to be at the same FMM as the resource.
- 2) I don't think they need t o prefix with the resource especially if they can be used by other resources.
Brian Postlethwaite (Dec 10 2017 at 06:57):
I dont think birthPlace makes any sense not on patient?
René Spronk (Dec 10 2017 at 08:25):
Birth Place may make sense in any 'role resource' played by a person. Any resource which has Birth Date as part of its data could also have Birth Place, as these (under the 'code napoleon') assist to uniquely identify a person.
Brian Postlethwaite (Dec 10 2017 at 08:53):
Practically speaking does anyone store them for RelatedPerson or Practitioner?
Richard Townley-O'Neill (Dec 11 2017 at 01:21):
Some of the patient- extensions could be useful for person. Is birth place much different to birth time or nationality? Both of which are defined only for patient.
Lloyd McKenzie (Dec 11 2017 at 02:31):
That's a reasonable question - any Patient extension that might be something of interest as part of shared demographics should probably support Person too, even if there are no use-cases for it on Practitioner or RelatedPerson
Last updated: Apr 12 2022 at 19:14 UTC
