<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 26/07/19 10:19, Joseph Eisenberg
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAP_2vPhjYYnKUkjO=qsm5EBw8HwrEzJp=A0=exwD9sUr0k0cBA@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=utf-8">
<div>
<div dir="auto">There are still 2 problems with
healthcare:equipment:</div>
</div>
</blockquote>
And how many with health_amenity:type ?<br>
<blockquote type="cite"
cite="mid:CAP_2vPhjYYnKUkjO=qsm5EBw8HwrEzJp=A0=exwD9sUr0k0cBA@mail.gmail.com">
<div>
<div dir="auto"><br>
</div>
<div dir="auto">1) Healthcare:equipment is yet another new
feature key for database users to support, if tagged on its
own node at the location of the MRI. This requires Osm20gsql
users like the main Openstreetmap-Carto style to reload the
whole planet database before this key can be supported for
rendering, routing or search applications. Using amenity=MRI
or healthcare=MRI would be easier for current database users
to support and it’s shorter for mappers to type.</div>
</div>
</blockquote>
<br>
Not all users will want to support heath care. <br>
While it may be easy in the short term to place everything into the
amenity key or some other key this creates problems in the long
term. And, even if placed into these other keys, support may still
not be given. <br>
<br>
<blockquote type="cite"
cite="mid:CAP_2vPhjYYnKUkjO=qsm5EBw8HwrEzJp=A0=exwD9sUr0k0cBA@mail.gmail.com">
<div>
<div dir="auto">2) If you want to add this as a tag to an
amenity=hospital, then you can’t add both an MRI and a CT
scanner, for example, since a key can only have one value. <br>
</div>
</div>
</blockquote>
<br>
Not true, a few keys support multiple values e.g.
sport=soccer;rugby;baseball<br>
<br>
<blockquote type="cite"
cite="mid:CAP_2vPhjYYnKUkjO=qsm5EBw8HwrEzJp=A0=exwD9sUr0k0cBA@mail.gmail.com">
<div>
<div dir="auto"><br>
</div>
<div dir="auto">So in that case you still need MRI=yes as an
addition key to tag on an existing facility. I suspect this
tagging will be more common than mapping the MRI separately,
and it certainly will be more common for ultrasounds, which
are on wheels (casters) usually and can move around the
hospital. <br>
</div>
</div>
</blockquote>
<br>
In the first instance I think you are correct in that this will be
popular as a sub tag under a hospital (or other =feature). <br>
And I think most renders will ignore these sub tags of whatever
method. <br>
<br>
I would think portable equipment would not be tagged. Much like
cars. <br>
Doctors, nurses and portable equipment can be transported in. And
can be changed fairly quickly, not something that OSM handles well.
<br>
An MRI is not so easy to transport and get working. <br>
<br>
<br>
<blockquote type="cite"
cite="mid:CAP_2vPhjYYnKUkjO=qsm5EBw8HwrEzJp=A0=exwD9sUr0k0cBA@mail.gmail.com">
<div dir="auto"><br>
</div>
<div dir="auto">Joseph</div>
<div><br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Fri, Jul 26, 2019 at 4:01
AM Mhairi O'Hara <<a
href="mailto:mhairi.ohara@hotosm.org"
moz-do-not-send="true">mhairi.ohara@hotosm.org</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">
<div>Hello everyone!</div>
<div><br>
</div>
<div>I completely agree with Warin that the <b>health_amenity:type</b>
tag is pretty confusing as to what its referring to. I
was trying to stay in line with what was proposed
previously, but in retrospect it would be better to move
away from previous efforts and vote in a tag that is
straight forward and easy to understand (says what it
is).</div>
<div><br>
</div>
<div>The main aim for the tag is to encapsulate that its
related to health equipment, so how about <b>healthcare:equipment</b>?</div>
<div><br>
</div>
<div>Kind regards,</div>
<div><br>
</div>
<div>Mhairi</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Sun, Jul 14, 2019 at
4:43 PM Warin <<a href="mailto:61sundowner@gmail.com"
target="_blank" moz-do-not-send="true">61sundowner@gmail.com</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF">
<div
class="m_2253964052862820198gmail-m_4242831532282797205moz-cite-prefix">This
is about the equipment available? <br>
<br>
Using the principle of 'say what it is' ...<br>
<br>
medical_equipment=MRI ??? Assuming the tag is for
equipment. <br>
<br>
Calling the key health_amenity:type "in use" is a
stretch - 40 uses .. and most of these are for first
aid kits!<br>
The next most popular is "scales".<br>
Fist aid kits have the tag emergency=first_aid_kit
... which is more popular (170) despite it being a
"draft". <br>
<br>
No, I don't think is is "in use" nor has it been
used in a sensible way. Probably because "type" can
mean anything. <br>
<br>
health_facility:type has the same problem, despite
being more popular, uses are for <br>
dispensary<br>
office<br>
clinic<br>
hospital <br>
etc<br>
<br>
<br>
On 14/07/19 23:18, François Lacombe wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div>Hi Mark,<br>
</div>
<div><br>
</div>
<div>I agree with your choice to specifiy which
service are available in a given facility.</div>
<div>This doesn't require to add :type in the name
of the key. Such suffixe don't bring any
information.</div>
<div>Your proposal would be way better if you use
health_amenit=MRI at least instead</div>
<div><br>
</div>
<div>All the best</div>
<div><br>
</div>
<div>François<br>
</div>
<div><br>
</div>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">Le jeu. 11
juil. 2019 à 21:10, Mark Herringer <<a
href="mailto:mark@healthsites.io"
target="_blank" moz-do-not-send="true">mark@healthsites.io</a>>
a écrit :<br>
</div>
<blockquote class="gmail_quote"
style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<div dir="ltr">The intention of the <span
class="m_2253964052862820198gmail-m_4242831532282797205gmail-m_7672916700881543143gmail-il">tag</span> is
to specify physical equipment
(health_amenity:type=MRI) and should be used
in conjunction with amenity=clinic to show
that the health facility contains that
specialised equipment. This will enable
mappers say that "this clinic contains an
MRI"<br>
</div>
<div hspace="streak-pt-mark"
style="max-height:1px"><img alt=""
style="width:0px;max-height:0px;overflow:hidden"
src="https://mailfoogae.appspot.com/t?sender=abWFya0BoZWFsdGhzaXRlcy5pbw%3D%3D&type=zerocontent&guid=ebf4513e-98fb-4587-a615-2310e3766d53"
moz-do-not-send="true"><font
color="#ffffff" size="1">ᐧ</font></div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Thu, 20
Jun 2019 at 08:15, Joseph Eisenberg <<a
href="mailto:joseph.eisenberg@gmail.com"
target="_blank" moz-do-not-send="true">joseph.eisenberg@gmail.com</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote"
style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">4)
health_amenity:type<br>
<br>
I think the key "healthcare" should be
used instead of the new key<br>
health_amenity:type". If it's necessary to
tag an MRI facility<br>
separately, then create a tag like
"healthcare=mri".<br>
<br>
However, it may be more useful to use a
tag like "mri=yes" on the<br>
main amenity=hospital or the radiology
department within the medical<br>
centre - this tag would let mappers say
that "this hospital contains<br>
an MRI" without requiring mappers to
precisely locate the MRI<br>
equipment within the building. This would
also make it easier for<br>
database users: they can just check for
"amenity=hospital" + "mri=yes"<br>
rather than doing a spacial query to find
MRI nodes within or near an<br>
amenity=hospital feature<br>
<br>
<br>
On 6/20/19, Mhairi O'Hara <<a
href="mailto:mhairi.ohara@hotosm.org"
target="_blank" moz-do-not-send="true">mhairi.ohara@hotosm.org</a>>
wrote:<br>
> Hello Tagging Mailing List,<br>
><br>
> We would like to bring your attention
and comments on the proposal for the<br>
> staff_count:doctors and
staff_count:nurses tags, which helps
identify the<br>
> number of doctors and nurses at a
given health facility [1][2]. The<br>
> operational_status tag, which has
been proposed before and I would like to<br>
> highlight again, as this is used to
document an observation of the current<br>
> functional status of a mapped feature
(i.e. health facility) [3]. The<br>
> health_amenity:type tag is also being
proposed, as this indicates what type<br>
> of speciality medical equipment is
available at the health facility [4] and<br>
> the final tag is insurance:health
which describes the type of health<br>
> insurance accepted at a health
facility [5].<br>
><br>
> Some of these are already in use but
have never been formally accepted, or<br>
> properly described as to how they
should be applied, which we would like to<br>
> try and achieve if possible for the
Healthsites.io project. Please take a<br>
> look at the proposal pages on the OSM
Wiki, as well as the Global<br>
> Healthsites Mapping Project page [2]
which is at the core of the recent<br>
> work focused on creating a health
facility data model. We look forward to<br>
> discussing these proposals on the
respective Wiki discussion pages.<br>
><br>
> Kind regards,<br>
><br>
> Mhairi<br>
><br>
> [1]<br>
> <a
href="https://wiki.openstreetmap.org/wiki/Proposed_features/Tag:staff_count:doctors"
rel="noreferrer" target="_blank"
moz-do-not-send="true">https://wiki.openstreetmap.org/wiki/Proposed_features/Tag:staff_count:doctors</a><br>
> [2]<br>
> <a
href="https://wiki.openstreetmap.org/wiki/Proposed_features/Tag:staff_count:nurses"
rel="noreferrer" target="_blank"
moz-do-not-send="true">https://wiki.openstreetmap.org/wiki/Proposed_features/Tag:staff_count:nurses</a><br>
> [3]<br>
> <a
href="https://wiki.openstreetmap.org/wiki/Proposed_features/Tag:operational_status"
rel="noreferrer" target="_blank"
moz-do-not-send="true">https://wiki.openstreetmap.org/wiki/Proposed_features/Tag:operational_status</a><br>
> [4]<br>
> <a
href="https://wiki.openstreetmap.org/wiki/Proposed_features/Tag:health_amenity:type"
rel="noreferrer" target="_blank"
moz-do-not-send="true">https://wiki.openstreetmap.org/wiki/Proposed_features/Tag:health_amenity:type</a><br>
> [5]<br>
> <a
href="https://wiki.openstreetmap.org/wiki/Proposed_features/Tag:insurance:health"
rel="noreferrer" target="_blank"
moz-do-not-send="true">https://wiki.openstreetmap.org/wiki/Proposed_features/Tag:insurance:health</a><br>
> [6]<br>
> <a
href="https://wiki.openstreetmap.org/wiki/Global_Healthsites_Mapping_Project#Tag_Proposal"
rel="noreferrer" target="_blank"
moz-do-not-send="true">https://wiki.openstreetmap.org/wiki/Global_Healthsites_Mapping_Project#Tag_Proposal</a><br>
><br>
><br>
</blockquote>
</div>
</blockquote>
</div>
</div>
</blockquote>
</div>
</blockquote>
</div>
</blockquote>
</div>
</div>
</blockquote>
<br>
</body>
</html>