-
Type:
Change Request
-
Resolution: Persuasive
-
Priority:
Medium
-
FHIR Core (FHIR)
-
DSTU1 [deprecated]
-
Modeling & Methodology [deprecated]
-
Datatypes
-
1.18.0.3
-
-
Eric Haas / Jean Duteau: 3-0-0
-
Correction
-
Non-substantive
-
DSTU1 [deprecated]
Existing Wording: In Structure documentation: "Content in a format defined elsewhere
It the Attachment has data, it SHALL have a contentType"
contentType 0..1
In description:
"The contentType element SHALL always be populated. It can include charset information and other mime type extensions as appropriate. If there is no character set in the contentType then the correct course of action is undefined, though some media types may define a default character set and/or the correct character set may be able to be determined by inspection of the content."
Proposed Wording: Make description agree with cardinaltiy and structure documentation
Comment:
Attachment.contentType is NOT required unless there is a url, but Attachment documentation conflicts
- is voted on by
-
BALLOT-685 Negative - Michelle Miller : 2015-May-FHIR R1
- Balloted