Values.CreateMedicalVocabularyRequestSourceCreates a new custom medical vocabulary. Before creating a new custom medical vocabulary, you must first upload a text file that contains your vocabulary table into an Amazon S3 bucket. Note that this differs from , where you can include a list of terms within your request using the Phrases flag; CreateMedicalVocabulary does not support the Phrases flag and only accepts vocabularies in table format. Each language has a character set that contains all allowed characters for that specific language. If you use unsupported characters, your custom vocabulary request fails. Refer to Character Sets for Custom Vocabularies to get the character set for your language. For more information, see Custom vocabularies.
type nonrec t = {vocabularyName : VocabularyName.t;A unique name, chosen by you, for your new custom medical vocabulary. This name is case sensitive, cannot contain spaces, and must be unique within an Amazon Web Services account. If you try to create a new custom medical vocabulary with the same name as an existing custom medical vocabulary, you get a ConflictException error.
*)languageCode : LanguageCode.t;The language code that represents the language of the entries in your custom vocabulary. US English (en-US) is the only language supported with Amazon Transcribe Medical.
*)vocabularyFileUri : Uri_.t;The Amazon S3 location (URI) of the text file that contains your custom medical vocabulary. The URI must be in the same Amazon Web Services Region as the resource you're calling. Here's an example URI path: s3://DOC-EXAMPLE-BUCKET/my-vocab-file.txt
*)}val make :
?tags:??? ->
vocabularyName:VocabularyName.t ->
languageCode:LanguageCode.t ->
vocabularyFileUri:Uri_.t ->
unit ->
tval to_value :
t ->
[> `Structure of
(string
* [> `Enum of string
| `List of
[> `Structure of (string * [> `String of TagKey.t ]) list ] list
| `String of VocabularyName.t ])
list ]