Transcribes patient-clinician conversations and generates clinical notes.
See https://www.paws-r-sdk.com/docs/transcribeservice_start_medical_scribe_job/ for full documentation.
transcribeservice_start_medical_scribe_job(
MedicalScribeJobName,
Media,
OutputBucketName,
OutputEncryptionKMSKeyId = NULL,
KMSEncryptionContext = NULL,
DataAccessRoleArn,
Settings,
ChannelDefinitions = NULL,
Tags = NULL
)
[required] A unique name, chosen by you, for your Medical Scribe job.
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 job
with the same name as an existing job, you get a ConflictException
error.
[required]
[required] The name of the Amazon S3 bucket where you want your Medical Scribe
output stored. Do not include the S3://
prefix of the specified
bucket.
Note that the role specified in the DataAccessRoleArn
request
parameter must have permission to use the specified location. You can
change Amazon S3 permissions using the Amazon Web Services Management
Console. See also Permissions Required for IAM User Roles.
The KMS key you want to use to encrypt your Medical Scribe output.
If using a key located in the current Amazon Web Services account, you can specify your KMS key in one of four ways:
Use the KMS key ID itself. For example,
1234abcd-12ab-34cd-56ef-1234567890ab
.
Use an alias for the KMS key ID. For example, alias/ExampleAlias
.
Use the Amazon Resource Name (ARN) for the KMS key ID. For example,
arn:aws:kms:region:account-ID:key/1234abcd-12ab-34cd-56ef-1234567890ab
.
Use the ARN for the KMS key alias. For example,
arn:aws:kms:region:account-ID:alias/ExampleAlias
.
If using a key located in a different Amazon Web Services account than the current Amazon Web Services account, you can specify your KMS key in one of two ways:
Use the ARN for the KMS key ID. For example,
arn:aws:kms:region:account-ID:key/1234abcd-12ab-34cd-56ef-1234567890ab
.
Use the ARN for the KMS key alias. For example,
arn:aws:kms:region:account-ID:alias/ExampleAlias
.
If you do not specify an encryption key, your output is encrypted with the default Amazon S3 key (SSE-S3).
Note that the role specified in the DataAccessRoleArn
request
parameter must have permission to use the specified KMS key.
A map of plain text, non-secret key:value pairs, known as encryption context pairs, that provide an added layer of security for your data. For more information, see KMS encryption context and Asymmetric keys in KMS.
[required] The Amazon Resource Name (ARN) of an IAM role that has permissions to access the Amazon S3 bucket that contains your input files, write to the output bucket, and use your KMS key if supplied. If the role that you specify doesn’t have the appropriate permissions your request fails.
IAM role ARNs have the format
arn:partition:iam::account:role/role-name-with-path
. For example:
arn:aws:iam::111122223333:role/Admin
.
For more information, see IAM ARNs.
[required] Makes it possible to control how your Medical Scribe job is processed
using a MedicalScribeSettings
object. Specify ChannelIdentification
if ChannelDefinitions
are set. Enabled ShowSpeakerLabels
if
ChannelIdentification
and ChannelDefinitions
are not set. One and
only one of ChannelIdentification
and ShowSpeakerLabels
must be set.
If ShowSpeakerLabels
is set, MaxSpeakerLabels
must also be set. Use
Settings
to specify a vocabulary or vocabulary filter or both using
VocabularyName
, VocabularyFilterName
. VocabularyFilterMethod
must
be specified if VocabularyFilterName
is set.
Makes it possible to specify which speaker is on which channel. For
example, if the clinician is the first participant to speak, you would
set ChannelId
of the first ChannelDefinition
in the list to 0
(to
indicate the first channel) and ParticipantRole
to CLINICIAN
(to
indicate that it's the clinician speaking). Then you would set the
ChannelId
of the second ChannelDefinition
in the list to 1
(to
indicate the second channel) and ParticipantRole
to PATIENT
(to
indicate that it's the patient speaking).
Adds one or more custom tags, each in the form of a key:value pair, to the Medica Scribe job.
To learn more about using tags with Amazon Transcribe, refer to Tagging resources.