-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[ AUTO ] Model Tracker #171
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…3.yaml --target-version=3.0.0
Specs: rework and migration to AsyncAPI v3.0.0
romainfd
force-pushed
the
auto/model_tracker
branch
from
August 21, 2024 13:19
db11c4a
to
dc335c6
Compare
…amples folder before generating new ones
…amples-before-generating-new-ones Feature/Nettoyage des fichiers exemples .xml anciens avant l’étape de génération
…gement Feature/Correction de la gestion d'erreur dans json_schema2xsd
|
|
Quality Gate passedIssues Measures |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Long Run
This branch stays open over a long period of time to track a specific work state of the repo
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Basée sur https://github.com/ansforge/SAMU-Hub-Modeles/pull/171/files
Schémas
EMSI : conforme avec la norme ?
regex avec ^$
MISSION.ID en 1..1
MISSION.NAME en 1..1
MISSION.STATUS en 1..1
RESOURCE.ID en 1..1
RESOURCE.NAME en 1..1
RESOURCE.STATUS en 1..1
GEO-POS
regex avec ^$
resourceId : balise "id" avant + devient identifiant partagé + regex
position et coord en 1..n
GEO-REQ
resourceId : devient identifiant partagé + regex
GEO-RES
id → resourceId : devient identifiant partagé + regex
RC-EDA
regex avec ^$
obsDatime → datetime
RPIS
event → context
samuId → orgId
fileId → caseId
unit → service
actionsSMUR → procedure
regex avec ^$
RS-DR
regex avec ^$
RS-EDA-MAJ
regex avec ^$
Ajout regex CIM10
Correction regex medical note qui plantait sur des clientId à 4 blocs et non 3 (autorise 3 ou 4 maintenant comme les autres regex sur ça)
RS-EDA
Toutes les modifs du RS-EDA-MAJ
obsDatime → datetime
RS-RI
regex avec ^$
suppression du bloc de géoloc
RS-RR
regex avec ^$
ajout de la nomenclature de délai
RS-SR
regex avec ^$
ajout d'un "wrapper" state pour réutiliser le format des statuts avec le RS-RI
Nomenclatures
Nature de fait : décalage des doublons C02.14.**
EMSI RESOURCE.RTYPE.CLASS : doublon FAC/OPR/HSPFLD → deuxième converti en FAC/OPR/HSPFLD2
CONTACT canal : DEFIBRILLATEUR, corrigé en DEFIBRILLATEUR
Migration du sexe vers la nomenclature NOS
Ajout de la nomenclature du délai
Reprise TYPE MOYEN