ansforge / ansforge/psc-psi-api
Dénomination des champs/format JSON non conformes à celles utilisées pour l'API FHIR
- Dominant language
- No language data
- Stars
- 3
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
la dénomination des champs ne respecte pas la codification adoptée pour FHIR : [AS Practitioner Profile - Annuaire Santé v1.1.0](https://interop.esante.gouv.fr/ig/fhir/annuaire/StructureDefinition-as-practitioner.html) + [AS Person Profile - Annuaire Santé v1.1.0](https://interop.esante.gouv.fr/ig/fhir/annuaire/StructureDefinition-as-person.html). Et de manière générale, pourquoi l'API PSI n'est pas basée sur FHIR ???
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by comparing the API's JSON field names with the linked AS Practitioner Profile and AS Person Profile specifications. No source files or tests are named, and the issue also raises the broader question of basing the PSI API on FHIR; confirm the intended scope and document which fields or API design should change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- json
- Domain
- api, backend-api-design
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100