Details
-
Question
-
Resolution: Considered - Question answered
-
Highest
-
Shorthand (FHIR)
-
2.0.0
-
FHIR Infrastructure
-
Language Reference
-
3.2.3
-
Description
Will FSH 3.0.0 leave these types TU? Should this statement be removed in FSH 3.0.0, or changed as suggested? Or is FSH leaving them as TU until FHIR has a release that makes them normative?
Existing Wording:
FSH supports new FHIR R5 datatypes integer64 and CodeableReference on a trial use basis.
Proposed Wording:
FSH supports FHIR R5 datatypes integer64 and CodeableReference.
(Comment 26 - imported by: Ron G. Parker)
Attachments
Issue Links
- is voted on by
-
BALLOT-51958 Affirmative - Ron G. Parker : 2023-Sep-FHIR IG SHORTHAND R3 Norm
- Balloted
-
BALLOT-53852 Affirmative - Joan Harper : 2023-Sep-FHIR IG SHORTHAND R3 Norm
- Balloted
-
BALLOT-53919 Affirmative - Elliot Silver : 2023-Sep-FHIR IG SHORTHAND R3 Norm
- Balloted
-
BALLOT-53986 Affirmative - Shannon O'Connor : 2023-Sep-FHIR IG SHORTHAND R3 Norm
- Balloted
-
BALLOT-54053 Affirmative - Sheridan Cook : 2023-Sep-FHIR IG SHORTHAND R3 Norm
- Balloted