V1.0

post

/ec-dc-svc/rest/v1.0/studies/{studyId}/{mode}/dataelements/withvendorcode

Creates data for a visit and for a form by vendor code, mainly used for Repeating Form.

Request

Path Parameters
Supported Media Types
Request Body - application/json ()
Root Schema : schema
Type: object
Request payload to create or update data elements with contextual information and the list of elements.
Show Source
Nested Schema : Context2
Type: object
Extended context including repeat sequence and repeat form number.
Show Source
  • Unique identifier(UUID, 32-character uppercase hexadecimal string) representing the clinical event like Screening, Visit 1 etc.
    Example: 699EF3745FC545589F186D2198F3C65E
  • Numeric value representing the instance number of the event. Used for repeated or unscheduled visits. It is null for scheduled events.
    Example: 1
  • Unique identifier(UUID, 32-character uppercase hexadecimal string) representing the clinical form.
    Example: 299BC76CF0F943E6BAC1D209BC3D1CDC
  • Represents the ordinal number assigned to a repeated instance of a data collection form. It uniquely identifies each occurrence of a repeating form for a subject when multiple instances of the form.
    Example: 1
  • Indicates the order of occurrence for a repeating form instance, used to distinguish between multiple repetitions of the same form.
    Example: 1
  • Unique identifier (UUID, 32-character uppercase hexadecimal string) representing the clinical site.
    Example: A86F2D0BB610404DB62D37AFA9C20B50
  • Minimum Length: 0
    Maximum Length: 100
    Name of the study
    Example: DEMO_STUDY
  • Minimum Length: 0
    Maximum Length: 100
    String representing the version of the study configuration or protocol. Helps track changes in form or study design.
    Example: 1.0.0.1
  • Unique subject identifier (UUID, 32-character uppercase hexadecimal string) representing the patient/participant enrolled in the study.
    Example: B1B8327AFAA6412287106192AB5984EF
Nested Schema : dataElements
Type: array
List of data elements to process for the given context.
Show Source
Nested Schema : CoreDataElementV3
Type: object
Core data element payload (v3).
Show Source
  • Minimum Length: 0
    Maximum Length: 2048
    Any general comments for the data element instance.
    Example: Measured after fasting
  • Unique Data flag identifier(UUID, 32-character uppercase hexadecimal string).
    Example: B1B8327AFAA6412287106192AB5984EF
  • ID (UUID, 32-character uppercase hexadecimal string) of the form section.
    Example: D9876543D9876543D9876543D9876543
  • Primary uuid identifier for the data element instance (HEX, upper case).
    Example: C1234567C1234567C1234567C1234567
  • Unique Item identifier (UUID, 32-character uppercase hexadecimal string) from the study Designer, associated to a form.
    Example: 1BC29B36F5D64B1B95F4BDBBCEA481BE
  • Unit of measurement for this value (if applicable).
    Example: mg/dL
  • An identifier representing the system, or user that initiated the transaction (UUID, 32-character uppercase hexadecimal string).
    Example: F4443333F4443333F4443333F4443333
  • Minimum Length: 0
    Maximum Length: 255
    Reason for this data entry/edit.
    Example: Other
  • Indicates the order of occurrence for a repeating form instance, used to distinguish between multiple repetitions of the same form.
    Example: 2
  • Transaction end date/time for this observation.
    Example: 2024-01-01T13:00:00Z
  • Transaction start date/time for this observation.
    Example: 2024-01-01T12:00:00Z
  • Minimum Length: 0
    Maximum Length: 4000
    Measured value captured for this data element.
    Example: 42.0
  • Variable identifier (UUID, 32-character uppercase hexadecimal string) in uppercase hex format.
    Example: E5554444E5554444E5554444E5554444
  • Minimum Length: 0
    Maximum Length: 100
    Code supplied by vendor.
    Example: VENDOR42
Examples

Back to Top

Response

Supported Media Types

200 Response

Success
Body ()
Root Schema : DataElementDto50
Type: object
Data element extension adding dataFlag identifier inherited by higher versions
Show Source
Examples

400 Response

Bad request.
Body ()
Root Schema : DcsResponse
Type: object
Show Source
Nested Schema : ErrorResponseData
Type: object
Structure representing an error response from the reporting service. Contains an error code, human-readable message, and details.
Show Source
  • details
    Detailed error context or debugging information such as validation error, stack trace, or field/parameter cause.
  • Application or business-specific error code representing the error type.
    Example: REPT_401
  • Human-readable error message describing the failure or issue.
    Example: Unauthorized: User does not have access to the requested resource
Nested Schema : result
Type: object
Nested Schema : details
Type: object
Detailed error context or debugging information such as validation error, stack trace, or field/parameter cause.
Example:
User role is missing required permission REPORTING_VIEW. Field: userId
Back to Top