Faites-nous part de vos impressions sur le Serveur terminologique, et aidez-nous à améliorer nos services! Vous avez jusqu’au 3 décembre 2024 pour répondre au sondage. Votre avis nous intéresse! En savoir plus >

Partager :

file Baseline Canadian FHIR Profiles - Entities Stream Calls

  • Messages : 132
il y a 4 ans 11 mois #5578 par Lloyd Mckenzie
Réponse de Lloyd Mckenzie sur le sujet Canadian Postal Code format
Forcing client systems to write code that take a complete Canadian postal code and render it in a standardized way is certainly possible. Systems will still need to convey partial postal codes, erroneous postal codes and postal codes for non-Canadian addresses. So we can't impose this as a general constraint. Systems need to be able to expose the data they have. Where automated transformation to align with a standard is possible, we can demand that be done. However, we should *only* demand that be done if we believe that the benefit is worth the cost of imposing that code on all client systems. (Note that servers could easily transform the data on consumption if they wished.)

Connexion ou Créer un compte pour participer à la conversation.

  • Messages : 68
il y a 4 ans 11 mois #5577 par Shamil Nizamov
Réponse de Shamil Nizamov sur le sujet Canadian Postal Code format
One of the questions we discussed on the Entity sub-stream is the formatting of the Canadian postal code.

What I've found so far is this - "Postal Code – Should be printed in uppercase and placed two spaces to the right of the Province or Territory, with one space between the first three and the last three characters. A hyphen should not be used (ex. of unacceptable format: T0L-1K0)." (www.canadapost.ca/tools/pg/manual/PGaddress-e.asp?ecid=murl10006450)

We decided not to overload the Address.postalCode component with the Regex extension but rather provide a textual description as above, which applies to Canadian postal codes only, allowing to provide other (e.g. US ZIP number).

Any concerns or ideas about that?

Connexion ou Créer un compte pour participer à la conversation.

  • Messages : 68
il y a 4 ans 11 mois #5525 par Shamil Nizamov
Results of the first call (Nov 25):
* Issue #37 accepted and closed;
* Ethnicity extension value set update ( Issue #5 ) - tgateway.infoway-inforoute.ca/singlesubset.html?id=2.16.840.1.113883.2.20.3.208&versionid=20190930
* Patient profile IG publication process discussion.

Connexion ou Créer un compte pour participer à la conversation.

  • Messages : 68
il y a 4 ans 11 mois #5524 par Shamil Nizamov
You are welcome to join the Zoom calls of the Baseline Canadian FHIR Profiles - Entities Stream.

We are meeting on Mondays at 2-3pm EST, starting on November 25.

We are going to start working on the Patient profile first, and then move to Practitioner, PractitionerRole, Organization and Location profiles.

Connexion ou Créer un compte pour participer à la conversation.

Logo d'InfoCentral

La santé numérique à votre service

 

Transformer les soins de santé au Canada grâce aux technologies de l'information sur la santé.